Which Prometheus versions are still supported, and when do they reach end of life?
Prometheus 3.13 is the supported LTS release, with fixes to 31 July 2027. Prometheus 3.5 ended on 31 July 2026 and 2.53 on 31 July 2025. The project patches a minor release for about six weeks, and LTS releases get high-severity fixes only. AceMQ supports self-managed Prometheus on any of these lines, including 2.x, while the upgrade is planned.
Who answers when Prometheus goes down or stops alerting, and how fast?
A named AceMQ senior engineer answers 24/7, with response targets from 15 minutes, by plan, when Prometheus is down, stuck in WAL replay or no longer alerting. Lower severities get a first response within 1 hour, 4 hours or the next business day. Monitoring that fails during an incident is treated as P1, and every P1 ends with a written root-cause analysis.
How does a Prometheus engagement with AceMQ start?
A Prometheus engagement starts with a free consultation with a senior engineer, booked in our reply within 1 hour. A metrics and cardinality assessment follows, covering series by metric and label, scrape and exporter coverage, recording and alerting rules, and retention. Written findings follow, and nothing changes until your team has read them.
Can an AceMQ engineer work alongside our in-house SRE team?
Yes. AceMQ assigns a named senior engineer from its team of 11+ who works with your engineers rather than around them, changing relabelling, recording rules and Alertmanager routing together. Each change is staged so you can compare query results before and after, and you keep the runbooks for WAL replay, target loss and cardinality regressions.
Why does Prometheus run out of memory, and is more RAM the fix?
Prometheus memory follows the number of active series in the head block, so an OOM kill almost always means series grew, usually because a label took unbounded values such as a user ID, request path or pod name. More memory only delays the next kill and lengthens WAL replay. AceMQ finds the metric and label, drops it with metric_relabel_configs and fixes the instrumentation.
Why does one failure fire dozens of Prometheus alerts, and how do we fix routing?
One failed node pages dozens of times when Alertmanager has no grouping, no inhibition and no ownership routes, so each rule becomes its own notification to the same channel. Setting group_by, inhibit_rules and routes that match a team label turns the storm into one notification for one owner. AceMQ also removes rules that never led to action.
Should we add Thanos or Mimir, or use a managed Prometheus service?
Choose by retention, query scope and who should carry the operational work. Thanos suits a Prometheus per cluster with a global query view, Mimir suits centralised high write volume, and cloud managed services take storage off your on-call but bill by series ingested. AceMQ supports the Prometheus side of all three and recommends the one that fits your query patterns and team.
Can AceMQ run Prometheus for us instead of only supporting it?
Yes, in two ways. AceMQ can operate Prometheus, Alertmanager and the long-term storage layer inside your own cloud account, cluster or data centre, or host them on AceMQ infrastructure and receive your samples by remote_write. Either way AceMQ owns monitoring, upgrades, capacity and on-call, and your team keeps writing rules and dashboards.
What does a Prometheus implementation engagement include?
It covers exporter and scrape architecture, a label and cardinality policy, retention sized from your sample rate, recording and alerting rules, and the storage layer behind Prometheus. The order is fixed: what is scraped, how long it is kept, how alerts are routed, then whether Thanos or Mimir is needed. Your team reads written findings before anything changes in production, and the steps are laid out above.
When do we need Thanos or Mimir instead of a bigger Prometheus server?
When one of three things is true: you need history longer than local disk can hold, you want one query view across several Prometheus servers, or you need the metrics to survive the loss of a server. The Prometheus documentation says local storage is not clustered or replicated, so a larger machine does not fix any of those. Below that point, a single server with sensible retention is usually the simpler choice.
Who offers Prometheus consulting and professional services?
AceMQ does: cardinality audits, exporter and alerting design, long-term storage with Thanos, Mimir or Cortex, and migrations from legacy monitoring, delivered by senior engineers and quoted per engagement. Prometheus is a community project with no single vendor behind it, so the other sources are observability vendors that sell their own metrics platform, general DevOps consultancies and independent specialists. Ask what each will do about cardinality, because that decides memory use, query speed and the bill on every backend. A consultant who proposes a new backend before measuring your series count is selling a platform, not fixing the cause.
Can we work with AceMQ on Prometheus without a long contract?
Yes. AceMQ works on Prometheus 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.
How much does AceMQ Prometheus support or consulting cost?
Every AceMQ proposal is tailored to your requirements: your Prometheus 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 Prometheus is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.