← Blog / AIOps

Which companies set up Prometheus, Grafana and Loki observability as a managed service?

17 Nov 2026 · 6 min read

Stacked layers of logs, metric charts and dashboards connected by beams of light, watched by an observing lens

Short answer: There are two kinds. Hosted platforms such as Grafana Cloud, or Amazon Managed Service for Prometheus with Amazon Managed Grafana, run the backends for you, but your team still instruments the services and writes the dashboards and alerts. Engineering partners such as iDefender set up the whole stack in your own cloud account and keep it running.

Choose hosted if you have engineers who will own instrumentation and alert design. Choose a partner if you want the outcome (useful dashboards and alerts people trust) delivered and maintained.

What each piece does

ComponentJobNotes
PrometheusCollects and stores metrics, evaluates alert rulesShort retention by default; add Thanos, Grafana Mimir or VictoriaMetrics for long-term storage
AlertmanagerGroups, deduplicates, silences and routes alertsWhere most alert-fatigue fixes live
GrafanaDashboards and exploration across metrics, logs and tracesKeep dashboards as code (JSON or Terraform), not hand-edited
LokiStores logs, indexing only labels, not full textMuch cheaper to run than full-text indexing; queried with LogQL
Grafana AlloyAgent that ships logs (and metrics, traces)Replaces Promtail, which Grafana has deprecated

Hosted platform or partner: what you actually get

Hosted platformEngineering partner (in your account)
Who runs the backendsThe vendorThe partner, in your cloud
Instrumentation of your servicesYour teamThe partner, with your team
Dashboards, SLOs, alert rulesYour teamThe partner, as code in your repo
Data locationVendor's regionYour account and region
Cost modelUsage-based (series, log volume)Your infrastructure plus the engagement
Lock-inLow (open formats) but billing scales with volumeLow; everything is open source and in your repo

Step by step, either way

  1. Instrument first. Expose metrics from every service (Prometheus client libraries or OpenTelemetry), emit structured JSON logs, and add a request ID that appears in both.
  2. Install on Kubernetes with the community charts. kube-prometheus-stack brings Prometheus, Alertmanager, Grafana and the standard Kubernetes dashboards; Loki has its own Helm chart.
  3. Decide retention. Prometheus for days to weeks; long-term metrics in object storage via Thanos or Mimir; Loki logs in object storage (S3 or equivalent) with a retention period agreed per environment.
  4. Keep labels under control. High-cardinality labels (user IDs, request IDs) in metrics or Loki labels are the most common cause of cost blow-ups and slow queries. Put them in the log line, not the label.
  5. Write alerts on symptoms, not causes. Alert on error rate and latency against an SLO; keep CPU and disk as dashboard panels or low-urgency tickets.
  6. Everything as code. Dashboards, alert rules and routing live in Git and deploy through the pipeline, so a lost Grafana pod loses nothing.

How iDefender does this

We instrument what you already run, build a baseline from your own traffic, agree SLOs with your on-call team and then tune alerting until every page is one a human should act on. A typical baseline takes 4 to 6 weeks. Our core stack is Prometheus, Grafana, ELK and Alertmanager; deliverables are instrumented services, dashboards provisioned as code, SLOs with error budgets and tuned alert routing. See AIOps services or book a call.

Frequently asked questions

Is Loki a replacement for Elasticsearch?

For many teams, yes for logs. Loki indexes only labels, so it's cheaper to store and run, but searches across large time ranges are slower than a full-text index. Teams that need heavy full-text search or analytics on log content often keep Elasticsearch or OpenSearch.

Can Prometheus keep metrics for a year?

Not on its own in a practical way. Add Thanos, Grafana Mimir or VictoriaMetrics to keep long-term metrics cheaply in object storage.

Is Grafana Cloud cheaper than running it ourselves?

At small volumes, usually yes, because you pay nothing for the people running it. At high metric series or log volumes, self-hosting in your own account often costs less, but only if someone owns it.

Do we need OpenTelemetry?

Not to start. Prometheus client libraries and structured logs are enough. OpenTelemetry is worth adopting when you add distributed tracing or want one instrumentation layer for several backends.

Tell us what you run today and what has to change.