Emergency Incident Response
Platform down, apps failing to stage, a foundation that won't deploy, or a data service cluster offline. A senior engineer joins a live bridge within 15 minutes with access to diagnose — not a ticket acknowledgement.
VMware Tanzu Support
Last reviewed by Tyler Eastridge
AceMQ is Broadcom's VMware Expert Advantage Partner of the Year for the Americas, 2025. We support Tanzu Application Service, Tanzu Kubernetes Grid, and the Tanzu data services — including RabbitMQ, GemFire, Greenplum, and Postgres — plus the Broadcom licensing and entitlement problems that block your upgrades. Every ticket reaches a named senior engineer.
Planning a build, upgrade or migration instead? See AceMQ VMware Tanzu consulting and services.
Customers




Partners


Incident Triage
These are real symptoms from real VMware Tanzu production environments — and the first thing our engineers check when one comes in.
| Symptom you're seeing | What we check first | Typical resolution |
|---|---|---|
| Tanzu Application Service app instances crash-looping after a platform upgrade | The stack and buildpack versions the app was staged against. A cflinuxfs upgrade changes the rootfs beneath apps that were never restaged, so binary dependencies compiled against the old stack fail at start with errors that point nowhere useful. | 1-3 hours |
| BOSH deploy hangs on an instance group that never reports running | The failing job's pre-start and monit output on the VM itself, plus IaaS-level quota and placement. A vSphere resource pool at capacity or an exhausted IP block stalls a deploy in a way the BOSH task log describes only as a timeout. | 2-4 hours |
| Tanzu downloads or upgrades blocked — entitlement not recognized | Which Broadcom site account the entitlement actually sits under after the portal migration. Perpetual VMware entitlements, subscription SKUs, and support contracts frequently land on separate accounts, so the person doing the download has no visible entitlement to a product you own. | Same day |
| Tanzu RabbitMQ Operator reconcile loop — cluster never reaches ready | Operator logs against the CRD version and the StatefulSet's current state. An immutable field changed in the custom resource, or an operator upgraded ahead of its CRDs, leaves reconcile retrying forever while the cluster sits in a partial state. | 1-3 hours |
| Broker latency spikes on vSphere with guest CPU showing idle | CPU ready time and co-stop at the host level, not in-guest metrics. An oversubscribed cluster or an oversized vCPU count makes the VM wait for scheduling, which appears as broker latency and network timeouts while every in-guest dashboard looks healthy. | 2-4 hours |
| TKG workload cluster stuck in an incomplete upgrade or provisioning state | Cluster API controller logs on the management cluster and the machine objects that never went Ready. A stale or expired node image template, or a cloud-provider credential that rotated, halts the rollout mid-flight with healthy-looking control plane nodes. | 2-4 hours |
| Service bindings fail after a Tanzu data services tile upgrade | Broker catalog and plan GUIDs against what the marketplace still advertises. A plan removed or renamed in the new tile version leaves existing bindings orphaned, so apps restart into a missing credential rather than a clear error. | Under 2 hours |
| License compliance flagged in an audit for VMs you thought were covered | Core counts and cluster boundaries against the current Broadcom subscription model. Post-acquisition licensing counts differently than the perpetual model most estates were sized under, and host-level changes made after renewal are the usual source of an unexpected gap. | Same day |
Resolution times reflect typical VMware Tanzu engagements under an active AceMQ support contract. Every P1 closes with a written root-cause analysis.
What's Included
No add-on pricing for incidents. No per-ticket charges. One contract covers the whole surface.
Platform down, apps failing to stage, a foundation that won't deploy, or a data service cluster offline. A senior engineer joins a live bridge within 15 minutes with access to diagnose — not a ticket acknowledgement.
Every P1 closes with a written RCA: what failed, why, the fix applied, and the tile, manifest, or platform change that prevents recurrence. Delivered as standard, not on request.
As Expert Advantage Partner of the Year for the Americas, we escalate into Broadcom engineering through partner channels when a defect is genuinely upstream — rather than leaving you to argue severity with a support portal.
Portal migrations, split site accounts, subscription conversions, and core-count questions. We untangle which entitlement covers which product and get the download or support contract working again.
Tanzu RabbitMQ, GemFire, Greenplum, Postgres, Valkey, and Spring. Cluster operations, operator behavior, upgrade paths, and the tuning that platform-level support does not reach.
Foundation upgrade sequencing, TKG version paths, TAS to Kubernetes migration where that's the right call, and honest advice about the parts of your Tanzu estate worth keeping.
Why AceMQ
Americas, 2025. That recognition comes from delivered outcomes on real Tanzu estates, and it gives us partner-level escalation into Broadcom engineering when an issue is genuinely a product defect rather than a configuration problem.
The same senior engineers stay on your account. They know your foundation layout, your tile versions, and your vSphere topology — so a P1 call starts with diagnosis, not twenty minutes of you explaining your environment.
You reach a senior Tanzu engineer directly by phone, email, or Slack. No help desk collecting information to pass along, no case that sits in a queue overnight, and no escalation approval standing between you and someone who can fix it.
We are the number one RabbitMQ partner globally with direct access to the RabbitMQ core team. For estates where Tanzu RabbitMQ carries production traffic, that is a materially different level of support than generalist platform coverage.
Engineers across 26+ countries and every time zone. Your 3am foundation incident is someone's mid-afternoon — no overnight skeleton crew, no waiting for a region to wake up.
The Broadcom transition moved entitlements, changed metering, and split site accounts. Much of what blocks Tanzu teams now is commercial rather than technical, and we resolve both instead of pointing you at a different vendor contact.
Cloud, Kubernetes, bare metal, hybrid, and air-gapped — including environments where you can't give us outbound network access.
Escalation Path
Every tier reaches a senior VMware Tanzu engineer. There is no tier-1 triage layer to get through.
P1 escalation path
A replay of one P1, from the first page to the written root-cause analysis
15-minute P1 response, 24/7.
A response time, not a resolution time.
P1 opened, on-call engineer paged
Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.
Senior engineer on your bridge
A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.
Specialists across the stack join
When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.
Written root-cause analysis
Root cause, the fix applied and the prevention steps, delivered after every P1.
Pricing
AceMQ VMware Tanzu support contracts typically run $24,000–72,000 a year, depending on SLA level, scope (number of clusters or nodes, and environments) and deployment (self-managed, cloud-managed or Kubernetes).
| What moves the price | How it changes the contract |
|---|---|
| SLA level | Business-hours cover costs less than 24/7 cover with a 15-minute emergency response. |
| Scope | More clusters or nodes, and more environments, make a larger contract. |
| Deployment | Self-managed, cloud-managed and Kubernetes estates need different amounts of hands-on work. |
Covering several technologies under one contract, for example RabbitMQ, Kafka and Redis, earns an aggressive discount.
Support In Practice
Representative engagements showing how these incidents get diagnosed and closed under an AceMQ support contract.
Medical Certification Organization
Developing a CVE patching strategy and upgrade path for RabbitMQ 3.12 deployments in a regulated medical certification environment, evaluating community 4.x versus commercial 3.13 LTS options.
European Logistics Group
Clearing the deprecated APIs, operator versions and storage drivers that had kept production Kubernetes clusters several minor versions behind.
Global Consumer Goods Manufacturer
Diagnosing queries that queued and never started during the nightly ETL window, and spill files that filled segment disks, then separating workloads with resource queues and memory limits.
Support options
AceMQ offers VMware Tanzu support in four tiers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident management for platforms your team runs, proactive monitoring that catches upgrade, entitlement and capacity problems first, managed Tanzu on your own infrastructure, and fully managed Tanzu on AceMQ infrastructure. Tanzu Application Service, Tanzu Kubernetes Grid and the Tanzu data services are covered.
You run it, we back you up
Best for: Teams that run VMware Tanzu themselves and need senior escalation cover.
You run it, we watch it with you
Best for: Teams that want fewer incidents, not just faster ones.
We run it in your cloud or data centre
Best for: Regulated or compliance-heavy estates that cannot move off their own infrastructure.
We host it and run it, as a service
Best for: Teams that want VMware Tanzu without owning any of its operations.
| Who does what | Tier 1 24/7 support | Tier 2 Proactive monitoring | Tier 3 Managed, your infrastructure | Tier 4 Fully managed by AceMQ |
|---|---|---|---|---|
| Who runs VMware Tanzu day to day? | Your team | Your team, with AceMQ reviews | AceMQ | AceMQ |
| Where does it run? | Your infrastructure | Your infrastructure | Your cloud account or data centre | AceMQ infrastructure |
| 24/7 incident response | 15-minute P1 response | 15-minute P1 response | 15-minute P1 response | 15-minute P1 response |
| Health checks and CVE alerts | On request | Scheduled | Included | Included |
| Patching and upgrades | Your team, AceMQ advises | Planned with AceMQ | Done by AceMQ | Done by AceMQ |
| Monitoring and on-call | Your team | Your team | AceMQ | AceMQ |
| Data, keys and accounts | Yours | Yours | Yours | Your data, hosted by AceMQ |
Every Tier can start as an ad hoc engagement or an annual partnership, and you can move up or down a Tier as your team changes.
One partner for VMware Tanzu
Support is one part of what AceMQ does for VMware Tanzu. The same engineers deliver consulting, health checks, migrations and end-of-life cover, and support the systems that usually run next to it.
Our Tanzu support covers 24/7 emergency incident response with a 15-minute SLA, root cause analysis on every P1, upgrade and migration planning, Tanzu data services support, vSphere performance diagnosis where it affects platform workloads, and Broadcom licensing and entitlement resolution. Every ticket is handled by a named senior engineer assigned to your account. There is no tier-1 triage layer and no per-incident charge.
AceMQ was named VMware Expert Advantage Partner of the Year for the Americas in 2025. Practically, it means two things for a customer. Our engineers hold current Broadcom certification across the Tanzu portfolio rather than legacy VMware credentials, and we have partner-level escalation into Broadcom engineering — so when an issue is a genuine product defect, we route it through a channel you do not have direct access to.
Yes, and it is now one of our most common opening tickets. The move to Broadcom's portal relocated entitlements, changed how cores are counted, and frequently split perpetual licenses, subscription SKUs, and support contracts across different site accounts. The usual symptom is a download or support case that says you are not entitled to a product you demonstrably own. We work that through the partner channel rather than leaving you in a portal support queue.
Yes, both, including the estates that run them side by side. For TAS that means BOSH deploys, tile upgrades, buildpack and stack changes, Diego cell capacity, and app staging failures. For TKG it means Cluster API behavior, management and workload cluster upgrades, node image templates, and the CNI and CSI layers underneath. We also advise on TAS to Kubernetes migration when the workload genuinely warrants it — and say so when it does not.
It is, and it is our strongest area. AceMQ is the number one RabbitMQ partner globally with direct access to the RabbitMQ core team. We support Tanzu RabbitMQ on both the OVA and Kubernetes deployment models, covering Cluster Operator reconcile behavior, quorum queue membership, TLS and Erlang distribution, and upgrade paths between Tanzu RabbitMQ versions. Many customers start with us for RabbitMQ and expand to the rest of the Tanzu estate.
P1 emergencies — platform down, apps failing to start, a data service cluster offline — get a 15-minute first response with a senior engineer joining a live bridge. P2 critical issues are 1 hour, P3 high-priority 4 hours, and P4 standard questions next business day. These are contractual, not best-effort targets.
Yes. AceMQ works on VMware Tanzu in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual partner engagement that covers 24/7 support, proactive reviews and named engineers. Many teams start ad hoc and move to an annual partnership once the first engagement is done.
Every AceMQ proposal is tailored to your requirements: your VMware Tanzu environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how VMware Tanzu is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.
Let's talk
Whether your foundation is down tonight, an entitlement is blocking an upgrade, or you want a second opinion on your Tanzu roadmap, AceMQ staffs every engagement with a named senior engineer. Quote requests answered within 1 hour.
Production incident right now?Email a VMware Tanzu Architect
Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.
305-204-2607info@acemq.comPrefer to talk now? Call us directly or use the consultation tab to find a time that works.