Emergency Incident Response
Monitoring blind during an incident, agents dark on a host group, or telemetry missing after a change. With response targets from 15 minutes, by plan, a senior engineer joins the bridge.
Independent Dynatrace support
AceMQ supports Dynatrace estates 24/7: OneAgent rollouts that leave hosts without services, OpenTelemetry data that does not arrive as expected, and the messaging and database platforms that feed the same view. Dynatrace still owns product defects, platform availability and licensing.
24/7 Dynatrace support with response targets from 15 minutes, by plan.
Customers




Partners


Incident Triage
These are real symptoms from real Dynatrace production environments — and the first thing our engineers check when one comes in.
| Symptom you're seeing | What we check first |
|---|---|
| Host appears in Dynatrace, its services do not | Whether the processes were running when OneAgent was installed. OneAgent does not inject into processes that are already running, so they must be restarted. Then confirm the monitoring mode (Full-Stack, Infrastructure or Discovery) matches what you expect to see. |
| A new host never reports after install | The API token used at install and the network path. The token is shown once during setup, so a lost token means generating a new one, and the host must be able to reach Dynatrace over SSL. |
| OpenTelemetry data is sent but nothing arrives | Whether the pipeline goes straight to the Dynatrace OTLP API over OTLP/HTTP or through a collector, then the collector's exporter endpoint and which signals (traces, metrics, logs) it actually forwards. |
| A service shows twice, or counts are doubled | A mixed OneAgent and OpenTelemetry setup on the same workload. Pick one source per service, or confirm how the two are meant to be combined, before touching alert rules. |
| Sessions and Session Replay missing for an app instrumented with OpenTelemetry | Dynatrace documents that real user monitoring features such as sessions and Session Replay are not available through OTLP alone. The gap is the signal type, not a misconfigured collector. |
| Queue depth, consumer lag or database signals are not in the same view | Which signals RabbitMQ, Kafka or PostgreSQL already expose, how they reach Dynatrace, and whether the metric names and units match what the dashboards expect. |
| Alerts fire on broker or database conditions nobody acts on | The thresholds against the platform's real behaviour. A static limit copied from another environment pages for normal peaks and stays quiet for the failure that matters. |
| A rollout stalls at scale across many hosts | The install method and restart plan per host group, not the agent. Stalls usually trace to how the rollout was sequenced and what had to restart, which a defect ticket does not address. |
Every P1 closes with a written root-cause analysis.
Deployment coverage
| Setup | What AceMQ covers | What Dynatrace covers | Excluded |
|---|---|---|---|
| OneAgent on hosts and VMs | Rollout plan, monitoring mode, restarts, tokens, network paths | The agent, its code modules and documentation | Host and OS faults |
| OneAgent on Kubernetes | Rollout sequencing, restarts, coverage gaps across namespaces | The agent and the product's Kubernetes integration | Control-plane faults |
| OpenTelemetry via collector | Collector config, pipelines, signals forwarded, duplicate sources | The OTLP API and its collector distributions | Upstream SDK defects |
| Direct OTLP/HTTP ingest | Endpoint, token and signal checks from your side | The OTLP API | Application instrumentation code |
| Messaging and database integrations | Bringing RabbitMQ, Kafka and PostgreSQL signals into the view, thresholds | The product's own integration points | The platforms' own faults, unless AceMQ also supports them |
| Licensing and billing | Not covered | Platform Subscription terms and rate card | Vendor licensing advice |
Support options
Dynatrace publishes two support tiers (dynatrace.com/support, read 17 Nov 2026).
What's Included
No add-on pricing for incidents. No per-ticket charges. One contract covers the whole surface.
Monitoring blind during an incident, agents dark on a host group, or telemetry missing after a change. With response targets from 15 minutes, by plan, a senior engineer joins the bridge.
Install method, monitoring mode, process restarts, tokens and network paths: the first things checked when a host shows up but its services do not.
Collector design and pipeline debugging on your side of the OTLP API: which signals leave, which arrive, and where OneAgent and OpenTelemetry overlap.
RabbitMQ, Kafka and PostgreSQL expose the signals worth watching. We help bring them into the same view and set thresholds that fit them.
Thresholds, noise and routing reviewed against real behaviour, so one failure pages one team once.
When the cause is in the product, we assemble the evidence and work the case with you and Dynatrace, instead of arguing severity alone.
Why AceMQ
The same senior engineers stay on your account, so a P1 opens with diagnosis instead of orientation.
You reach a senior engineer directly by phone, email or Slack. No help desk collecting details to pass along.
Dynatrace owns the platform and supports it. Your agents, pipelines, integrations and alerting design sit on your side of that line, which is the side we work on, alongside vendor support, not instead of it.
The same engineers run your brokers and databases, so a signal from RabbitMQ or PostgreSQL gets read by someone who knows what it means.
Round-the-clock coverage for customers in 26+ countries. Your 3am incident is someone's mid-afternoon.
Platform Subscription terms and the rate card are between you and Dynatrace. AceMQ gives no vendor licensing advice and says so up front.
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 Dynatrace engineer. There is no tier-1 triage layer to get through.
Response targets by plan; your contract sets the tier.
Pricing
AceMQ Dynatrace 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).
Prices are in US dollars (USD). Response targets from 15 minutes, by plan, 24/7. Quote requests answered within 1 hour. Covering several technologies under one contract earns an aggressive discount.
Support options
AceMQ offers Dynatrace support in layers, each handing more of the day-to-day work to AceMQ: 24/7 support and incident response for estates your team runs, proactive review of OneAgent rollouts, OpenTelemetry pipelines and alert thresholds, and help running the messaging and database platforms that feed Dynatrace. Product defects, platform availability and licensing stay with Dynatrace in every layer.
You run it, we back you up
Best for: Teams that run Dynatrace 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 Dynatrace without owning any of its operations.
One partner for Dynatrace
Support is one part of what AceMQ does for Dynatrace. The same engineers deliver consulting, health checks, migrations and end-of-life cover, and support the systems that usually run next to it.
Dynatrace supports its own platform on two published tiers, Standard and Enterprise. AceMQ provides independent support around a Dynatrace estate, covering integrations, OneAgent rollout and OpenTelemetry ingest, and works the escalation to Dynatrace when the cause is in the product. AceMQ costs $24,000 to $72,000 a year (USD), set by SLA, scope and deployment.
Dynatrace's Enterprise tier is 24/7/365; Standard is business hours, Monday to Friday. AceMQ's support is 24/7 across Americas, EMEA and APAC, with response targets from 15 minutes, by plan.
No. Only Dynatrace can patch its product or run its platform. Independent support covers the work around it, and many estates use both.
Often because the processes were already running when OneAgent was installed. OneAgent does not inject into running processes, so restart them, then check the monitoring mode and the network path.
Yes. Dynatrace ingests traces, metrics and logs over OTLP/HTTP, directly or through a collector. Check which signals your pipeline sends, since real user monitoring features need more than OTLP.
Yes. The same team runs RabbitMQ, Kafka and PostgreSQL estates, so those signals are read by engineers who know them.
Yes, as a comparison, not a pitch: see /compare/dynatrace-alternatives/ for pricing units, options and who should stay.
AceMQ offers a rollout and coverage review, an OpenTelemetry pipeline design and an alert threshold clean-up as named deliverables, each with written findings.
Response targets start at 15 minutes, by plan. Quote replies come within 1 hour.
Yes. AceMQ works on Dynatrace 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 Dynatrace 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 Dynatrace is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.
Let's talk
Send us one host that shows no services and your OneAgent install method. We reply to quote requests within 1 hour.
Production incident right now?Email a Dynatrace Architect