If companies have a central system monitoring based on Prometheus/Grafana, they want to integrate SwiftMQ metrics here
as well. The
Prometheus Metrics App provides metrics of the SwiftMQ router network connected to Flow Director through
a REST interface in native Prometheus format.
Prometheus can be configured to pull (resp. scrape) this data so that it can be displayed in Grafana dashboards:
The default user is
admin with the password
changeme. After login please change this password.
Click on the
Flow Orchestrator menu.
RESTHandler flow collects the outputs from all activated probes on all connected routers and provides them
as single result on each REST request from Prometheus.
This flow must be activated on a single router node (where Flow Director is connected to). It must not be started on multiple nodes!
Click on the
rest tag which selects this flow:
Then select the cell of the router and click on
The flow is now receiving data and is ready to serve REST requests.
Start the Probe Flows
Probe flows collect single metrics. These flows must be activated on all nodes that should be observed.
rest tag and select the
probetag. Then select all flows and all nodes, click on
Set x flows on y routers
SET and the flows will be activated on all nodes:
The flows are now producing metrics.
To test the output, open a browser and point it to
You should see the metrics of all nodes in Prometheus format:
Single Queue Metrics
In addition to the preconfigured probe flows it is also possible to create metrics for single queues. Base for this
is a template flow
SingleQueueProbeTemplate which is tagged as
Say, we want to monitor queue
testqueue. First of all we need to create a copy of the template flow:
Give it a name:
Then edit this copy which opens the flow editor:
We now need to set the values of 2 flow parameters:
clicontext(the CLI context of the queue)
queuename(the name of the queue)
In flow editor click on the flow parameter button (upper right corner):
A panel to edit the flow parameters opens:
(You need to push the
+ button for each change)
Result should look like:
Now go back to the `Flow Orchestrator' and deploy/activate the flow on the node where the queue is located:
After a few seconds you'll notice the new metrics in the REST output:
prometheus.yml add this configuration under the
Note: If you run Prometheus as docker container together with Flow Director on your localhost, you'll need to
specify the IP address of the local host instead of
You should see all metrics from Flow Director here: