The Event List is a grid-like interface displaying a list of all the events within the current timeframe and View. Each row in the grid describes an event and provides deep contextual information as to its type, location in the code and impact in terms of volume and spread across your application.
For each event the grid displays the following values:
- Type - The type of the error. Possible values:
Event Type Description Caught Exception Exceptions that were captured and dealt with by the user’s application Uncaught Exception Exceptions that were not captured by the user’s application Swallowed Exception Exceptions that were captured but ignored by the user’s application Log Error Events logged as Errors in the user’s applications Log Warning Events logged as Warnings in the user’s applications HTTP Error HTTP communication errors Timer Events that exceeded thresholds configured under Timers Custom Event Events that occur in the custom SDK
- Error - The name of the error. In case of an exception this is the exception class name (e.g. AmazonException, NullPointerException, etc.). In case of a log error or warning this is a sample message for that event (e.g. "Could not complete operation for user...").
- Error Location - The application class and method in which the event occurred. OverOps displays the last location in the application code calling into the error (vs. 3rd party code), even if the actual error is generated by a 3rd party or core JDK frameworks, to direct attention to the code that is being impacted within your application. Error location can also be filtered according to packages.
- Entry Point - The application class and method at the top of the call stack leading to the event. The entry point demonstrates the business transaction/application flow impacted by the event.
- Times - The number of times this event has occurred. This value indicates the severity of the event. The Times column adjusts itself to the current timeframe, meaning it dynamically reflects the number of times this event has occurred within the configured timeframe (e.g. last hour, last day, 10:30 - 11:00 pm, etc.).
- Error Location Calls - The number of times the application method containing the error has been called. For example, an application method 'foo' may be calling into framework 'util' which is called into by many locations within the application. OverOps measures the number calls specifically into 'foo' vs. 'util', which may contain many calls that are irrelevant to this event. This is especially helpful within the context of the Error Rate column below.
- Error Rate - The percentage of time when this errors occurs out of calls into the error location. This value is calculated as Times / Error Location Calls. It provides powerful context as to how many times it occurs compared to calls into the actual code.
- First Seen - The time in which this error was first detected in your environment.
- Last Seen - The last time this error was detected in your environment. This value indicates whether this event is still impacting your application.
- Applications - The list of applications (e.g. "Producer-Service", "Consumer-Service", Web-frontend", etc.) in which this event was detected. Click here to learn how to assign application names to the JVMs.
- Servers - The list of servers in which this error was detected. Click here to learn how to assign names to the monitored servers.
Hover over the Applications and Servers column to see which Servers or Applications have reported this error:
The Event List can be searched and sorted to concentrate on the most relevant events.
- Sort by First Seen - Sorts event according to the newest events introduced into your application within the last day, week, etc. This enables you to keep track of when new errors have been introduced to your environment.
- Sort by Times - Sorts events according to those happening most frequently within the current timeframe.
- Sort by Last Seen - Sorting by Last Seen combined with the Last day/hour timeframe, displays the errors happening in real-time within your application.
- Filter Type to Uncaught Exceptions - Filters exceptions not handled by your code, which may lead to undetected failures.
- Filter by Entry Point or Error Location - Filters events that were originated or called in into your code from specific locations.
- Filter by Server/Application - Filters the impact and the level of errors impacting a specific set of monitored servers or JVMs that you tagged with application names.
To sort and filter events, use and at the top of each column.
Filters set within the grid are automatically reflected in the Filter bar that appears below the grid header.
To choose filters:
- Where applicable, from the filter heading, click to choose elements to filter and then click Apply.
Filters can be saved as Views and shared with team members to highlight the important events and applications. Click here to learn more about Views.
To set the Event List Columns:
- From the + at the top-right of the Event List, choose the columns to display in the Event List.
The selection is saved as in the Views settings.
The Search box enables you to search through the application for events according to error type, name, location and entry point. The search box uses auto-complete to make searching easier.