Softwr

Software · head to head

Elastic APM vs Loki

Elastic APM logo

Elastic APM

Software

Application Performance Monitoring from Elastic

From
Free
Rated
-
Loki logo

Loki

Software

Like Prometheus but for Logs

From
Free
Rated
-

The short version

  • Each has a real cost: Elastic APM pricing is not published on the product page; cost follows the underlying Elastic deployment rather than being quoted per host or per service; Loki the Grafana Cloud free tier caps log ingestion at 50 GB a month with 14 day retention
  • They diverge on capability: Elastic APM covers Performance monitoring, Loki covers Log aggregation.

Where they differ

Only the attributes on which Elastic APM and Loki actually diverge.

Attributes where Elastic APM and Loki differ
AttributeElastic APMLoki
Founded20112014

Identical on both: starting price (Free), pricing model (open-source), free tier (Yes), platforms (Web, Api), user rating (Not yet rated), category (Unknown).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Elastic APM

  • Performance monitoring
  • Error tracking
  • Transaction tracing
  • Custom metrics

Only in Loki

  • Log aggregation
  • Label-based indexing
  • Real-time log streaming
  • LogQL query language

Both cover

  • API
  • Webhooks
  • REST
  • Web support
  • Api support

What people use each for

The jobs each tool is most often brought in to do.

Elastic APM

  • Distributed tracing across microservicesnot Loki
  • Auto-instrumenting Java, .NET, Python, Go, Node.js, Ruby, PHP and C++ servicesnot Loki
  • OpenTelemetry-native collection through the Elastic distributionsnot Loki
  • Correlating latency and errors with machine learningnot Loki
  • Monitoring LLM calls alongside application tracesnot Loki

Loki

  • Aggregating application and infrastructure logs with label based indexingnot Elastic APM
  • Querying logs alongside metrics in Grafananot Elastic APM

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Elastic APM

  • Pricing is not published on the product page; cost follows the underlying Elastic deployment rather than being quoted per host or per service
  • Self-managed deployment means running and scaling Elasticsearch yourself
  • Serverless does not carry every capability the hosted option does

Loki

  • The Grafana Cloud free tier caps log ingestion at 50 GB a month with 14 day retention
  • Paid log pricing is split across three separate meters, at $0.050 per GB processed, $0.400 per GB written and $0.100 per GB retained
  • Retaining logs is billed separately from ingesting them, so keeping data costs on an ongoing basis rather than once
  • The Pro plan carries a $19 a month platform fee before any usage charges

Pricing, plan by plan

Elastic APM

Free
  • FreeFree
    • Performance monitoring
    • Error tracking
    • Transaction tracing

Loki

Free
  • FreeFree
    • Log aggregation
    • Label-based indexing
    • Real-time log streaming

Which should you pick?

Choose Elastic APM if

  • You need performance monitoring.
  • You want to start without paying.
  • You work on Web, Api.
  • You also want error tracking.

Choose Loki if

  • You need log aggregation.
  • You want to start without paying.
  • You work on Web, Api.
  • You also want label-based indexing.

Questions people ask

Is Elastic APM or Loki better?
Neither clearly leads. Elastic APM starts at Free and Loki at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Elastic APM or Loki?
Elastic APM starts at Free and Loki at Free.
Does Elastic APM or Loki run on more platforms?
Both run on Web, Api, so platform support will not decide this one for you.
Can I use Elastic APM for free?
Both have a free tier, so you can try either at no cost before committing.
What is Elastic APM best used for?
Elastic APM is most often used for distributed tracing across microservices, auto-instrumenting java, .net, python, go, node.js, ruby, php and c++ services, opentelemetry-native collection through the elastic distributions, correlating latency and errors with machine learning. Of those, distributed tracing across microservices and auto-instrumenting java, .net, python, go, node.js, ruby, php and c++ services are not what Loki is typically brought in for.
What can Elastic APM do that Loki cannot?
Elastic APM covers Performance monitoring, Error tracking, Transaction tracing, Custom metrics. Loki covers Log aggregation, Label-based indexing, Real-time log streaming, LogQL query language. Both handle API, Webhooks, REST, Web support.

Related pages

Other head to heads