integrations

IBM MQ monitoring with logstash, filebeat and Middleware Admin

You can configure IBM MQ monitoring in different ways. One is to use the json error logs of the Qmanager and forward them to the midleo.CORE (Middleware Admin) system.

There is an article for configuring the json logs: Forwarding MQ JSON error logs to Elasticsearch

In our scenario, we will use only filebeat and logstash as additional services.
You can find the configuration files in github: Midleo Agents github

When the services are installed and configurations updated, it is important to update the variables in logstash.conf file:

"srvid" => ""                             #the "uid" from /var/midleoagent/conf/agentConfig.json
"inttoken" => ""                          #internal API token taken from Middleware Admin Configuration -> Core
url => "http://web/pubapi/monalert"       #web -> the DNS name of the Middleware Admin frontend

now you can start the logstash and filebeat services.

Back in the Middleware Admin control panel -> Monitoring, you have to add the Error code for which you want to receive notifications or incidents.

In our test case:




Now we can test the monitoring.

endmqm VMQAPP
Quiesce request accepted. The queue manager will stop when all outstanding work
is complete.

In a few moments:






When you select the Application server, you can check statistics for the selected month:




Note: The configuration and installation of the products are done in Your enterprise environment by middleware specialists and system administrators. All listed products are not part of Middleware Admin installation and are third-party.