RabbitMQ Ask AceMQ Live Open Q&A Forum

Ask the RabbitMQ Experts, brought to you by AceMQ, the featured authorized partner of RabbitMQ. Bring any RabbitMQ question and get a 5-Minute answer from our SMEs and RabbitMQ's core team. If your inquiry needs more time, we'll guide you through the right Support Path.

hero image

How it Works

  • Submit

    Submit

    Post your question ahead of time in our monitored forum. Add version, topology, and a short description for prioritization.

    Submit a Question
  • Attend Live

    Attend Live

    Join the biweekly session to hear concise, practical answers and learn from peers’ scenarios across the RabbitMQ ecosystem.

    Add to Calendar
  • Continue

    Continue

    If a topic needs deeper work, we’ll route you to paid support or schedule a focused session with our engineers.

    Contact Support

What can I ask?

Operations & Resilience

  • HA/DR, quorum queues, partitions
  • Monitoring & alerting patterns
  • Zero‑downtime upgrades

Performance & Scale

  • Throughput bottlenecks
  • Throughput bottlenecks
  • Storage and I/O tuning

Architecture & Licensing

  • Tanzu RabbitMQ roadmap
  • Feature parity & supportability
  • Migration & EOL planning

Need more than a 5-minute answer? Talk to our RabbitMQ engineers.

Contact Us

Next live Session

Picture of the author

Sunday, Nov 8 — 12:00 PM ET

Open forum — bring your questions. We’ll prioritize items with enough context to answer in ~5 minutes.

Can’t make it? We’ll post the next date shortly, or contact us to schedule a private session.

Picture of the author

Overflow & follow‑ups

If your question runs long, we’ll invite you to continue via paid support. Questions not reached within the 1–2 hour window get the option to schedule a focused discovery call to discuss support and services. or to be answered in the next QA session

Submit a question

Full Name

Email Address

Question

RabbitMQ Version

Timezone

Submission tips

  • Keep the core question scoped to a 5‑minute answer.
  • Add brief context (version, cluster size, queue type, symptoms).
  • Exclude secrets, keys, or proprietary data.
  • For deep dives, ask for a private follow‑up.

When to move to support

  • Repeated incidents or Sev‑1/Sev‑2 events
  • Upgrades, migrations, or DR testing
  • Performance tuning and load modeling
  • Compliance and security reviews