mit einem Klick
robustmq-metrics
// Designs and implements minimal, high-value metrics for RobustMQ services and dashboards. Use when the user asks to add metrics, improve observability, or update Grafana panels for core processing pipelines.
// Designs and implements minimal, high-value metrics for RobustMQ services and dashboards. Use when the user asks to add metrics, improve observability, or update Grafana panels for core processing pipelines.
7×24 chaos testing for RobustMQ. Injects broker-kill and network-delay faults, validates SDK client resilience across Python/Go/Rust/Java, and publishes a Markdown + JSON report to GitHub after each run.
Audit and update the HTTP API documentation under docs/zh/Api/ and docs/en/Api/ against the actual route definitions in src/admin-server/src/. Uses path.rs as the single source of truth. Fixes wrong URI prefixes, non-existent routes, wrong request/response fields, and syncs the English docs to match the Chinese ones.
Complete step-by-step guide for implementing a new protocol Broker in RobustMQ. Use when the user asks to add a new broker, implement a new protocol, or scaffold a new broker crate.
Deep analysis and iterative fixing of a Rust source file. Finds logic errors, lock/concurrency issues, and simplification opportunities, then fixes them one by one until the file is clean.
Implements new RobustMQ MQTT connector integrations end-to-end using project conventions. Use when the user asks to add, implement, or support a new connector type such as webhook, opentsdb, clickhouse, influxdb, cassandra, mqtt bridge, or protocol-compatible targets.
Create GitHub issues for the RobustMQ project. Use when the user asks to create an issue, file a bug, propose a feature, or track a task.
| name | robustmq-metrics |
| description | Designs and implements minimal, high-value metrics for RobustMQ services and dashboards. Use when the user asks to add metrics, improve observability, or update Grafana panels for core processing pipelines. |
Add observability with minimal but complete coverage of a target pipeline:
Do not over-instrument. Prefer compact metrics that support operations and debugging.
Cover chain, not everything:
Always include count and latency for processing path.
Label policy:
result, strategy, protocol)topic, error_message, payload-derived labelsNaming:
mqtt_, raft_, handler_)_total_ms_upAdapt this template to the target module:
<module>_messages_processed_success_total{...}<module>_messages_processed_failure_total{...}<module>_process_duration_ms{...} (histogram)<module>_retry_total{...,strategy} (if retry exists)<module>_terminal_total{...,result} (discard/dlq/drop etc., if applicable)<module>_critical_step_failure_total{...} (read/write/commit/etc.)<module>_up{...} (gauge)Define metrics in src/common/metrics
Insert runtime instrumentation
Fix call sites impacted by signature changes
Validation
cargo check for impacted cratesAfter metrics are added, decide whether to update grafana/robustmq-broker.json:
When updating dashboard:
Return: