Finding a reported error by its error ID

1.Note the error ID from the client's error message (e.g. E334507610T34707).

2.Enter the error ID under Advanced filters in the Log Explorer.

3.Click the entry: the detail view shows the complete message.

4.Use ±1 min around this entry and clear the error ID filter to see the entries right before and after – the actual cause is often found there.

 

Narrowing down an accumulation of errors

1.Look for sections with many red bars in the timeline.

2.Drag across the section or zoom in with the mouse wheel.

3.Click a bar to see the most frequent messages and affected projects.

4.Use Error groups to check whether it is a single error that repeats (e.g. a map service that cannot be reached) or several different ones.

 

Following the actions of a user

Click an entry of the user and click filter next to Session in the detail view (or double-click the session ID in the table). The table then shows all entries of this user session in chronological order.

 

Problems after a restart or update

Use Jump to application start to go to the start in question. The entry shows version and build; the entries after it show the initialization of the projects and map services.

 

Comparing the logs of several cluster nodes

Put the log files of all nodes into one folder per node and drag the folders into the Log Explorer Standalone. The entries are merged chronologically; the column File shows which node an entry comes from, and the file chips show and hide individual nodes.

 

Getting more details for an analysis

1.In SynAdmin, set the logging category in question to DEBUG on the Logging tab (see Troubleshooting and problem solution).

2.Enable Live in the Log Explorer and reproduce the problem; the new entries appear after a few seconds.

3.Use the category filter (Ctrl + click on the code) to show only the messages of this category.

4.Reset the logging category afterwards – DEBUG can slow down the application considerably.