TDMQ for Apache Pulsar
- Release Notes and Announcements
- Product Introduction
- Purchase Guide
- Pricing Overview
- Pro Cluster
- Getting Started
- Using SDK to Send and Receive Normal Messages
- Developer Guide
- How It Works
- Operation Guide
- Cluster Management
- Monitoring and Alarms
- Permission Management
- Pulsar Instance Permission Management
- Cross-Region Replication
- Practical Tutorial
- API Documentation
- Making API Requests
- Cluster APIs
- Namespace APIs
- CMQ Management APIs
- Environment Role APIs
- TDMQ for RabbitMQ APIs
- RocketMQ APIs
- TDMQ for RocketMQ APIs
- Production and Consumption APIs
- SDK Documentation
- Apache Pulsar TCP Protocol
- General References
DocumentationTDMQ for Apache PulsarOperation GuideMonitoring and AlarmsMonitoring and Alarm Practices
Monitoring and Alarm Practices
Last updated: 2025-04-01 14:26:16
Based on the professional cluster specifications and usage limits provided by the product, the following are some recommended metrics and alert items for your reference.
Core Metrics and Impact
Dimension | {alarm item} | Configuration Suggestion | Limit Exceeded Impact |
Topic | Message backlog used quota percentage | 80% | Sending failure will occur after exceeding the limit, and the client will repeatedly reconnect. |
| Percentage of used quota for message production number | 80% | The default single partition is 5000 TPS. After exceeding the limit, the server will return with a delay, and the sending duration of the client will increase. |
| Percentage of used quota for message production traffic | 80% | The default single partition is 40 Mbps. After exceeding the limit, the server will return with a delay, and the sending duration of the client will increase. |
| Percentage of used quota for message consumption count | 80% | The default single partition is 5000 TPS. After exceeding the limit, it may be due to the push rate limit of messages, resulting in message backlog. |
| Percentage of used quota for message consumption traffic | 80% | The default single partition is 40 Mbps. After exceeding the limit, it may be due to the push rate limit of messages, causing message backlog. |
| Number of Producers | 800 | The upper limit of the number of producers for a single default partition is 1000. After exceeding the limit, new producers cannot be created. |
| Number of Consumers | 1500 | The upper limit of the number of consumers for a single default partition is 2000. After exceeding the limit, new consumers cannot be created. |
Subscription | Percentage of used quota for number of unconfirmed messages | 80% | The default is 5000 for a single subscription and a single partition. After exceeding the limit, the server will stop pushing messages until the client confirms completion of unacknowledged messages. |
| Number of Consumers | 800 | The upper limit of the number of consumers for a single default subscription in a single partition is 1000. After exceeding the limit, new consumers cannot be created. |
Instance | [Pro Edition] Fixed storage utilization of professional cluster | 80% | Sending failure will occur after exceeding the limit, and the cluster cannot be written. |
| [Pro Edition] TPS usage percentage of Pulsar cluster | 80% | Exceeding the limit can lead to high-load running of the cluster, posing a stability risk. |
| [Pro Edition] Limited number of tenant throttling write requests per minute | 1 | After traffic throttling occurs, the server will return with a delay, which will increase the sending duration. |
Was this page helpful?
You can also Contact Sales or Submit a Ticket for help.
Yes
No