Softwr

Log Management · head to head

Loki vs Elasticsearch Service

Loki logo

Loki

Log Management

Like Prometheus but for Logs

From
Free
Rated
-
Elasticsearch Service logo

Elasticsearch Service

Log Management

Managed Elasticsearch Cloud Service

From
Free
Rated
-

The short version

  • Each has a real cost: Loki the Grafana Cloud free tier caps log ingestion at 50 GB a month with 14 day retention; Elasticsearch Service the 99.95 percent monthly uptime SLA applies only to the Platinum and Enterprise subscription tiers
  • They diverge on capability: Loki covers Log aggregation, Elasticsearch Service covers Full-text search.

Where they differ

Only the attributes on which Loki and Elasticsearch Service actually diverge.

Attributes where Loki and Elasticsearch Service differ
AttributeLokiElasticsearch Service
Pricing modelopen-sourceusage-based
Founded20142011

Identical on both: starting price (Free), free tier (Yes), platforms (Web, Api), user rating (Not yet rated), category (Log Management).

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 Loki

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

Only in Elasticsearch Service

  • Full-text search
  • Scalability
  • High availability
  • Security

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.

Loki

  • Aggregating application and infrastructure logs with label based indexingnot Elasticsearch Service
  • Querying logs alongside metrics in Grafananot Elasticsearch Service

Elasticsearch Service

  • Managed Elasticsearch without running the clusternot Loki
  • Log and observability data storage and searchnot Loki
  • Full-text search behind an applicationnot Loki
  • Deployments needing a specific cloud region across AWS, Azure or GCPnot Loki

Where each one falls short

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

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

Elasticsearch Service

  • The 99.95 percent monthly uptime SLA applies only to the Platinum and Enterprise subscription tiers
  • Serverless does not yet support traffic filtering, cross-project search or bring-your-own-key encryption
  • Serverless runs on AWS, GCP and Azure only, against 60 regions for the hosted option
  • Per-unit prices are not published; hosted is resource-based and serverless usage-based

Pricing, plan by plan

Loki

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

Elasticsearch Service

Free
  • FreeFree
    • Full-text search
    • Scalability
    • High availability

Which should you pick?

Choose Loki if

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

Choose Elasticsearch Service if

  • You need full-text search.
  • You want to start without paying.
  • You work on Web, Api.
  • You also want scalability.

Questions people ask

Is Loki or Elasticsearch Service better?
Neither clearly leads. Loki starts at Free and Elasticsearch Service at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Loki or Elasticsearch Service?
Loki starts at Free and Elasticsearch Service at Free.
Does Loki or Elasticsearch Service run on more platforms?
Both run on Web, Api, so platform support will not decide this one for you.
Can I use Loki for free?
Both have a free tier, so you can try either at no cost before committing.
What is Loki best used for?
Loki is most often used for aggregating application and infrastructure logs with label based indexing, querying logs alongside metrics in grafana. Of those, aggregating application and infrastructure logs with label based indexing and querying logs alongside metrics in grafana are not what Elasticsearch Service is typically brought in for.
What can Loki do that Elasticsearch Service cannot?
Loki covers Log aggregation, Label-based indexing, Real-time log streaming, LogQL query language. Elasticsearch Service covers Full-text search, Scalability, High availability, Security. Both handle API, Webhooks, REST, Web support.

Related pages

Other head to heads