ArcGIS Enterprise Analysis with System Log Parser's Optimized Analysis Type (Beginner)

5785
4
07-03-2022 03:35 PM
AaronLopez
Esri Contributor
3 4 5,785

System Log Parser's Optimized Analysis Type

Although you are probably familiar with using System Log Parser (SLP) to read logs and help you quantify your ArcGIS Enterprise usage, there is a relatively new feature in this popular, free utility that can make the effort easier and the analysis more powerful.  

This feature is the "Optimized" report option which is a new parameter in the GUI listed under Analysis Type. For log queries such as ArcGIS Server (Web), ArcGIS Server (File System), Internet Information Services (IIS) and Elastic Load Balancer (AWS), it is now the default. This option is not yet available for Cloud Front and Azure log queries. For backward compatibility, Simple, WithOverviewCharts and Complete types are still an option, but for the best analysis experience, they are not recommended.

  • The Optimized Analysis Type option shown in the GUI:

systemlogparser_iis.png

A System Log Parser spreadsheet report generated using the Optimized option:

systemlogparser_report_optimized.png

Also Available From the Command-Line

The GUI (SystemLogsGUI.exe) is convenient for creating reports but the command line version (slp.exe) is great for automating System Log Parser analysis. The Optimized report option is available from both!

Optimized Report Origins

Over the years, one of the most requested enhancements for SLP has been to improve the speed and memory usage (of the machine running it) when parsing logs for very busy Sites or large time spans (e.g. several weeks or more). The Optimized report directly addresses these two items. Performance is measurably faster and memory orders of magnitude lower. With the ability to search greater spans of time with a quicker executions, more powerful statistics can be performed as the report can analyze more requests.

For the best results, use the Optimized report with ArcGIS Server (File System), Internet Information Services (IIS) or Elastic Load Balancer (AWS) log queries. Memory usage savings can still be obtained with ArcGIS Server (Web) log queries, but the act of retrieving large amounts of logs through the REST Admin API is still the performance bottleneck.

Optimized Report Contents

System Log Parser reports focus on grouping the values from the logs into key time-based categories. While the Optimized report for the different log sources (ArcGIS Server, IIS, or ELB) has some commonality, there can be additional statistics depending on which was utilized. For example, if the Optimized report was used for querying ArcGIS Server (Web) or ArcGIS Server (File System) logs, wait time, instance creation time, and arrival time will each be statistically broken down in additional to elapsed time. 

System Log Parser Support

For support contact SystemTestTool@esri.com

Note: System Log Parser is developed from Esri's Professional Services but is not a product of Esri.  

Latest Version

Bug fixes and new features are always being added to SLP.

The latest version can be found here: System Log Parser (0.12.17.0) 

 

4 Comments
notebooker
New Contributor

Hi Aaron,

is it possible to let the application (GUI version) persist Log Location and Report Folder? Every time I start the app, it has default values.

Thank you. 

AaronLopez
Esri Contributor

Hello @notebooker,
In the System Log Parser GUI it is not possible to persist those values.

However, everything you can do in the GUI you can also accomplish in the command-line version, slp.exe.
With PowerShell (or bat) scripts, you could persist the necessary inputs and make the execution easier.

Hope that helps.

Aaron

WenfengLi
New Contributor III

I generated reports successfully. However most tables are empty (such as users, waiting time, statistics.....). I have the ArcGIS log level set to INFO. Is it the problem? Should set to to higher level of logging? 

ghaskett_aaic
New Contributor II

Hello.

Do we know if there are any compatibility issues with this tool and the ArcGIS Enterprise 11.2 software?

I recently set this up and ran it on one of our servers, however it doesn't look like it is working properly.

It completed and shows a start time and end time for the query and timing for the Start/End Time for Data (Coordinated Universal Time), but it doesn't show a Start/End Time for Data (Central Standard Time), plus the Data TimeSpan value is 0 along with a lot of the other values from Unique Resources Requested down.

Am I not filling something out right or is there an issue with 11.2?

Thanks,

systemLogParser.png