Skip to Content

Customizing the event text

You can customize the event rule name and add it to the event description by modifying the appropriate strings in the installationDirectory\pw\pronto\conf\resources\i18nData\en_US\alarms\intelligentEvents.properties file. This adds an additional variable called $EVENTRULE_NAME and causes the event processing system to insert the name of the event rule into the description.

The properties to modify the event rule name start with the following lines:

  • pronet.alarms.abs
  • pronet.alarms.sig
Warning

Note

Multiple event rules could affect a singe event. In this case, only the first event rule name is inserted into the description text.

Event messages might be customized to include additional information in the Description field of an Event table. By editing the event text template in the intelligentEvents.properties file, you can modify the event text and add additional event data to e-mail notifications and event summary links.

There are four templates for absolute events and four for signature events.

One application of this feature is to provide users with specific procedures to follow when an issue occurs (for example, "runbooks"). Such procedures can be referenced as a URL supplied in custom event text.

For example, changing the definition in the intelligentEvents.properties file from pronet.alarms.abs.abovethresh=$MO_TYPE $ATTR_NAME above $THRESH$UNITS.<$EVENT_CODE,$ABNORMALITY,$AVG,$LAST,$DUR> to pronet.alarms.abs.abovethresh=$MO_TYPE $ATTR_NAME above $THRESH$UNITS

See http://helpserver.mycompany.com/runbooks/$MO_TYPE/$ATTR_NAME
<$EVENT_CODE,$ABNORMALITY,$AVG,$LAST,$DUR>

This can be used to reference a web page on a web server called helpserver that tells an operator what to do when an event is issued for (example) Solaris System Memory Utilization. You could make it even more specific by referring a procedure for a particular monitor instance, for example:

http://helpserver.mycompany.com/runbooks/$MO_TYPE/$ATTR_NAME/$INSTANCE_NAME

This would mean creating an extra web page for each particular monitor instance that needs its own procedure.

The above examples are simplified and are useful only in notification e-mails sent as ASCII. They cannot be used to drill-down from the event summary.

Below is a more sophisticated example that embeds an HTML reference in the definition so it can be referenced directly from the event summary. Note that in this example the web server provides dynamic web content using active server pages:

pronet.alarms.abs.abovethresh=$MO_TYPE $ATTR_NAME above $THRESH$UNITS.<A HREF="http://helpserver.mycompany.com/proserver1/runbook.asp?INST=$INSTANCE_NAME&MOTYPE=$MO_TYPE&ATTR_NAME=$ATTR_NAME">Runbook1</A><$EVENT_CODE,$ABNORMALITY,$AVG,$LAST,$DUR>
Warning

Note

  • It is very important NOT to modify the following string: <$EVENT_CODE,$ABNORMALITY,$AVG,$LAST,$DUR>. Modifying this string adversely affects certain operations in the system.
  • Each definition must appear on a single line (ignore the line breaks in the examples).
  • Expanded text appearing after {~code language="none"}}={{/code} sign should not exceed 254 characters (this limit is imposed by the database tables). Expanded text is one that already has variable substitutions. To prevent this, avoid using long URL paths for runbooks pages.
  • To avoid inappropriate navigation or event history generation failure, it is recommended to have runbooks URL within quotes.

Once the changes are completed, you must either restart BMC ProactiveNet Server or start the rate process (pw process restart rate) and then restart the snmpdc process (pw process restart snmpdc) for the changes take effect.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC ProactiveNet 9.6