1. ProTop Knowledge Base
  2. Advanced Alerting Configuration

How do I customize the way ProTop handles messages coming from the database log file?

ProTop defines how it handles OpenEdge database messages in etc/messages.cfg. Copy it to etc/messages.[custid].cfg and you make your edits there.

For example, we are regularly getting an alert on the ProTop Portal to the fact that after-imaging is not enabled on the database in our development environment (message 3803).  We will not use AI there and I cannot change the vendor-supplied logic causing the alert. How do I suppress them?

ProTop first reads etc/messages.cfg (this is the default file, do not change it, as it will be overwritten in future updates to ProTop).  It then looks for a localized version of the messages file named etc/message.[custid].cfg. If found, it overrides the directives in the default file with the customized instructions in the localized version.

So ...

  1. cd $PROTOP/etc
  2. copy messages.cfg to messages.[cusitd].cfg
  3. edit messages.[custid].cfg
  4. find the offending message number, 3803 in this case, and change the second parameter on the line from "alert" to "ignore"
  5. save the file
  6. the database monitor service will see the change and read the new messages.[custid].cfg file and adjust accordingly