Open Aeryes opened 2 months ago
Another question I would like to ask is should the script be ran in its own queue manager or should it be run inside my other queue managers that I wish to monitor. Its not very clear in the docs where I should run this when not using docker.
I've no real idea about the pthread issue. Google searches suggest it's often to do with a ulimit problem in your environment.
Each instance of the monitor will check on one queue manager. Sop it's usually best, where possible, to run it as a service alongside the queue manager you are monitoring. Each queue manager would have its own service and configuration,
If running the queue manager in a container, I'd prefer to add the monitor into that container. If that's not possible, then you can run it in its own container, connecting as a client. But then you probably have to coordinate the lifecycles of both the qmgr and the monitor containers.
MQ Go Version : v5.5.4 mq-metric-samples-5.5.4.1 go version go1.22.2 linux/amd64
I am trying to install the mq_prometheus in an air gapped env.
File locations (All moved from /home/myuser/gowork/mq-metrics-samples-5.5.4.1/ after building with go): /usr/local/bin/mqgo/mq_prometheus/mq_prometheus.sh /usr/local/bin/mqgo/mq_prometheus/mq_prometheus.mqsc /usr/local/bin/mqgo/mqprometheus/ - Contains all the files from the mqprometheus folder in the repo. /usr/local/bin/mqgo/compiled/mqprometheus - File built with go build.
I built from /home/myuser/gowork/mq-metric-samples-5.5.4.1/mq-metrics-samples-5.5.4.1 using
MQSC File Contents:
SH File Contents:
I have a queue manager that I want to monitor so I run: runmqsc QM_PROMETHEUS<"/usr/local/bin/mqgo/mq_prometheus/mq_prometheus.mqsc"
After running this and checking the error log located at /var/mqm/errors/mq_prometheus.err I get the following:
and sometimes I see this instead:
How can I resolve these issues?