Analyzing synthetic health event details
For applications with synthetic transaction monitoring enabled and as the application operator, you can identify and diagnose application issues by examining a single event and see the violations that contributed to the event. You can use the event details to help identify the source of application issues.
This topic contains the following information:
Before you begin
Before you can examine a single event and see the violations that contributed to it, ensure that your system meets the following conditions:
- To access the Synthetic Health tab, you must be logged in with -level access, or higher.
If you do not define your own synthetic metric rules, only the global metric rules for performance, availability, accuracy, and execution events are evaluated. are defined, usually by an application specialist in your organization.
To view the details of a synthetic health event
- From the navigation pane in the TrueSight console, select Monitoring > Applications.
- Select one application that you want to examine in detail.
- Under the Synthetic Health tab, in the Events table, click a value in the Violation Frequency column to see the Event Details view for that event.
The Synthetic Health > Event Details view has two sections.
- The header displays specific information about the event.
- The Violations table displays details for all violations that contributed to opening and updating the event.
Evaluating the Event Details header
The following event details are displayed in the header:
When the event's severity changes, the event is updated with the current severity status.
Description of the Event Details header
Click to collapseor expand the header section.
From the action menu, you can close an open event.
Indicates if the event severity is Minor or Critical.
Indicates if the event is currently Open or Closed
If the event is Closed, the time the event was closed is also displayed.
|Start Time||Time the event was opened.|
Name of the synthetic metric rule that defines the criteria for opening this event
Click the name of the rule to view its settings and fine tune the criteria for the results you want to see.
Name of the Execution Plan through which the transaction was executed on the application
|Transaction||Name of the transaction on which the event occurred|
Defined number of impacted execution cycles within the defined number of total execution cycles.
The violation frequency is defined in the synthetic metric rule.
|Location Threshold||Defined in the synthetic metric rule, the location threshold|
Locations where the metric thresholds were breached:
Metrics that breached thresholds:
Examining the violations associated with an event
In the Violations table you see data about metrics that breached defined thresholds in selected locations, which contributed to the event status.
By default, only the violations that caused the last event update are displayed in the table. That is, only the specific combination of the definitions in the synthetic metric rules that caused the event to open or change severity are displayed. If you want to see all the violations that occurred from the time the event opened until its current status and severity, clear the Show only violations that caused the event update check box.
Description of the Violations table
For each violation, you can perform the following actions:
|Severity||Indicates if the violation is Minor or Critical|
|Location||Name of the location where the violation occurred|
Name of the measured metric
Defined threshold for the metric
Actual value that breached the threshold
Time that the execution cycle starts and ends.
An execution cycle comprises a single run of an Execution Plan in all of its defined locations.
|Transaction End Time||Time that the transaction ended|
Where to go from here
If necessary, adjust synthetic metric rules to reflect better the critical data you need for your environment.