Module 16

MODULE 16
Event Monitoring
Prepared By :
Dipanjan Das
linkedin.com/in/dauthjan
AGENDA
• What is Event Monitoring and Why we need Event Monitoring
• Required MQ concepts for Implementation – How Event Monitoring works
• Methods of Implementation
 Monitoring Properties in the nodes
 Monitoring Profile – including Monitoring Profile Policies
• Advantages of implementation by Monitoring Profile
• POC for Event Monitoring
• IBM MQ is required – is it?
What and Why!!!
 What is Event Monitoring:

Monitoring is a feature in IIB/ACE, which enables the developer to configure the flow to
emit events when something event occurs. These events can either be stored in a DB or
consumed by different monitoring applications.
 Why we need Event Monitoring:

Event monitoring helps us to log and track messages pass through our flows. Also helps
us to track the path the messages traverse of a message flow.
Required MQ concepts for Implementation
 Required MQ Components:
o Queue
o Topic String
o Subscription
 Required Concept:
o Pub-Sub Concept
How the event monitoring works?
TOPIC STRING
Required MQ concepts for Implementation
 Default Topic String:
Default format of monitoring topic string (for Integration Node):

$SYS/Broker/{{IntegrationNodeName}}/Monitoring/{{integrationServerName}}/{{messageFlowName}}
Default format of monitoring topic string (for Integration Server):

$SYS/Broker/integration_server/Monitoring/{{integrationServerName}}/{{messageFlowName}}
 Subscription Topic string:
Default format of subscribing topic string (works for both):

$SYS/Broker/+/Monitoring/#
Where + is single label , # is zero or n labels

Implementation by Monitoring properties in the nodes
Add Monitoring events:

Go to the Monitoring tab in Properties view, and click on the Add
button and follow the given screen to provide the required
information.
Event Monitoring on Integration Node [IIB]
 Enable Monitoring:
By default, Monitoring is off. Monitoring should be turned on every time a fresh deployment is
done. Open IIB/ACE console and run below commands.
 Enable monitoring for particular flow on Integration Node:

mqsichangeflowmonitoring {{IntegrationNodeName}} -e {{IntegrationServerName}} -k {{AppName}}
-f {{FlowName}} -c active
 Disable monitoring on Integration Node :

mqsichangeflowmonitoring {{IntegrationNodeName}} -e {{IntegrationServerName}} -k {{AppName}}
-f {{FlowName}} -c Inactive
Event Monitoring on Integration Server [ACE]
 Enable Monitoring:
By default, Monitoring can be turned by specifying properties on server.conf.yaml. Below shows
how to enable monitoring by default with a default monitoring Profile.
Event Monitoring on Integration Server [ACE]
 Creating Monitoring Profile Policy in ACE:

1. In the ACE Toolkit create a new Policy Project, for
example “Module 16 - Event Monitoring – POL”.
2. Import/create/copy a file inside this Policy Project
with the extension “.monprofile.xml” which contains
the XML Monitoring Profile, for example
"Monitoring.monprofile.xml". Note that currently
the Monitoring profiles inside a Policy Project are
only listed by the ACE Toolkit navigator view under
the "Other Resources" folder.
3. Deploy the Policy Project.
Extracting a Monitoring Profile from an Application
mqsireportflowmonitoring -i {{HostIP}} -p {{REST_Admin_Port}} -k “{{ApplicationName}}" -f

“{{FlowName}}" -x "D:\Monitoring.monprofile.xml"
The extracted Profile is generated as per Monitoring Event schema (location):

<install_location>/server/sample/Monitoring/MonitoringEventV2.xsd
Node Level Monitoring Config or Monitoring Profile??
 Advantages of implementation by Monitoring Profile

o Since it is a configurable service, any changes made to the profile don’t require any
deployment
o Monitoring profiles are reusable. A single monitoring profile can be used for multiple flows
 Disadvantages of implementation by Monitoring Profile (as a Policy)

o Monitoring Profile Policies are static Policies and hence, redeployment and deletion is not
possible while the EG is running.
o Be specific with the naming of Nodes where you want to target, wrong name will not
enable the monitoring.
POC on Event Monitoring
IBM MQ is required – is it?
Since IIB 10, the dependency on MQ was removed, how can we establish Event Monitoring if we do not want to use MQ in
our architecture? Till IIB 9, there was a dependency on MQ.
IIB 10 included built-in MQTT server/broker and input/output nodes for processing MQTT messages. We can use the build-
in MQTT Server or free to use any already running MQTT server.
These MQTT Brokers are only available for Integration Node. For IBM ACE with standalone Integration Server, external
MQTT Broker is required.
The Events that were published on the MQ Topic String are published on an MQTT Topic String.
 Default Topic String:

IBM/IntegrationBus/{{IntegrationNodeName}}/Monitoring/{{integrationServerName}}/{{messageFlowName}}

IBM/IntegrationBus/ integration_server /Monitoring/{{integrationServerName}}/{{messageFlowName}}
MQTT is an open OASIS and ISO standard lightweight, publish-subscribe network protocol that transports messages between devices.
The protocol usually runs over TCP/IP; however, any network protocol that provides ordered, lossless, bi-directional connections can
support MQTT.
Any
Questions?
Thank you

Module 16 - Event Monitoring

Uploaded by

Copyright:

Available Formats

Module 16 - Event Monitoring

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Module 16 - Event Monitoring

Uploaded by

Copyright:

Available Formats

 What is Event Monitoring:

 Why we need Event Monitoring:

Default format of monitoring topic string (for Integration Node):

Default format of monitoring topic string (for Integration Server):

 Subscription Topic string:

Default format of subscribing topic string (works for both):

Where + is single label , # is zero or n labels

Add Monitoring events:

 Enable monitoring for particular flow on Integration Node:

 Disable monitoring on Integration Node :

 Creating Monitoring Profile Policy in ACE:

mqsireportflowmonitoring -i {{HostIP}} -p {{REST_Admin_Port}} -k “{{ApplicationName}}" -f

The extracted Profile is generated as per Monitoring Event schema (location):

 Advantages of implementation by Monitoring Profile

 Disadvantages of implementation by Monitoring Profile (as a Policy)

 Default Topic String:

Default format of monitoring topic string (for Integration Node):

Default format of monitoring topic string (for Integration Node):

You might also like