ibm-messaging / mq-metric-samples

IBM® MQ metric gathering client samples
Apache License 2.0
58 stars 70 forks source link

Problems getting QMGR monitored with lots of objects (more than 1200) #88

Open manwe81 opened 2 years ago

manwe81 commented 2 years ago

QMGR Version 9.1.0.9 we use the latest mqprometheus build for 9.1.x we set max handles to 10240 we have the following config and run the deamon as client:

queues="VERS.,EPZ.,AZL.,HD.,GOLV.,FN.,DMS.,CMD.,CLIENT.,PUBLIC.,READ.,AKO.,GELD.,DBC.,VAUST.,IMMO.,ALF.,GGF.,COM.,ESB.,VGT.,APL.,DE.,SYSTEM.,ADMIN.,TEST.,MQ*"

An alternative is to have a file containing the patterns, and named

via the ibmmq.monitoredQueuesFile option.

Do similar for channels

channels="2,MQ,CL*"

See config.go for all recognised flags

ARGS="-ibmmq.queueManager=$qMgr" ARGS="$ARGS -ibmmq.monitoredQueues=$queues" ARGS="$ARGS -ibmmq.monitoredChannels=$channels" ARGS="$ARGS -ibmmq.monitoredTopics=#" ARGS="$ARGS -ibmmq.monitoredSubscriptions=*" ARGS="$ARGS -rediscoverInterval=1h" ARGS="$ARGS -pollInterval=600s" ARGS="$ARGS -ibmmq.httpListenHost=xxxx.xxxx.xxxx.xxxx" ARGS="$ARGS -ibmmq.httpListenPort=$port" ARGS="$ARGS -ibmmq.tzOffset=1h" ARGS="$ARGS -ibmmq.replyQueue=ADMIN.PROMETHEUS.MON.AGENT" ARGS="$ARGS -ibmmq.queueSubscriptionSelector=put,get" ARGS="$ARGS -ibmmq.useStatus=true" ARGS="$ARGS -log.level=error"

we see just filling up the reply Queues and that some messages are processed but seem to be dropped from the prometheus server. Is there someone around with the same problem and/or got it working with a huge amount of queues/channels? Thanks in advance for any hint.

WockaFlockaRist commented 2 years ago

my team is experiencing the same thing in our testenvironments.