Skip to content

Spike: Document IBM MQ broker throughput collection#8244

Closed
ramonsmits wants to merge 3 commits intomasterfrom
ibmmq-broker-throughput
Closed

Spike: Document IBM MQ broker throughput collection#8244
ramonsmits wants to merge 3 commits intomasterfrom
ibmmq-broker-throughput

Conversation

@ramonsmits
Copy link
Copy Markdown
Member

@ramonsmits ramonsmits commented May 7, 2026

Pairs with:

Summary

  • Adds an "IBM MQ" entry to the usage-reporting connection setup, with the queue manager prerequisites, multi-consumer fan-out patterns, and minimum permission set.
  • Adds an "Usage Reporting when using the IBM MQ transport" section to the ServiceControl configuration reference, documenting the three new settings:
    • LicensingComponent/IBMMQ/ConnectionString
    • LicensingComponent/IBMMQ/StatisticsQueue
    • LicensingComponent/IBMMQ/StatisticsForwardingQueue
  • Includes a runmqsc/bash script that enables STATQ on the queue manager and resets every existing user queue with an explicit STATQ override back to QMGR-inherit, so operators can opt every queue in without scripting it themselves.
  • Frames broker-side IBM MQ collection as a fallback for environments where the monitoring source isn't fully deployed, and cross-links to the existing monitoring / metrics / Monitoring-instance setup pages so readers know where to start if they want to avoid the broker path entirely.

Adds the IBM MQ section to the usage-reporting docs covering the
three new settings (LicensingComponent/IBMMQ/ConnectionString,
StatisticsQueue, StatisticsForwardingQueue), required queue manager
prerequisites, and the minimum permission set the connecting MQ user
needs.

Includes a runmqsc/bash script that enables STATQ on the queue
manager and resets every existing user queue with an explicit STATQ
override back to QMGR-inherit, so operators can opt every queue in
without scripting it themselves.
ramonsmits added 2 commits May 8, 2026 11:20
Broker-side throughput collection requires queue manager admin work
(STATQ, MAXDEPTH, additional permissions) to produce data that the
monitoring source already provides for any NServiceBus endpoint with
metrics enabled. Document the broker path as a fallback for
environments where monitoring isn't fully deployed, rather than the
default recommendation.
Cross-reference the existing monitoring + metrics + Monitoring
instance documentation from the IBM MQ usage section so readers
arriving at the IBM MQ broker setup steps can see how to configure
the monitoring path instead.
@ramonsmits ramonsmits changed the title Document IBM MQ broker throughput collection Spike: Document IBM MQ broker throughput collection May 8, 2026
@ramonsmits ramonsmits closed this May 8, 2026
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

Successfully merging this pull request may close these issues.

2 participants