You can collect monitoring messages for all message flows in a server by deploying a
monitoring profile in a policy project, and configuring the server.conf.yaml
file.
Before you begin
Create a monitoring profile that uses the Event type
All transaction events, and the Event source address
transaction.all as described in Creating a monitoring profile.
About this task
You can collect monitoring messages for all message flows in a server by creating a monitoring
profile that is configured for all transaction events. You must then add the profile to a policy
project before you deploy it to the server. You must then configure the
server.conf.yaml file for all transactions, enable the collection of the
events, and enable the writing of the events to a file.
To collect monitoring messages for all message flows in a server, complete the following
tasks.
Procedure
- If you do not have a monitoring profile that uses the Event type
All transaction events, and the Event source address
transaction.all, create one as described in Creating a monitoring profile.
-
Add the monitoring profile to a policy project and deploy it to the integration server. For
more information, see Deploying and redeploying a monitoring profile.
-
Configure the default monitoring profile for all flows in the
server.conf.yaml file. In the following example, the monitoring profile is
called AllTransactions_Test and is in a policy project called PolProj
:
Defaults:
Policies:
monitoringProfile: '{PolProj}:AllTransactions_Test' # Default Monitoring profile
-
Configure the server.conf.yaml file to enable the collection of monitoring
events:
Monitoring:
MessageFlow:
publicationOn: 'active' # choose 1 of : active|inactive, default inactive
# Ensure Events.BusinessEvents.MQ|MQTT is set
#eventFormat: 'MonitoringEventV2' # choose 1 of : MonitoringEventV2|WMB
-
Configure the server.conf.yaml file to enable the writing to file of
monitoring events:
Events:
BusinessEvents: # Monitoring events
File:
enabled: true # Set true or false, default false
#outputFormat: 'json' # Set comma separated list of one or more of : json,xml. Defaults to 'json'
The publishing of the events can be done over WebSphere MQ, MQTT, or ELK.