Menu Path : Notifications>Default Settings |
Read Access Rights:
|
Write Access Rights:
|
The Default Settings page enables you to:
- Set up notifications for unmonitored components.
- Set the default Resend and Escalation Periods.
- Set the default threshold values for communication points, routes and web services.
Default Notification Settings
Notifications for Unmonitored Components
The Notifications for Unmonitored Components panel can be used for all new components that are being added and do not have notifications set up, or in cases where the notification schedule has gaps. The purpose of Unmonitored Component Notifications is to handle components that do not have any Person (24x7), Watchlist, Email, Windows Event Log or SNMP set up to receive notifications and where watchlists have gaps in the schedule.
When a Warning, Alarm or Escalation is raised for a given component, Unmonitored Component Notifications are only sent if they are not already being sent to any of the following recipients: Person (24x7), Watchlist, Email, Windows Event Log or SNMP.
When assigning a Person in the Notifications for Unmonitored Components panel it is possible to assign a user who cannot view all the lockers for all unmonitored components. In this instance, a warning is shown. It is still possible to configure and save the user in this state if required. All users will receive all notifications of all unmonitored components, irrespective of their ability to view some, or all, of the components. However, this may result in users receiving notifications for problems which they are unable to resolve.
Resend and Escalation Periods
When an issue is raised, a notification is sent. The resend period is when a Warning or Alarm will be resent for a notification. Escalation is the period after a notification event is escalated from an alarm to an escalation (the issue is of much higher importance and needs to be looked at).
However, If an issue that has been escalated to an alarm no longer exists, then the issue correctly resolved. However, if the issue occurs again (even as a warning):
- Within the resend period, then the issue is escalated back to alarm immediately.
- After the resend period, then the issue is raised as a new warning.
Field |
Description |
|---|---|
Resend Warnings Every |
A warning is sent every |
Resend Alarms Every |
An alarm is sent every |
Send Escalations After |
A notification is escalated from an alarm to an escalation after |
Setting any of these periods to 0 (zero) disables resends or escalations. Each individual route or communication point has its own 'Resend and Escalation Periods' settings; therefore if required, these settings can be overridden at the component level.
Select the Apply button to save the changes made to the Resend and Escalation Periods panel.
- Click the Discard Changes link to discard any changes made to the page.
Default Threshold Settings
The issue will be raised only in the context of an associated component. The default settings apply unless the setting has been overridden for a specific component.
- Select the Apply button at the bottom of the page to save the changes made to the Default Threshold Settings panel.
- Click the Discard Changes link to discard any changes made to the page.
Communication Points
Issue |
Description |
Default Value | |
|---|---|---|---|
| Warning | Alarm | ||
Communication Point Stopped |
When the communication point has stopped. This includes being stopped manually or via a schedule. |
Warning | |
Communication Point Stopped In Error |
When the communication point has stopped due to an error. |
Alarm | |
Communication Point Started |
Every time the communication point is started. This includes being started manually or via a schedule. |
Warning | |
Communication Point Started Out Of Schedule |
When the communication point has a scheduled start time and is manually started. |
Warning | |
Unexpected Message Tracking Response |
When the communication point has received an unknown response via Message Tracking. |
Warning | |
Message Tracking Response Timeout |
When the communication point has not received a response to a tracked message sent by the communication point. This issue will only be triggered when the maximum retries have been exceeded. |
Warning | |
Error Queue Message |
When a message is sent to the Error Queue by the communication point. |
Warning | |
Long Idle Time (mins) |
When the communication point has had no messages sent or received for a period of time. |
10 | 30 |
Large Queue (messages) |
When the communication point has a certain number of messages waiting to be sent on it. This event typically means an external system has gone down and the communication point has a number of messages to send to the external system. It may also occur when the route the communication point is on is stopped. |
25 | 100 |
Unconnected Running Communication Point (mins) |
When the communication point is running with no connections or has been retrying for a period of time. |
10 | 30 |
Slow Message Processing (secs) Average over (mins) |
If the message latency for the communication point exceeds the defined notification thresholds (in seconds), on average, over the course of the past For example, for the default settings:
Therefore, for a message latency of 399,994 milliseconds, the corresponding notification would be: Over the last 5 minute(s) communication point 'This TCP Server' has sent 1 message(s). These messages had an average processing time of 399,994ms which exceeds the configured threshold of 30 second(s). The calculation of the message processing time is performed only when a message is sent by the communication point. Consequently, a notification for slow message processing can only be only generated after the message has been sent by the communication point. Therefore, this notification cannot be used to identify cases where a message is currently waiting on the output queue of a communication point. |
10 | 30 |
Message Potentially Stuck While Sending (mins) |
Raised if a message has been provided to a communication point connection thread for sending but has for any reason not completed the sending process in the specified amount of time (in minutes). This notification could be raised multiple times on the same communication point simultaneously, but the number of notifications is effectively limited by the number of communication point connection threads as configured. This issue cannot be manually resolved by the user. It is automatically resolved if the message leaves the connection thread or if the communication point is stopped. As messages cannot be stuck while sending during Rhapsody startup, any active notifications of this type are automatically resolved during startup. Furthermore, it does not appear in the activity stream when it is not configured as a warning or alarm. |
10 | 20 |
| Messages in Failed Queue (mins) | Raised if the Failed Queue of a communication point contains at least one message (in other words is not empty) for over a certain period of time. | 10 | 60 |
Routes
Issue |
Description |
Default Value | |
|---|---|---|---|
| Warning | Alarm | ||
Route Stopped |
If the route is stopped at any time, via any means. |
Warning | |
Route Stopped In Error |
If the route is stopped due to an error. |
Alarm | |
Route Started |
Any time a route is started manually or via a schedule. |
Warning | |
Error Queue Message |
When a message is sent to the Error Queue by the route. |
Warning | |
Hold Queue Message |
When a message is sent to the Hold Queue by the route. |
Warning | |
Long Idle Time (mins) |
If the route has no messages flowing through it for the time period specified. |
10 | 30 |
Large Queue (messages) |
If there is a backlog of messages waiting to be processed by the route. This generally indicates that the route is not processing messages as quickly as required. |
2500 | 5000 |
Message Time In Filter Exceeded (mins) |
When a message has been processing in the same filter for longer than desired. |
5 | 10 |
Web Services
Issue |
Description |
Default Value | |
|---|---|---|---|
| Warning | Alarm | ||
Web Service Connector Restarted |
When a user explicitly restarts the web service connector. |
Warning | |
Web Service Retrying |
When the web service enters the retrying state. The primary cause of this is the HTTP server was unable to bind to the selected port and address and so cannot listen for messages. |
Warning | |
Web Service Started |
When the web service enters the running state when it was previously in another state (not configured or retrying). |
Warning | |
Long Idle Time (mins) |
If the web service has been idle for longer than the specified time interval. |
30 | 60 |
System
To review the system threshold settings, first apply any changes to this page and then navigate to the System Monitor page.
3-Step Guide For Setting up Notifications
The 3-step guide appears at the top of the Default Settings page for all users when an administrator or developer has navigated there by clicking on the page link in the 3-step guide. Refer to 3-Step Guide For Setting up Notifications for details.