APC NetBotz 320 Rack Appliance NBRK0320E Manual De Usuario
Los códigos de productos
NBRK0320E
Advanced View: Creating Alert Actions
Using Your Appliance
165
delivering the custom HTTP GET command to an alternate web host. This backup URL would be
used only if attempts to deliver the alert data to the primary Target Host failed. You can also check
the following check boxes:
used only if attempts to deliver the alert data to the primary Target Host failed. You can also check
the following check boxes:
– Use POST instead of GET: Uses the POST command instead of the GET command.
– Include XML-encoded Alert Parameter (xmlalert): Appends the parameter “xmlalert=<xml
alert encoding>” to the provided URL for the action. The encoded XML is the same as is
generated by the HTTP POST code, but is URL-encoded to enable those that can't easily handle
multi-part/form-data encoded POSTS to get the XML for the alert.
generated by the HTTP POST code, but is URL-encoded to enable those that can't easily handle
multi-part/form-data encoded POSTS to get the XML for the alert.
9. Click OK to save this Alert Action.
Example Target URLs
When creating a Send Custom HTTP GET alert action, a data handling application of some sort (CGI
script, ASP script, servlet, etc.) must be invoked on the web host invoked in the Target URL, and
appropriate data must be passed to the application in a format that is appropriate. Therefore, the content
of the Target URL field is entirely dependent on the configuration of the target server which will process
the HTTP GET. The following examples demonstrate two possible ways in which this alert action could
be configured, and are intended to help you to construct an appropriate Target URL value.
script, ASP script, servlet, etc.) must be invoked on the web host invoked in the Target URL, and
appropriate data must be passed to the application in a format that is appropriate. Therefore, the content
of the Target URL field is entirely dependent on the configuration of the target server which will process
the HTTP GET. The following examples demonstrate two possible ways in which this alert action could
be configured, and are intended to help you to construct an appropriate Target URL value.
Example #1:
In this first example, the custom HTTP GET command provides user-specified values for a CGI script
(pagersend.cgi). This custom HTTP GET would send the message “hello there,” with a subject of “test
message,” from “mike” to the specified pin (telephone number):
(pagersend.cgi). This custom HTTP GET would send the message “hello there,” with a subject of “test
message,” from “mike” to the specified pin (telephone number):
http://www.mymmode.com/messagecenter/pagersend.cgi?pin=512
5551212&from=mike&subject=test+message&message=hello+there
5551212&from=mike&subject=test+message&message=hello+there
Example #2:
In this example, alert data is sent to a pager using the same CGI script (pagersend.cgi) as we used in
Example #1, but this time we use BotzWare macros to dynamically generate the message content:
Example #1, but this time we use BotzWare macros to dynamically generate the message content:
http://www.mymmode.com/messagecenter/pagersend.cgi?pin=512
5551212&from=${HOSTNAME}&subject=test+message&message=${SENSORNAME}+${SEN
SORVAL}+at+${ALERTPOD}
5551212&from=${HOSTNAME}&subject=test+message&message=${SENSORNAME}+${SEN
SORVAL}+at+${ALERTPOD}
A message generated by this Target URL could read “Humidity 94% at Sensor Pod 0930261” from
“mybotz.netbotz.com.”
“mybotz.netbotz.com.”
Creating a Send Custom Text File to FTP Server Alert Action
If you are creating an Alert Action that will use the Send Custom Text File to FTP Server alert
notification method:
notification method:
1. Double click on the Alert Actions icon to start the Alert Actions task.
2. Click Add to open the Select Notification Method window.
3. Select Send Custom Text File to FTP Server from the Select Notification Method pop-up window
and then click OK to open the Add Alert Action window.
4. Type in the Alert Action Name field a name for this alert action.
5. Specify Advanced Scheduling for the Alert Action (optional). By default, all Alert Actions are
assumed to be active 24 hours a day, 7 days a week. However, you can specify that an Alert Action
will be active only when alert conditions occur during specific time ranges. To configure Advanced
Scheduling:
will be active only when alert conditions occur during specific time ranges. To configure Advanced
Scheduling: