Alert Settings options

  Test an alert action after it is created or modified. You need to verify the test was successful: the display does not report test failures. For example, for Send SNMPv1 Trap, verity the trap was received at the trap receiver, or for Send E-mail, verify the e-mail was received.  

    State alert thresholds State thresholds are thresholds defined for sensors that report state values. State threshold options Value Open or Closed Up or Down Locked or Unlocked Unknown, No Fault, or Fault No Motion or Motion Detected Varied Threshold Description Door Settings for sensors that determine whether a door is open or closed. Door (Handle) Settings for sensors that determine whether a door handle is up or down. Door (Lock) Settings for sensors that determine whether a door lock is locked or unlocked. Dry Contact Settings for sensors that determine the fault status of dry contacts. Motion Sensor Settings for sensors that detect motion. Other State Sensors Settings for sensors that measure state settings not reported for other Alert Thresholds options. State threshold types Setting Description Alert State Threshold An alarm occurs when the sensor's state matches the Alert State setting. State Mismatch Threshold An alarm occurs when the sensor's state does not match the Normal State setting. Note This threshold setting is useful for sensors that can report more than two states. Alert State for Time Threshold An alarm occurs when the sensor's state matches the Alert State setting for longer than the Time Allowed in Alert State setting's delay. State Mismatch for Time Threshold An alarm occurs when the sensor's state does not match the Normal State setting for longer than the time defined by the Time Allowed in Abnormal State setting. Note This threshold setting is useful for sensors that can report more than two states. State threshold types for rack access Setting Description Door Forced Entry Threshold An alert occurs when the door is open while the handle is down and the lock is locked, enabled by default. Note When the “Allow handle down while door open” option is selected, returning the handle to the down position while the door is open will not generate an alert. Handle Forced Entry Threshold An alert occurs when the handle is up while the lock is locked, enabled by default. Unscheduled Access Threshold An alert occurs when unscheduled rack access is attempted using a card, key, or remote command, enabled by default. Note If any of the other “Unscheduled” access thresholds are used (Card, Key, or Remote), this threshold should be removed from the lock sensor. Unscheduled Remote Access Threshold An alert occurs when unscheduled rack access is attempted using a remote command issued from the NetBotz Appliance Advanced View or Basic View, or the Data Center Expert console. Note To allow remote access without generating an alert, you must modify the threshold schedule, disable the threshold for the desired time frame, and disable the default “Unscheduled Access Threshold”. An unlock event will still be generated in the NetBotz Appliance event log. Unscheduled Card Access Threshold An alert occurs when unscheduled rack access is attempted using a card, or a door is opened with a card, and left open past that card’s access schedule. Unscheduled Key Access Threshold An alert occurs when unscheduled rack access is attempted using a key. Note To allow key access without generating an alert (for example, during normal work hours), you must modify the threshold schedule, disable the threshold for the desired time frame, and disable the default “Unscheduled Access Threshold”. A key unlock event will still be generated in the NetBotz Appliance event log.  

    Define the settings for a Set Switch Output State alert action on a NetBotz Appliance. A name field, severity selections, and the "Alert Action Scheduling" display that all alert action types share, are also available. All time periods are enabled for an alert action, by default, in its "Alert Action Scheduling" display. Element Description Switch Output Device Select the switch relay device that will be triggered by the alert action from the list of all switch relay devices defined for use with the selected NetBotz Appliance. Note When no devices that support a switch output are monitored by the NetBotz Appliance, N/A is the only choice. Switch State on Alert Select the state (On or Off) to which the selected switch relay device will be set when an alert occurs. Switch State on Clear Select the state (Unchanged, On, or Off) to which the selected switch relay device will be set when the violated threshold returns to a normal state.  

    Define the settings for a Send Wireless SMS Message alert action on a NetBotz Appliance configured with a wireless modem. This alert action is available for a NetBotz Appliance with a modem that supports SMS messaging, installed in or connected to that appliance only. A name field, severity selections, and the "Alert Action Scheduling" display that all alert action types share,are also available. Basic tab Element Description Add Click to add a destination address of the recipients to whom the wireless SMS message alert notification will be sent, in the following format. sms:sms_device_address where sms:sms_device_address is the telephone number or e-mail address associated with the SMS-enabled device. For example: sms:5123334444 or sms:user@mycorp.com Remove Click to remove a selected destination from the list. Include Threshold-specific SMS Destinations Select to send wireless SMS messages to the destination addresses added to the E-mail tab for NetBotz Appliance alert thresholds. Note If the destination addresses list is empty, and Include threshold-specific SMS destinations is not selected, no wireless SMS messages can be sent; if the destination addresses list is empty, and Include threshold-specific SMS destinations is selected, wireless SMS messages can be sent only for thresholds that have an SMS destination address identified in their Threshold-specific address list. Message Enter a message for the alert; macros can be used. Threshold-specific addresses example A “generic_send_wireless_SMS” alert action is created and no SMS destinations are included. Include threshold-specific SMS destinations is selected for this "generic_send_wireless_SMS" action. The “generic_send_wireless_SMS” alert action is added to an alert profile called “alert_profile1.” The “alert_profile1” profile is specified for two NetBotz Appliance thresholds, “temp_too_high” and “humidity_too_high.” The “temp_too_high” threshold has Threshold-Specific Addresses for User1 and User2, and the “humidity_too_high” threshold has Threshold-Specific Addresses for User3 and User4. When “temp_too_high” triggers, only User1 and User2 will receive SMS messages. When “humidity_too_high” triggers, only User3 and User4 will receive SMS messages. Advanced tab Provides elements that further define what a wireless SMS message can include, as well as an Alert Action Scheduling button that allows you to select when an alert action is enabled (all time periods are enabled, by default). Element Description Do Not Send Return-to-Normal Messages Select if you do not want to send SMS messages when the threshold state returns to normal. Message Character Size Limit (1 - 160) Identify the number of characters that can be used in the messages. Message Validity Period Select how long a period of time the messages will be valid, from 5 Minutes through 3 Days.  

    Define the settings for a Send HTTP POST alert action on a NetBotz Appliance. A name field, severity selections, and the "Alert Action Scheduling" display that all alert action types share are also available. Primary and Backup tabs You must define at least the Primary tab elements. Element Description Target URL Identify the web address, port and parameters of the system to which HTTP POST data will be posted. Target User ID Identify the user identification needed to post HTTP data to the server at the specified Target URL. Target Password Identify the password needed to post HTTP data to the server at the specified Target URL. Verify Password Retype the password. Advanced tab Provides elements that further define what an HTTP POST can include, as well as an Alert Action Scheduling button that allows you to select when an alert action is enabled (all time periods are enabled, by default). Setting Description Maximum Camera Pictures Identify the maximum number of pictures that can be included in an HTTP POST. Include a Graph with the Alert Select to include a graph with the HTTP POST. Include Related Maps with the Alert Select to include a related maps with the HTTP POST. Include a Sound Clip with the Alert Select to include related sound clips in the HTTP POST. Note Disabled for NetBotz Appliances that have no audio support. SSL Verify Options Select No verification, Verify certificate, or Verify certificate and hostname for HTTP POSTs.  

    Define the settings for a Send Data to FTP Server alert action on a NetBotz Appliance. A name field, severity selections, and the "Alert Action Scheduling" display that all alert action types share, are also available. Primary and Backup tabs You must define at least the Primary tab elements. Note The only difference between the two tabs is that the Backup tab includes backup settings. Setting Description FTP Server Hostname Identify the hostname or IP address of the FTP server that will receive the data. User ID Identify the user identification needed to log on to the FTP server. Password Identify the password needed to log on to the FTP server. Verify Password Retype the password. Target Directory Identify the relative directory path to be used to store the data at the FTP server. This should always be a path relative to the default directory associated with the user ID used to log on to the FTP server. If the directories on the path do not exist they will be created automatically. Note This Target Directory field accepts macros. Base Filename Identify the base filename to be used for storing the data at the FTP server. Pictures from alerts will be stored in files with this name, followed by the *.n.jpg file extension, where n is the picture number (1, 2, 3, etc.). Alert data will be stored in a file with this name, followed by the *.nbalert file extension. Pictures include in the data will be stored in files with this name, followed by the *.n.jpg file extension, where n is the picture number (1, 2, 3, etc.). Note This Base Filename field accepts macros. Advanced tab Provides elements that further define what an e-mail can include, as well as an Alert Action Scheduling button that allows you to select when an alert action is enabled (all time periods are enabled, by default). Setting Description Maximum Camera Pictures Identify the maximum number of pictures that can be included in the data sent to an FTP server. Include a Graph with the Alert Select to include graphs with data sent to an FTP server. Include Related Maps with the Alert Select to include related maps with data sent to an FTP server. Include a Sound Clip with the Alert Select to include related sound clips in the data sent to an FTP server. Note Disabled for NetBotz Appliances that have no audio support. Picture Export Format Select the format used for pictures sent with the data sent to an FTP server. Note The export options will depend on how the NetBotz Appliance is configured.  

 Location macros are available for use when defining alert action settings for NetBotz Appliances.   Macro Example Definition ${LOCATION} Test Lab The Location setting at a NetBotz device. ${ENCLOSURE} RACK1234 Enclosure ID ${SLOT} A23 Slot in Enclosure ${ENCRELLOC} ATUPS Position in Enclosure ${ROOM} C-100 Room Number ${ROOMROW} AA Row in Room  ${ROOMCOL} 25 Column in Room ${HEIGHT} 60 Height above Floor  ${BLDG} 205 Building  ${FLOOR} 3 Floor Number  ${COMPANY} APC Company Name  ${ADDRESS1} 132 Fairgrounds Road Address 1  ${ADDRESS2} Building 1 Address 2  ${CITY} W. Kingston City  ${STATE} RI State/Province  ${COUNTRY} USA Country  ${CONTACT} J. Smith Primary Contact  ${SITE} West Campus Site Name  ${NOTES} IT Closet, Server Room Notes  ${LATITUDE} 30° 18’ N Latitude (for units to which a GPS pod is connected) ${LONGITUDE} 97° 42’ W Longitude (for units to which a GPS pod is connected) ${GPSLOC} 30° 18’ N / 97° 42’ W The current longitude and latitude data when the alert occurred (for units to which a GPS pod is connected)

  Identification macros are available for use when defining alert action settings for NetBotz Appliances.   Macro Example Definition ${SERIAL} 5A0902V00025 The serial number of the device. ${IP} 192.168.2.23 The dotted-decimal IP address of the device. ${HOSTNAME} isxc.apc.com The hostname of the device. ${MODEL} WallBotz 500 The model of the device. ${TIMESTAMP} 998885130 The current UTC time (seconds since 1/1/1970). ${DATE} 3/27/2009 The current date (year-month-day). ${YEAR} 7/1/1905 0:00 The current year. ${MONTH} 3 The current month (2-digit number, January=01). ${DAY} 27 The current day of the month (2-digit number). ${TIME} 23-30-01 The current time (24-hour, hour-minute-second). ${HOUR} 23 The current hour of the day (2-digit, 24-hour time). ${MIN} 0:00:00 The current minute of the hour. ${SEC} 0:00:00 The current second of the minute. ${VER} 2_6_2-20071031_1658 The current firmware version of the NetBotz Appliance.

You can use the same basic procedure to delete any type of alert action for a NetBotz appliance. Select "Alert Actions" in the Device menu > NetBotz Appliance Configuration > Alert Settings option. In the "Select Alert Action Type" display, highlight the type of alert you want to delete, and click Next. In the "Select Next Action" display, select to modify an action, and click Next. In the "Select Devices" display, select the parent device or devices associated with the action you want to delete, and click Next. In the "Select Alert Actions" display, select the action or actions you want to delete, and click Delete. Click Cancel, to exit the "Alert Actions" wizard.

    Alert thresholds and supported devices Which alert thresholds can be used for sensors at the monitored devices depends on the type of device. For a NetBotz Appliance, all alert threshold options, except Power(VA) and Power (Watts), can be used to define alert thresholds on camera pods, sensor pods, and other devices managed by the NetBotz Appliance. NetBotz Appliances When you create alert thresholds for a NetBotz Appliance, its sensor pods, camera pods, and monitored SNMP devices, the threshold settings are set at the NetBotz Appliance. It is the NetBotz appliance that stores the settings and sends the alerts to the Data Center Expert server. Note Because NetBotz Appliance alert profiles are device-specific, you will not be able to configure the profile for a threshold setting when configuring that setting for multiple appliances.  

    Alert profile sequences An alert profile must have at least one sequence that includes one or more alert actions defined. When that profile is associated with an alert threshold or other alarm condition, it is the alert profile sequences, and their associated alert actions, that control what alert notifications are generated by the NetBotz Appliance in response to alarm conditions. These sequences identify what will happen in response to an alarm condition, and when it will happen. For example, for a sequence that will send an e-mail to user 1, you can do the following: Define how many minutes to wait after the alarm occurs before an e-mail is sent to user 1. Select to have e-mails continuously sent to user 1 while the alarm remains active, or limit the e-mails to a specific number, as well as how much time will elapse between e-mails. Select capture settings for Graphs, Pictures, and Maps that may be included in an e-mail sent by a NetBotz Appliance. Select the alert action that has been defined to send an e-mail to user 1. An alert profile can include multiple alert sequences which allow you to customize which alert actions are triggered, and when. For example, if sending e-mails to user 1 has not resulted in an alarm returning to its normal condition within 20 minutes, you can start sending e-mails to user 2, and start sending data to an FTP server. How many alert profile sequences you use, and what actions they use, will depend on exactly what you want to happen, and when, for alarm conditions, including alert threshold violations, associated with the alert profile.

Alert macros are available for use when defining alert action settings on NetBotz Appliances.   Macro Example Definition ${ALERT_LEVEL} First Alert Level, Second Alert Level Corresponds with the Label value of the alert sequence. ${ALERT_PROFILE} Default, Profile #1 The name of the specific alert sequence that caused the alert to be generated. ${ALERTPODSERIAL} NB007100730114 The serial number of the pod that either contains the sensor that reported the alert or to which the sensor is connected. ${ALERTPOD} My Pod The label of value of the pod that either contains the sensor that reported the alert or to which the sensor is connected. ${ALERTPORT} Ext1 The label value for the external sensor port to which the external sensor that reported the alert is connected. ${ALERTSEV} ERR, WARN-RTN The severity value reported by the sensor that is generating the alert (such as ERR, WARN, INFO). If the alert state has returned to normal, the severity value will be followed by "-RTN" (for example WARN-RTN). ${ALERTTIME} 4/2/2009 13:01 The date and time at which the alert notification was generated. ${ALERTTYPE} HIGHERR The type of alert. ${CURRENT_ALERT_NUM} 0, 1, 2 The number of times the alert sequence has been repeated, from 0 up to the Repeats value for the alert sequence. ${EVENTID} 3E4512C0FE03440F The unique 16 character identifier shared by all messages generated as a result of a single alert notification event. For example, if an appliance generates an alert notification when the internal temperature sensor threshold is exceeded, and then generates a "return to normal" message when the temperature drops below the high threshold, both of these messages will have the same Event ID number. However, if the temperature rises again and a second threshold exceeded alert is generated, the second alert will have a new Event ID. ${ISACTIVE?yes?no} “active” and “cleared” Specifies custom active vs. return to normal text. The strings “yes” and “no” can be replaced with user-specified strings. For example, if you specify “active” and “cleared” for the “yes” and “no” values and the macro is translated, if the alert is still active the word "active" would appear and when it has returned to normal, the word "cleared" would appear. ${RESOLVE_TIME} 13:07:13 The time at which the alert condition returned to normal. ${RESOLVECOMMENT} “Turned on the A/C”; “Fixed the leak” The text entered into the user-specified description field whenever an alert needs to be manually returned to normal (an option which can be selected whenever a threshold is configured). ${RESOLVEUSERID} joeuser The user ID that is responsible for manually resolving an alert (when this option applies). ${SENSORGUID} B000113_TEMP1 The globally unique ID of the sensor generating the alert. ${SENSORLUID} TEMP1 The locally unique ID of the sensor generating the alert. ${SENSORNAME} Bldg. 3 Door The name of the sensor associated with the alert. ${SENSORTYPE} TEMP The type of sensor generating the alert. ${SENSORVAL} 60 The value reported by the sensor that is generating the alert. ${START_TIME} 13:01:45 The time at which the alert condition was initially detected. ${USERDESC} “Too high” The user-specified description value which can be defined within the threshold configuration. ${USERURL} http://www.mysite.com The user-specified URL that can be defined within the threshold configuration.

    Alert action severity settings Every alert action type allows you to select up to five severities. The alert action will only trigger when used in an alert profile that is tied to an alert threshold with a matching severity. In the following example, User1 will only receive an sms message if a critical severity threshold is violated. An alert action named "send_user1_sms” is created, and defined to send User1 an SMS e-mail for critical events only. The “send_user1_sms” alert action is added to an alert profile called “sms messaging.” The "sms messaging" alert profile is selected on various alert thresholds. The alert thresholds are of varying severity - some are set for critical, and some are set for warning. If an alarm occurs, User1 will only receive an SMS message for those alert thresholds defined as critical. You must select at least one severity. Severity Description Information Typically used to set up an alert action to respond to events considered to be unimportant, but important enough to require alert notifications when they occur. Warning Typically used to indicate a condition exists that may require attention to make sure it does not deteriorate into a critical state. Error Typically used by NetBotz Appliances to indicate a sensor threshold violation requires immediate attention. For example, a high temperature violation that could lead to equipment damage. Critical Typically used to indicate an operational failure requires immediate attention. Failure Typically used by NetBotz Appliances to indicate an operational failure requires immediate attention. For example, communication with a camera pod was lost which could lead to an undetected security violation.  

    Use the "Alert Actions" wizard used to create and edit the actions that can be included in the alert profiles used with alert notifications for monitored NetBotz Appliances. The alert notifications can alert you, or other members of your organization, when a sensor threshold violation, or other alarm condition, occurs at a monitored NetBotz Appliance. Note A default alert profile exists for notifications associated with each NetBotz Appliance. You can create multiple versions of the alert actions, each with unique settings, such as which severities apply to the alert action.  

    "Alert Action Scheduling" display Use this display to define the specific periods of time, for each day of the week, during which an associated activity will be disabled (by default, scheduling is enabled 24 hours a day, seven days a week). Note This display is used to schedule when an alert action will be enabled and disabled, using the action's settings display, or to schedule when a camera is enabled or disabled, using the "Surveillance Settings" display. The table provides cells for 15-minute increments, and columns for every day of the week. You can do all of the following to schedule when an alert action, or camera, is enabled:   Click a column title to enable or disable all of that day's cells. Drag your mouse from one cell to another cell in a column, to enable or disable a set of cells. Drag your mouse from a cell in one column to a cell in another column, to enable or disable an identical set of cells for each of the selected days. Click a single cell. Note The surveillance activity on a camera can also be scheduled directly on the NetBotz Appliance, and in the Data Center Expert client Surveillance perspective. The camera will not capture data when either the Data Center Expert server or the NetBotz Appliance has surveillance disabled; both must have surveillance enabled, to capture data.  

    "Activate Button Output" display Use this display to define the settings for an Activate Button Output alert action on a NetBotz Appliance. A name field, severity selections, and the "Alert Action Scheduling" display that all alert action types share, are also available. Element Description Button Output Device Select the button-output device that will be activated at the NetBotz Appliance. Note   When no devices that support a button output are monitored by the NetBotz Appliance, N/A is the only choice. Activate on Return-to-Normal Select to activate the button output when the threshold state returns to normal.