search

ibm-messaging / mq-metric-samples

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

Queries related mq_otel #302

Closed rputtur closed 1 month ago

rputtur commented 2 months ago

Dear Team,

Thanks a lot for developing and sharing the mq_otel repository and instructions to set it up. We have setup mq_otel and we are able to gather and send the mq metrics to OTEL collector and from there to Prometheus/Grafana. In our test setup we have MQ, mq_otel, OTEL Collector, Prometheus and Grafana are setup on the same machine. We have the below queries kindly request you to guide us.

  1. Can mq_otel be used along with monitoring tools like ITM. We are asking this doubt as we saw "Warning: Data from 'RESET QSTATS' has been requested." line in config.go under mq_otel. Can RESET QSTATS by mq_otel hamper the data collection by ITM?

  2. Can mq_otel be used to send the MQ metrics to OTEL Collector running on any other server, provided that grpc port is open on that server? Or OTEL collector needs to be running on every server were mq_otel is configured/running

  3. We tried importing the Queue_Manager_Status.json[given in mq_otel repository] in Grafana[version 10.4.2]. It's showing some data on the dashboard but at some places we are seeing errors related to angular js deprecation warning. We are new to Angular/React and learning them. We tried setting angular_support_enabled = true in grafana configurations but those errors are still there. kindly let us know how it can be fixed to see an error free dashboard.

Thank you once again, Ravi

ibmmqmet commented 1 month ago
  1. Yes. RESET QSTATS can interfere with ITM because that is the only mechanism ITM uses to get some metrics. On Distributed platforms it's not really necessary to use RESET QSTATS with this package because other equivalent metrics are available through different routes. But it can be problematic when running against a z/OS qmgr. That's why there's a config option to disable using that command.
  2. The OTEL Collector can be running anywhere that's network-accessible. Setting up TLS options might be more important then, but in theory you can have a single central Collector aggregating all the data from multiple mq_otel instances.
  3. Some of the example dashboard elements use "old" forms of the Grafana panels. My systems use Grafana 9, and they work fine, but v10 has apparently started to deprecate those older versions because they are getting rid of Angular. The panels from the sample would have to be migrated to use the newer panel styles, and potentially tweaked further. The example is purely that - you might be better off creating your own dashboard from scratch to show the data you think is important. I do plan on updating some of the samples at some point, but it's not going to be immediate.
rputtur commented 1 month ago

Thanks a lot for detailed answer for our every doubt. Really appreciate it.

Thank you once again Ravi