Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Channel counts #129

Closed
salapat11 opened this issue Nov 11, 2019 · 2 comments
Closed

Channel counts #129

salapat11 opened this issue Nov 11, 2019 · 2 comments

Comments

@salapat11
Copy link

Mark,

Will it be possible to add a metric for channel count for each channel (that counts the channels that are running)? Currently we measure the count using the count query after the samples are collected. But it would be more useful if we can have a metric for that.

Also, a metric for max channel count on a queue manager.

@ibmmqmet
Copy link
Collaborator

ibmmqmet commented Nov 13, 2019

Prometheus is the best way to count metrics. It can do various groupings automatically.
For example,

count by (channel,qmgr) (ibmmq_channel_status)

gives a graph of the number of active channels of each name for each qmgr. So you can see how many SYSTEM.DEF.SVRCONN instances are going.

I could consider adding MaxChannels for z/OS as it is available via MQINQ. But not for Distributed platforms as the corresponding controls are in the qm.ini file, not readily accessible in a program.

@salapat11
Copy link
Author

Mark, thanks for the response. Yes. I am using the same metric but given the number of samples for some queue managers, it is taking a long time to return the query.

ibmmqmet added a commit that referenced this issue Dec 6, 2019
- ibmmq - Add qmgr variant of the CB function for event handlers (#128)
- mqmetric - Add MaxChannels/MaxActiveChannels for z/OS (#129)
- mqmetric - Add MaxInst/MaxInst for SVRCONN channels (ibm-messaging/mq-metric-samples#21)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants