Log Management · head to head
Elasticsearch Service vs Stackdriver
Elasticsearch Service
Log Management
Managed Elasticsearch Cloud Service
- From
- Free
- Rated
- -
Stackdriver
Log Management
Google Cloud Operations - Monitoring and Logging
- From
- Free
- Rated
- -
The short version
- Each has a real cost: Elasticsearch Service the 99.95 percent monthly uptime SLA applies only to the Platinum and Enterprise subscription tiers; Stackdriver stackdriver is now branded Google Cloud Observability and cloud.google.com/stackdriver redirects to the Observability product page
- They diverge on capability: Elasticsearch Service covers Full-text search, Stackdriver covers Log management.
Where they differ
Only the attributes on which Elasticsearch Service and Stackdriver actually diverge.
| Attribute | Elasticsearch Service | Stackdriver |
|---|---|---|
| Founded | 2011 | 2006 |
Identical on both: starting price (Free), pricing model (usage-based), 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 Elasticsearch Service
- Full-text search
- Scalability
- High availability
- Security
Only in Stackdriver
- Log management
- Metrics collection
- Real-time monitoring
- Error reporting
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.
Elasticsearch Service
- Managed Elasticsearch without running the clusternot Stackdriver
- Log and observability data storage and searchnot Stackdriver
- Full-text search behind an applicationnot Stackdriver
- Deployments needing a specific cloud region across AWS, Azure or GCPnot Stackdriver
Stackdriver
- Centralised logging, metrics and traces for workloads running on Google Cloudnot Elasticsearch Service
- Alerting and uptime checks on cloud servicesnot Elasticsearch Service
- Running managed Prometheus-compatible monitoring at scalenot Elasticsearch Service
Where each one falls short
Documented limitations, not opinions. Every one is a constraint you would hit in normal use.
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
Stackdriver
- Stackdriver is now branded Google Cloud Observability and cloud.google.com/stackdriver redirects to the Observability product page
- Cloud Logging charges $0.50 per GiB ingested, with only the first 50 GiB per project per month free
- Logs kept beyond 30 days cost an extra $0.01 per GiB per month on top of the ingestion charge
- Monitoring metric ingestion starts at $0.2580 per MiB, with only the first 150 MiB per billing account free
- Alerting policies are billed at $0.35 per month for each metric reference in the policy
- Uptime checks cost $0.30 per 1,000 executions and synthetic monitors $1.20 per 1,000 executions, with only 100 synthetic executions per billing account free
- Monitoring read API calls cost $0.50 per million time series returned beyond the first million per billing account
- Log volume is measured before indexing on the actual size of log entries, so verbose logging directly drives cost
Pricing, plan by plan
Elasticsearch Service
Free- FreeFree
- Full-text search
- Scalability
- High availability
Stackdriver
Free- FreeFree
- Log management
- Metrics collection
- Real-time monitoring
Which should you pick?
Choose Elasticsearch Service if
- You need full-text search.
- You want to start without paying.
- You work on Web, Api.
- You also want scalability.
Choose Stackdriver if
- You need log management.
- You want to start without paying.
- You work on Web, Api.
- You also want metrics collection.
Questions people ask
- Is Elasticsearch Service or Stackdriver better?
- Neither clearly leads. Elasticsearch Service starts at Free and Stackdriver at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
- Which is cheaper, Elasticsearch Service or Stackdriver?
- Elasticsearch Service starts at Free and Stackdriver at Free.
- Does Elasticsearch Service or Stackdriver run on more platforms?
- Both run on Web, Api, so platform support will not decide this one for you.
- Can I use Elasticsearch Service for free?
- Both have a free tier, so you can try either at no cost before committing.
- What is Elasticsearch Service best used for?
- Elasticsearch Service is most often used for managed elasticsearch without running the cluster, log and observability data storage and search, full-text search behind an application, deployments needing a specific cloud region across aws, azure or gcp. Of those, managed elasticsearch without running the cluster and log and observability data storage and search are not what Stackdriver is typically brought in for.
- What can Elasticsearch Service do that Stackdriver cannot?
- Elasticsearch Service covers Full-text search, Scalability, High availability, Security. Stackdriver covers Log management, Metrics collection, Real-time monitoring, Error reporting. Both handle API, Webhooks, REST, Web support.