...
The Uptime Infrastructure Monitor Agent monitor determines whether an agent is running on a system that you are monitoring. For a list of the currently-supported platforms, see Monitored Application Platform Support.
Configuring Uptime Infrastructure Monitor Agent Monitors
To configure Uptime Infrastructure Monitor Agent monitors, do the following:
- In the Uptime Infrastructure Monitor Agent monitor template, complete the monitor information fields.
To learn how to configure monitor information fields, see Monitor Identification. - Complete the following options by clicking the checkbox beside each option, then specifying a warning and critical threshold.
If the thresholds that you set are exceeded, then Uptime Infrastructure Monitor generates an alert. For more information, see Configuring Warning and Critical Thresholds.- Major
The major version number of the agent. For more information, see Understanding Major and Minor Versions. - Platform
The operating system on which the agent is installed and running. - Response Time
Enter the Warning and Critical Response Time thresholds for the length of time a service check takes to complete. For more information, see Configuring Warning and Critical Thresholds.
- Major
- To save the data from the thresholds for graphing or reporting, click the Save for Graphing checkbox beside each of the metrics that you selected in step 3.
- Complete the following settings:
- Timing Settings (see Adding Monitor Timing Settings Information for more information)
- Alert Settings (see Monitor Alert Settings for more information)
- Monitoring Period settings (see Monitor Timing Settings for more information)
- Alert Profile settings (see Alert Profiles for more information)
- Action Profile settings (see Action Profiles for more information)
- Click Finish.
Exchange
The Exchange 2003 and Exchange monitors identify when certain performance counters for Microsoft Exchange servers have exceeded user-defined thresholds. These thresholds can be, for example, an inordinately high number of inbound connections or a rapidly-growing message queue. Whenever a threshold exceeds a warning or critical amount, Uptime Infrastructure Monitor generates an alert.
Use Uptime Infrastructure Monitor ’s Exchange 2003 monitor if you are using and monitoring Microsoft Exchange 2000 or 2003; use the Exchange monitor for later versions (e.g., Microsoft Exchange 2007 and 2010).
Configuring Exchange 2003 Monitors
To configure an Exchange 2003 monitor for your Microsoft Exchange 2000 or 2003 server, do the following:
- Complete the monitor information fields.
To learn how to configure monitor information fields, see Monitor Identification. - Complete the following settings by clicking the checkbox beside each option, and then specifying a warning and critical threshold.
If the thresholds that you set are exceeded, then Uptime Infrastructure Monitor generates an alert. For more information, see Configuring Warning and Critical Thresholds.- Web Mail Sends Per Second
The maximum number of messages that can be sent from the Exchange server each second. - Web Mail Auths Per Second
The maximum number of authorization requests that can be sent to the Exchange server each second. - SMTP Bytes Sent Per Second
The total number of bytes sent per second by the Exchange SMTP server. - SMTP Bytes Received Per Second
The total number of bytes received per second by the Exchange SMTP server. - SMTP Bytes Total Per Second
The total number of bytes of information passing through the Exchange SMTP server each second. - SMTP Local Queue Length
The number of messages in the SMTP queue that are scheduled for local delivery. - SMTP Messages Per Second
The maximum number of messages per second that are allowed by the SMTP server. - SMTP Inbound Connections
The number of incoming connections that the SMTP server allows. - SMTP Outbound Connections
The number of outbound connections that the server allows to all remote domains. - SMTP Connection Errors Per Second
The number of number of connection errors that occur per second. - Response Time
Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.
- Web Mail Sends Per Second
- To save the data from the thresholds for graphing or reporting, click the Save for Graphing checkbox beside each of the metrics that you selected in step 2.
- Complete the following settings:
- Timing Settings (see Adding Monitor Timing Settings Information for more information)
- Alert Settings (see Monitor Alert Settings for more information)
- Monitoring Period settings (see Monitor Timing Settings for more information)
- Alert Profile settings (see Alert Profiles for more information)
- Action Profile settings (see Action Profiles for more information)
- Click Finish.
Configuring Exchange Monitors
To configure an Exchange monitor for your Microsoft Exchange 2007 or 2010 server, do the following:
- Complete the monitor information fields.
- To learn how to configure monitor information fields, see Monitor Identification.
- Complete the following settings by clicking the checkbox beside each option, and then specifying a warning and critical threshold.
If the thresholds that you set are exceeded, then Uptime Infrastructure Monitor generates an alert. For more information, see Configuring Warning and Critical Thresholds.- SMTP Bytes Sent Per Second
The total number of bytes sent per second by the Exchange SMTP server. - SMTP Bytes Received Per Second
The total number of bytes received per second by the Exchange SMTP server. - SMTP Messages Sent Per Second
The maximum number of messages sent per second allowed by the SMTP server. - SMTP Messages Received Per Second
The maximum number of messages received per second allowed by the SMTP server. - SMTP Average Bytes Per Message
The average number of message bytes per inbound message received, indicating the size of messages received through an SMTP receive connector. - SMTP Inbound Connections
The number of incoming connections that the SMTP server allows. - SMTP Outbound Connections
The number of outbound connections that the server allows to all remote domains. - Average Delivery Time
The average time, in milliseconds, between an Exchange server receiving a message from the client, and an Exchange server delivering the message to an Inbox. - Active Connections
The number of connections to the Exchange store that have shown activity in the last 10 minutes. - Active Client Logons
The number of clients that performed any action within the last 10-minute time interval. - Active User Count
The number of unique user connections that have logged on to the server and shown activity in the last 10-minute time interval. - Current Webmail Users
The number of unique users currently logged in to Outlook Web Access. This counter decreases when users manually log out or their sessions time out. - Webmail User Logons Per Second
The number of Outlook Web Access logins or login attempts per second. - RPC Averaged Latency
The average time, in milliseconds, it takes for the last 1,024 packets to be processed. - RPC Operations Per Second
The rate that RPC operations occur, and implicitly, how how many RPC requests are outstanding. - RPC Requests
The number of client requests that are currently processed by the Exchange store. - Response Time
Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.
- SMTP Bytes Sent Per Second
- To save the data from the thresholds for graphing or reporting, click the Save for Graphing checkbox beside each of the metrics that you selected in step 2.
- Complete the following settings:
- Timing Settings (see Adding Monitor Timing Settings Information for more information)
- Alert Settings (see Monitor Alert Settings for more information)
- Monitoring Period settings (see Monitor Timing Settings for more information)
- Alert Profile settings (see Alert Profiles for more information)
- Action Profile settings (see Action Profiles for more information)
- Click Finish.
...
Live Splunk Listener
Live Splunks are scheduled searches of Splunk queries that are saved on the Splunk server. A Live Splunk automatically runs a search, can initiate an alert, and can perform actions based on that alert. You can, for example, set up a Live Splunk to search for all critical error conditions.
The Live Splunk Listener monitor enables you to capture the information generated by a Live Splunk (from Splunk 4.x only). This monitor is very similar to the External Check monitor, and uses scripts that are bundled with Uptime Infrastructure Monitor (found in the /scripts subdirectory) to return Live Splunk information to the Monitoring Station.
To use this monitor, you must first modify the two Splunk scripts that are included with Uptime Infrastructure Monitor:
- alertUptimeStatusHandler.sh
- alertUptime.py
This pair of scripts take the following options:
- --message
A message that is returned to the Uptime Infrastructure Monitor Monitoring Station. For example, if the Live Splunk is configured to search for warning conditions, you can enter the message “Changed to WARN” . - --status
The script can return the following status codes:- 0 - OK
The services are functioning properly. - 1 - Warning
There is a potential problem with one of more of the monitored services. - 2 - Critical
There is a critical problem with one or more of the monitored services. - 3 - Unknown
There is an error in the configuration of the monitor itself, or Uptime Infrastructure Monitor cannot execute the service check.
- 0 - OK
- --monitor
The name of the Uptime Infrastructure Monitor monitor to which the information from the Live Splunk is directed.
The following is an example of the script with all of its options specified:
| No Format | ||
|---|---|---|
| ||
alertUptimeStatusHandler.sh --message="sendmail has some traffic going through new command!"
--status=2 --monitorName="Live Splunk" |
Uptime Infrastructure Monitor captures the output from the script, which appears in the service status section of the Global Scan dashboard (see Understanding the Status of Services). The Uptime Infrastructure Monitor monitoring framework picks up any error codes and triggers the appropriate monitoring action.
Before You Begin
Before you can monitor Live Splunks generated on a Splunk server, you must do the following:
- Edit the alertUptime.py script to point to the Uptime Infrastructure Monitor Monitoring Station:
- Navigate to the /scripts directory on the Monitoring Station.
- Open the file alertUptime.py in a text editor.
Find the following entry in the file:
No Format nopanel true host = "uptime-host" port = "9996"
- Change the values for host and port to the host name and port of the Monitoring Station.
- Save and close the file.
- Edit the alertUptimeStatusHandler.sh script to configure how the Live Splunk is reported on the Monitoring Station:
- Open alertUptimeStatusHandler.sh in a text editor (found in the /scripts directory on the Monitoring Station).
- For the message option, enter a diagnostic message that accompanies a Live Splunk captured by the Uptime Infrastructure Monitor service monitor.
- For the status option, enter the status of the monitored service.
- For the monitorName option, enter the name of the service monitor that is listening to the Live Splunk.
- Save and close the file.
- Copy the alertUptimeStatusHandler.sh and alertUptime.py scripts from the Monitoring Station’s /scripts directory to the
/data/splunk/bin/scripts directory on the Splunk server. - Configure a Live Splunk. For information on configuring Live Splunks, see the Splunk user manual.
When setting up your Live Splunk, select the Run the shell script option on the configuration page. Then, enter the path to alertUptimeStatusHandler.sh in the field.
Configuring the Live Splunk Listener Monitor
To configure a Live Splunk Listener monitor, do the following:
- Complete the monitor information fields.
To learn how to configure monitor information fields, see Monitor Identification. - Complete the following settings:
- Timing Settings (see Adding Monitor Timing Settings Information for more information)
- Alert Settings (see Monitor Alert Settings for more information)
- Monitoring Period settings (see Monitor Timing Settings for more information)
- Alert Profile settings (see Alert Profiles for more information)
- Action Profile settings (see Action Profiles for more information)
- Click Finish.