Comments (4)
That metric name does look out of date. There have been some reworks over time either from the qmgr side, or in the heuristics used to convert names into a more prometheus-friendly format.
The metrics.txt file says that it explictly lists only those metrics that are NOT provided from the topic-provided resource metrics already shown in the full product documentation. If you follow that link to the docs, you'd find "Interval total MQPUT/MQPUT1 count X" as one of the metrics. Which would get converted to ibmmq_qmgr_interval_mqput_mqput1_total_count
. One easy way to find the metric names is to stop prometheus from actually calling the collector, and then do
curl -Ss <hostname>:9157/metrics | grep "^ibmmq"
from mq-metric-samples.
Thanks for the prompt reply, apologies for my own tardiness. One of my children had a medical emergency which has taken my attention for the last few days. Unfortunately I don't see the ibmmq_qmgr_interval_mqput_mqput1_total_count metric in my output, the only ibmmq related metrics I see are:
ibmmq_qmgr_active_listeners gauge
ibmmq_qmgr_channel_initiator_status gauge
ibmmq_qmgr_command_server_status gauge
ibmmq_qmgr_connection_count gauge
ibmmq_qmgr_exporter_publications gauge
ibmmq_qmgr_log_extent_archive gauge
ibmmq_qmgr_log_extent_current gauge
ibmmq_qmgr_log_extent_media gauge
ibmmq_qmgr_log_extent_restart gauge
ibmmq_qmgr_log_size_archive gauge
ibmmq_qmgr_log_size_media gauge
ibmmq_qmgr_log_size_restart gauge
ibmmq_qmgr_log_size_reusable gauge
ibmmq_qmgr_status gauge
ibmmq_qmgr_uptime gauge
ibmmq_queue_attribute_max_depth gauge
ibmmq_queue_attribute_usage gauge
ibmmq_queue_depth gauge
ibmmq_queue_input_handles gauge
ibmmq_queue_oldest_message_age gauge
ibmmq_queue_output_handles gauge
ibmmq_queue_qfile_current_size gauge
ibmmq_queue_qfile_max_size gauge
ibmmq_queue_qtime_long gauge
ibmmq_queue_qtime_short gauge
ibmmq_queue_time_since_get gauge
ibmmq_queue_time_since_put gauge
ibmmq_queue_uncommitted_messages gauge
Given that the only config I can see being pushed to our container is
IBMMQ_CONNECTION_CHANNEL: SYSTEM.DEF.SVRCONN
IBMMQ_CONNECTION_QUEUEMANAGER: {{ .Values.global.mq.queueManager.name }}
IBMMQ_GLOBAL_CONFIGURATIONFILE: ""
IBMMQ_GLOBAL_LOGLEVEL: DEBUG
IBMMQ_GLOBAL_USEOBJECTSTATUS: "true"
IBMMQ_GLOBAL_USEPUBLICATIONS: "false"
IBMMQ_OBJECTS_QUEUES: ',!SYSTEM.,!AMQ.'
IBMMQ_OBJECTS_SUBSCRIPTIONS: '!$SYS'
IBMMQ_OBJECTS_TOPICS: '!*'
would you know if there's anything now missing in there that would cause us to be missing the metrics? Code is now old, so perhaps we're out of sync with requirements
ibmmq_queue_depth is reporting metrics, so we are generating mq traffic
from mq-metric-samples.
usePublications
should be true
from mq-metric-samples.
Thanks, that did the trick. I can now see all the metrics with the names described in your comment above. Closing this ticket, thanks for your assistance.
from mq-metric-samples.
Related Issues (20)
- MFT metrics HOT 1
- Inconsistent prometheus response from subsequent `GET /metrics` scrapes (e.g. `ibmmq_queue_depth`) HOT 3
- I need monitor two queueManagers. HOT 3
- Queue Level Metrics not visible on Prometheus dashboard HOT 2
- Listener metrics HOT 3
- panic: inconsistent label cardinality: expected 4 label values but got 3 in prometheus.Labels HOT 2
- Error collecting status: MQGET: MQCC = MQCC_FAILED [2] MQRC = MQRC_NO_MSG_AVAILABLE [2033] HOT 2
- Queue manager must be at least V9.0 HOT 1
- MQ redistributable binary missing for Linux HOT 2
- Prometheus Remote Write Support HOT 2
- ERRO[0000] Invalid value for poll interval parameter: time: invalid duration "" HOT 8
- Ibmmq_queue_depth parameter is missing after upgrading mq 9.1 to 9.3 HOT 1
- mq_prometheus: allow enable/disable status metrics separately HOT 4
- MQ certified container reference HOT 2
- [Question] Permissions needed and behaviour of exporter HOT 2
- Invalid tag does not allow compilation of monitors HOT 1
- How to collect additional MQ metrics? HOT 1
- Error faced while compiling go programs (mq_otel) HOT 3
- runtime/cgo: pthread_create failed: Resource temporarily unavailable HOT 3
- Queries related mq_otel HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mq-metric-samples.