ServicePulse collects and displays performance monitoring data about running endpoints on the Monitoring tab.
The main monitoring tab shows a list of logical endpoints as well as the performance data collected about those endpoints. If a logical endpoint is running more than one physical instance, a badge will show a count of physical instances.
Clicking on an endpoint in the main monitoring tab will open the endpoint details page.
The endpoint details page shows larger graphs for each of the performance metrics gathered for the logical endpoint. It also contains a number of breakdown views.
The default breakdown view is by Message Type.
This shows a breakdown of performance metrics for each type of message that the endpoint processes.
The second breakdown view is by Instance.
Each logical endpoint can be running one or more physical instances. This view shows a breakdown of performance metrics for each physical instance.
The main monitoring tab and the endpoint details page both contain an option to change the reporting period.
All graphs present the data collected during this reporting period. Where an average is shown, it is the average over the selected reporting period.
All performance metric data is retained in memory in the ServiceControl Monitoring instance. Restarting the ServiceControl Monitoring instance will cause all performance metric data to be lost.
Performance metric data is only kept by the ServiceControl Monitoring instance long enough to support the longest reporting period (1 hour).
If an endpoint instance stops sending metric data it will appear with a warning indicator.
This warning indicator will show in the instances break down on the endpoint details page for each instance that is not sending metric data.
If ServicePulse is aware of failed messages to be processed by an endpoint, it will show a badge indicating how many failed messages there are.
Click this badge to review the failed messages for this endpoint. See Failed Message Monitoring for more details.