Destinations for Monitoring and Transaction Events
For the Monitoring and Transaction event types, in addition to the SNMP, Elasticsearch, and EDA/Database destinations, there are additional event notification destinations to select from.
Monitoring events are generated by the following run-time actions that you can configure for your virtual services in CentraSite:
Monitor Service Performance
Monitor Service Level Agreement
Throttling Traffic Optimization
Transaction events are generated by the run-time action Log Invocations.
Destinations for Monitoring and Transaction events are as follows and you selects these destinations when you configure your virtual services in CentraSite :
An EDA/Database destination
An Elasticsearch destination
The
CentraSite SNMP server or a third-party SNMP server
An
API Portal destination
The additional destinations for monitoring and transactional events are:
SMTP Email
To specify an SMTP email destination, you must:
Select Email as a destination when you configure the run-time actions.
Set the Email Configuration parameters in
Integration Server (go to
Solutions > Mediator > Administration > Email) as described in
Administering webMethods Mediator.
The Integration Server's Local Log
To specify the Integration Server's local log as a destination, you must:
Select Local Log as a destination when you configure the run-time actions. When configuring actions, you must also specify the severity of the messages to be logged (the logging level).
Set the
Integration Server Administrator's logging level for
Mediator to match the logging levels specified for the run-time actions (go to
Settings > Logging > Server Logger) as described in
Administering webMethods Mediator. For example, if a Log Invocation action is set to the logging level of Error, you must also set
Integration Server Administrator's logging level for
Mediator to Error. If the action's logging level is set to a low level (Warning-level or Information-level), but
Integration Server Administrator's logging level for
Mediator is set to a higher level (Error-level), then only the higher-level messages are written to the log file.
Entries posted to the local log are identified by a product code of MED.
The Integration Server's Audit Log
You can select the Integration Server Audit Log as a destination for the Log Invocation action only. If you expect a high volume of invocations in your system, it is recommended that you select the Audit Log destination. For more information, see webMethods Audit Logging Guide.
