Considerations for Metric Limitations on an Event Broker Service
All monitors provide the essential information useful for monitoring the health and status of the event broker service using various objects. The integrated best practices for monitoring each event broker service determines the number of objects available.
Following our best practices for monitoring event broker services, PubSub+ Insights monitors all queue and topic endpoints for both spool and capacity utilization. In addition, Insights collects detailed metrics for a limited number of queues, topic endpoints, and bridges. These detailed metrics contain supplemental information that might be useful for detailed application utilization investigations, but are not required to monitor the health and status of the queues, topic endpoints, and bridges. Most use cases do not exceed the limits for the number of queues, topic endpoints, and bridges for which Insights collects detailed metrics for enhanced monitoring.
The table below shows the limits per event broker service object type (for example, endpoints, queues, client names, etc.) that you can monitor using your PubSub+ Insights monitors. You can use your event broker service logs to monitor event broker service objects beyond the limits listed below.
| Object type | Limits (Per Event Broker Service) |
|---|---|
| Default broker object limit per object type (bridges, caches, endpoints, etc.) | 100 per type, unless specified otherwise below. |
| Cache Instances | The first 50 cache instances in ASCII-order. |
| Client Username | 200 in alphanumeric ascending order. |
| Message VPN Bridges (Bridges) | 200 in alphanumeric ascending order. |
| Queues Detailed Metrics | The first 200 queues in ASCII-order. |
| REST Delivery Points (RDPs) | 200 in alphanumeric ascending order. |
| Topic Endpoints Detailed Metrics | The first 200 topic endpoints in ASCII-order. |