Message Broker Operations

Operations Scope

Start with the operator runbooks when local broker startup, route health, metrics exposure, audit visibility, diagnostics collection, storage inspection, quota rejection, replication status, or support details need a reviewed path.

Operations Pages

• 

  Available

  Message Broker operator runbooks

  Health, metrics, audit, diagnostics, storage inspection, quota rejection, replication status boundaries, and support details.

• 

  Available

  Cross-product observability and audit guide

  Use shared health, metrics, audit, logs, diagnostics, support bundle details, and privacy-safe handoff practices before escalation.

• 

  Available

  Troubleshooting index

  Start with symptom-oriented Message Broker and cross-product entries before opening the exact product runbook.

• 

  Available

  Support bundle and privacy page

  Use support bundle contents, exclusions, redaction expectations, and approval checks before sharing broker evidence.

• 

  Available

  Message Broker HTTP reference

  Check route permissions, auth behavior, error responses, page limits, metrics, audit, storage, and replication status routes.

• 

  Available

  Message Broker CLI and SDK reference

  Use lifecycle flags, local and remote CLI diagnostics, and Rust SDK boundaries for operator-facing checks.

• 

  Available

  Message Broker known limits

  Keep replication outcomes, Kafka compatibility, identity-provider validation, remote CLI writes, and support wording product-bound.

Operations Boundaries