# Elastic Observability APM — Error Tracking & APM

Elastic Observability APM by Elastic (Elasticsearch B.V.) holds a panel rating of 2/5 from 6 AI judges (category median 2.5/5), as of 2026-11-18. Provenance: provenance unknown; sovereignty: 3 of 6 dimensions proven.

- Vendor: Elastic (Elasticsearch B.V.) (https://www.elastic.co)
- Category: [Error Tracking & APM](https://whats-best.ai/software/error-tracking.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/error-tracking/elastic-observability-apm
- Alternatives: https://whats-best.ai/software/error-tracking/elastic-observability-apm/alternatives ([markdown](https://whats-best.ai/software/error-tracking/elastic-observability-apm/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-18 · oldest source captured 2026-11-17

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Elastic (Elasticsearch B.V.)
- Headquarters: Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting: Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 17 Nov 2026

## The panel's verdict

Elastic Observability APM is an application performance monitoring system built on the Elastic Stack. The bench scores it strongest on performance tracing, 4-6, and sovereignty, 5-8. Higher tracing scores rest on W3C Trace Context propagation, a trace waterfall linking spans to their errors and a managed OpenTelemetry intake endpoint; lower ones stop at undescribed percentile breakdowns, profiling and anomaly detection. Workflow and integrations is the weakest criterion, scored 2 with no spread: the documented integrations pull data in, and no public information appears on alert rules, notification channels or issue-tracker sync, so nothing shown routes an error to whoever fixes it. Error tracking clusters at 4-5, ending at grouping, with issue states, release tracking and source maps undescribed. Sovereignty is the genuine split: the reliability engineer scored 8 for the self-managed chain keeping events on customer-controlled servers; the SaaS CTO scored 5, finding the managed chain only partly verifiable — no EU region named, no data processing agreement found, no subprocessor locations shown. A 14-day free trial with all features and no credit card required is public; no plan prices appear.

**Speaks for it:**
- Distributed tracing over W3C Trace Context works out of the box, with a trace waterfall that links a span to its errors and a managed OpenTelemetry intake endpoint.
- Agents are documented for Go, iOS, Java,.NET, Node.js, PHP, Python, Ruby and real-user monitoring, capturing stack traces, a culprit field, service, host, process, URL and user context, automatic grouping and KQL search.
- The whole stack runs self-managed as packages, Docker images and Kubernetes Helm charts on Linux, macOS, Windows, Docker or Kubernetes, with the default distribution including the full set of free features under the Elastic License.
- SAML 2.0 single sign-on is documented in depth — signed requests, encrypted assertions, role mapping from identity-provider groups, automatic provisioning — and is included at no additional cost on Elastic Cloud Serverless on any tier.
- Cloud deployments allow hosting-region selection on AWS, Azure or Google Cloud Platform with backups stored in the selected region by default, alongside a published transfer impact assessment and a stated no-backdoor commitment.

**Held against it:**
- No public information appears on alert rules, notifications to email, Slack, PagerDuty or Teams, or issue-tracker sync, and the documented integrations pull audit and security data in rather than route errors to anyone.
- Triage stops at grouped errors: no public information appears on issue states such as resolved or regressed, release and deploy tracking, or source maps and symbolication.
- User email, ID and username are captured when supplied, field limits of 1024 and 10,000 characters truncate but do not anonymise, and no public information appears on scrubbing, IP anonymisation or deletion on request.
- Audit logging is disabled by default, limited to certain subscription levels and stated to be unavailable on Serverless, with no public information on two-factor authentication, ISO 27001 or SOC 2, a public status page or an SLA.
- The captured pages name no EU region, show no subprocessor locations, and give no public information on a data processing agreement or the jurisdiction of the contracting entity, elasticsearch B.V.

**Best for:**
- You need every trace and error in your own chain — the stack runs self-managed on your Linux, Windows, Docker or Kubernetes infrastructure, with APM events indexed into your own Elasticsearch data streams.
- You standardise on OpenTelemetry and want a managed intake endpoint that keeps instrumentation portable.
- You already run Elasticsearch and Kibana and want errors, traces and logs searched together through KQL and Discover.
- You must select your hosting region for data residency among AWS, Azure or Google Cloud Platform, with backups kept in that region by default.

**Avoid if:**
- You need an error to page someone — ask the vendor: the public pages we read do not show it
- You triage frequent releases — the errors pages stop at frequency trends and top affected transactions, while release and deploy tracking, source maps, symbolication and issue states are undescribed on the captured pages.
- Error payloads will carry personal data — user email, ID and username are captured when supplied, and field limits of 1024 and 10,000 characters truncate rather than anonymise.
- You need audit logging on Serverless — the captured pages state it is unavailable there, and it is disabled by default and gated to certain subscription levels elsewhere.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Agency Tech Lead | The SaaS CTO | The Mobile Team Lead | The Site Reliability Engineer | The Data Protection Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Error capture, grouping & triage | 2/5 | 2/5 | 2/5 | 2/5 | 2.5/5 | 2/5 |
| APM, tracing & profiling | 2/5 | 3/5 | 2/5 | 3/5 | 3/5 | 2/5 |
| Alerting, integrations & developer workflow | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 |
| Data scrubbing, retention & volume control | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Access control, security & the vendor's reliability | 2.5/5 | 3/5 | 2/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| European sovereignty | 3/5 | 2.5/5 | 3/5 | 4/5 | 3/5 | 3.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2/5** | **2.5/5** | **2/5** | **2/5** | **2.5/5** | **2.5/5** |

### The judges

- **The Agency Tech Lead** (v1.0): Technical lead at a web agency in Cologne with fourteen developers and forty client sites on Laravel, Shopware and WordPress, most on maintenance contracts. Wants every client in its own project with its own alert channel, PHP stack traces that show the query and the queued job, slow pages found before the client calls, request data scrubbed because the shops hold customer addresses, and a monthly bill that does not jump when one client's cron job throws the same exception a million times.
- **The SaaS CTO** (v1.0): CTO of a B2B SaaS company in Berlin with thirty-five engineers, twelve services in Go, Python and TypeScript on Kubernetes and a React frontend. Wants one trace from the click in the browser to the slow database call three services down, OpenTelemetry so the instrumentation is not locked to one vendor, errors routed to the team that owns the service, releases linked to the commits that broke them, and an EU region because the enterprise customers ask where their data goes.
- **The Mobile Team Lead** (v1.0): Leads the six-person app team of a fashion retailer in Hamburg, with an iOS and an Android app and a Flutter rewrite under way, released every two weeks. Wants native crashes symbolicated without a manual upload, crash-free users per release so a bad version is stopped in the store rollout, the device, OS and the last screens before the crash, logs from a customer's phone when support asks, and alerts when a new release crashes more than the last.
- **The Site Reliability Engineer** (v1.0): Site reliability engineer on the on-call rota of a payments platform in Amsterdam, woken at night when checkout latency climbs. Wants alerts on error rates and latency percentiles, not on every single exception, routed to PagerDuty with the trace attached, spike protection so an incident does not also blow the quota, SSO and audit logs for the auditors, and a vendor whose own status page and SLA say what happens when the monitoring is the thing that is down.
- **The Data Protection Officer** (v1.0): Data protection officer of a statutory health insurer whose member portal and app are built by an in-house team and two agencies. Knows that a stack trace or a request body can carry a member number, a diagnosis code or an IBAN. Reads the subprocessor list, asks where events are stored and for how long, wants scrubbing on the server and not only in the SDK, asks which AI model explains the errors and where, and needs a DPA before the first SDK goes into production.
- **The Skeptic** (v1.0): Has seen a "free tier" that ran out on the first busy Monday, an overage bill larger than the plan after one deploy looped on an exception, "EU hosting" with the support desk and the AI assistant in the US, and an SDK that slowed the app it was meant to watch. Asks what happens at the quota, how long events are really kept, whether the instrumentation works with another vendor after leaving, what the self-hosted edition leaves out — and what the second year costs.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 3 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Self-hostable | 1/1 | [S14] |
| Open source | Source available | 0/1 | [S4] |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Published | 1/1 | [S3] |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Local security: Basic authentication · no [S5]
- No backdoor: no [S3]
- Privacy statements: General Privacy Statement · Product Privacy Statement · Candidate Privacy Statement · California Privacy Rights Statement · Elastic Cookie Privacy Statement · Free and Open Privacy Statement [S3]
- White papers: White papers available for Privacy, Data Security, and AI Compliance [S3]

**Data**
- Transaction data streams: traces-apm.rum-<namespace> · traces-apm-<namespace> [S8]

**Hosting**
- Backup residency: yes [S3]
- Providers: AWS · Microsoft Azure · Google Cloud Platform [S3]
- Region selection: yes [S3]

**Integrations**
- API request stream: api_request data stream, no inputs of its own [S11]
- Code scanning: retrieve security vulnerabilities and coding errors via GitHub Advanced Security Code Scanning [S11]
- Code scanning permissions: security_events read / security_events scope / public_repo scope [S11]
- Filebeat log collection: Filebeat [S14]
- Language clients: Elasticsearch language clients · curl [S5]
- Secret scanning: retrieve secret scanning advanced security alerts [S11]
- Secret scanning permissions: secret_scanning_alerts read / admin + repo or security_events scope [S11]
- Self managed formats: packages · Docker images · Kubernetes Helm charts [S1]
- Supported idps documented: Okta · Microsoft Entra ID [S13]

**Legal**
- Consumer use excluded: yes [S4]
- Entity: elasticsearch B.V. [S3]
- Entity: elasticsearch B.V. [S4]
- Entity name: elasticsearch B.V. · 2026 [S2]
- Footer links: Trademarks · Terms of Use · Privacy Statement · Sitemap [S2]
- Public authority requests: Disclosure only if strictly required by law; principles published [S3]
- Third party trademarks: Apache trademarks acknowledged; all other trademarks belong to their respective owners [S2]
- Trademark owner: Elastic and Elasticsearch marks owned by elasticsearch B.V. in the United States and other countries [S2]
- Trademarks:  [S1]
- Use restriction: Website intended for professional use only; no consumer use intended or directed [S2]

**Pricing**
- Free trial: 14 · yes [S6]
- Free trial: 14-day free trial with all features, no setup [S7]
- Free trial: 14 · yes [S8]
- Free trial: all features included · 14 · yes [S9]
- Local trial: all Elastic features · one month [S5]
- Managed option: Elasticsearch Service on Elastic Cloud [S5]
- Post trial: Free and open - Basic [S5]
- Trial: 14 · no · yes [S1]
- Trial offer: 14 · yes [S13]

**Product**
- AI capabilities:  [S1]
- API request routing: Route API request events to separate data stream logs-github.api_requests-* [S11]
- Apm data streams: yes [S10]
- Apm description: Application performance monitoring built on the Elastic Stack, monitoring real-time response time for requests, DB queries, caches, external HTTP [S10]
- Apm doc version: Current · v9.0+ [S10]
- Apm fleet management: yes [S10]
- Apm serverless unavailable: Managed OTLP Endpoint or managed intake service · no [S10]
- Audit dataset: github.audit records all org/enterprise events [S11]
- Audit log output file: every cluster node · <clustername>_audit.json · host file system [S14]
- Audit log scope: read:audit_log [S11]
- Audit log sources: GitHub API · Azure Event Hubs · Azure Blob Storage · AWS S3 · AWS SQS · Google Cloud Storage [S11]
- Audit logging deployment types: self-managed · Elastic Cloud Hosted · Elastic Cloud Enterprise (ECE) · Elastic Cloud on Kubernetes (ECK) [S14]
- Audit logging disabled by default: no [S14]
- Audit logging dynamic setting 9 5: yes · no · 9.5 [S14]
- Audit logging enable setting: yes · xpack.security.audit.enabled [S14]
- Audit logging events: security-related events: authentication failures, refused connections, data access authorization, user security configuration changes [S14]
- Audit logging independent elasticsearch kibana: yes [S14]
- Audit logs subscription gated: subscription_level_dependent [S14]
- Auth API key: yes [S5]
- Automatic instrumentation: Distributed tracing works out-of-the-box for supported technologies with no additional configuration [S9]
- Autoops diagnostics: /latency · /cpu_utilization · /index_queue_depth · /node_load · region_dependent [S12]
- Build system: Gradle [S5]
- Bulk API: yes · NDJSON [S5]
- Data sources: GitHub API · Azure Eventhub · yes [S11]
- Data streams: yes [S5]
- Default ports: 5601 · 9200 [S5]
- Deployment models: Serverless · Stack [S9]
- Deployment options: Elastic Cloud Serverless · Elastic Cloud Hosted · self-managed [S1]
- Deployment SSO protocols: LDAP · OIDC · SAML [S13]
- Deployment SSO role mapping scope: built-in and custom stack-level roles · organization-level roles · cloud resource access roles · Serverless project custom roles [S13]
- Description: Distributed search and analytics engine, scalable data store and vector database [S5]
- Developer: Elastic [S11]
- Distributed tracing: Distributed tracing spans operations across multiple services/components [S9]
- Domain claim limit: 10 · yes [S13]
- Ech latency threshold: 6 [S12]
- Enforce disable API: organization owner · yes [S13]
- Enforce SSO default state: no · yes [S13]
- Enterprise admin scope: admin:enterprise [S11]
- Error context metadata: Agents allow capturing custom metadata; indexed as labels or non-indexed as custom [S6]
- Error culprit: Error culprit field indicates where the error originated [S6]
- Error data streams: logs-apm.error-<namespace> · logs-apm.app.<service.name>-<namespace> [S6]
- Error document example: Page provides an example error document indexed in Elasticsearch [S6]
- Error environment data: Service · Host · Process · URL · User [S6]
- Error event contents: Error events capture the original exception or a log created when the exception occurred; errors are represented by a unique ID [S6]
- Error field limits: 1024 · 10000 [S6]
- Error group top transactions: Error group details page shows error occurrences over time and top 5 affected transactions [S7]
- Error grouping: Error documents include a grouping_key and grouping_name for grouping errors [S6]
- Error sample contents: Error sample shows most recent error with exception message, culprit, stack trace, context, all copyable [S7]
- Error stacktrace: Captured exception and captured log of an error can each contain a stack trace [S6]
- Error storage indices: Errors are stored in error indices [S6]
- Error transaction link: Errors can relate to transactions via transaction.id [S6]
- Errors capture condition: Errors appear only when APM agent or OpenTelemetry SDK records them; HTTP 5xx without exception needs the Failed transaction rate chart [S7]
- Errors from logs discover: Exception logs can be inspected in Discover; Open in Discover explores all matching logs [S7]
- Errors from logs limit: Errors from logs section lists up to 500 most recent matching exception logs [S7]
- Errors from logs version: Errors from logs section requires Elastic Stack 9.5.5+ [S7]
- Errors UI grouping: Errors page in Applications UI groups similar errors to show frequency, trends, and affected transactions/code [S7]
- Event hub auth: connection_string · client_secret_azure_ad [S11]
- Event hub rbac roles: Azure Event Hubs Data Receiver · Storage Blob Data Contributor [S11]
- Federation: ES\|QL federation [S1]
- Field export: integration exports documented field schema incl. github.* ECS fields [S11]
- Field length limits: 1024 · 10000 [S8]
- First role mapping owner required: Organization owner role [S13]
- Free trial: 14 · yes [S12]
- Idp changes not auto synced: no [S13]
- Idp initiated SSO not supported: no [S13]
- Incompatible github es: no [S11]
- Ingestion methods: API · AWS S3 · Azure Blob Storage · Azure Event Hub · Google Cloud Storage [S11]
- Integration name: GitHub Integration [S11]
- Intended use: no [S3]
- Kibana visualization: yes [S5]
- Kql scope: KQL search bar and time range apply to both APM errors and Errors from logs sections [S7]
- Kubernetes option: Elastic Cloud on Kubernetes available for Kubernetes deployments [S4]
- Languages: 3.3% · 96.1% · 0.3% [S5]
- Latest version: 3.1.0 [S11]
- Legacy header compat: Backward-compatible support for legacy elastic-apm-traceparent header [S9]
- License: Elastic License · full set [S4]
- Local docker install: start-local script installs Elasticsearch and Kibana via Docker for local testing [S4]
- Managed beta no SLA: yes [S11]
- Managed ech requirement: 9.5+ [S11]
- Manual propagation agent support: Manual traceparent add/parse supported in Go, iOS, Java, .NET, Node.js, PHP, Python, Ruby agents; Android not applicable [S9]
- Manual roles overwritten by mapping: yes [S13]
- Manual trace propagation: Manual trace propagation via agent APIs for unsupported protocols [S9]
- Minimum kibana versions: 9.3.0 · 9.2.4 · 9.1.10 · 8.19.10 [S11]
- Orchestrated audit logs require forwarding: must ship to monitoring deployment to be user-accessible [S14]
- Otel exception logs ungrouped: OpenTelemetry exception logs not recorded as APM errors are listed but not grouped or in error charts [S7]
- Otlp rate limit error message: rpc error: code = ResourceExhausted desc = request exceeded available capacity · Managed OTLP Endpoint [S12]
- Owner access verification: yes [S13]
- Prerequisites enterprise cloud: requires enterprise owner and Enterprise Cloud plan with audit log access [S11]
- Prerequisites enterprise server: site administrator and audit logging enabled required for GitHub Enterprise Server [S11]
- Prerequisites organization: organization owner, Enterprise Cloud, enterprise plan with audit log required [S11]
- Privacy datasheets: Elasticsearch · Observability · Security · Support Services · AutoOps in Cloud Connect · Elastic AI · yes [S3]
- Privacy program commitment: Privacy program ensures customers own their data and control processing [S3]
- Rate limiting behavior: Managed inputs respond with HTTP 429 errors when incoming data exceeds processing/indexing capacity [S12]
- Rate limiting ech behavior: cluster_capacity · http_429 · ech [S12]
- Rate limiting identification: 429 [S12]
- Rate limiting serverless behavior: automatic · serverless · rare [S12]
- Release date: 2026-11-02 [S4]
- Release status: beta [S11]
- Retention customization: retention customized via logs-github.api_requests@custom component template / ILM [S11]

**Subprocessors**
- Exists: Infrastructure and customer support subprocessors used; public lists available [S3]

**Support**
- Ech undersized cluster: Elastic Support · AutoOps unavailable in region [S12]
- Forum slack: Elastic Forum · Slack [S5]
- Github issues: GitHub Issues [S5]
- Serverless persistent 429: Elastic Support · serverless [S12]

42 more facts on the canonical page: https://whats-best.ai/software/error-tracking/elastic-observability-apm

## Questions

### Is Elastic Observability APM European?

Not determined: the vendor’s pages as captured do not say where Elastic Observability APM is based.

### Where does Elastic Observability APM store data?

Not stated on the vendor’s pages as of 17 Nov 2026.

### Does Elastic Observability APM have a free plan?

Not stated on the vendor’s pages as of 17 Nov 2026.

### What are the best alternatives to Elastic Observability APM?

As of 18 Nov 2026, the panel rates [Sentry (3.5/5)](https://whats-best.ai/software/error-tracking/sentry), [Datadog APM & Error Tracking (3.5/5)](https://whats-best.ai/software/error-tracking/datadog) and [Dynatrace (3/5)](https://whats-best.ai/software/error-tracking/dynatrace) highest among the other 19 Error Tracking & APM products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [Tideways](https://whats-best.ai/software/error-tracking/tideways) (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Elastic Observability APM alternatives](https://whats-best.ai/software/error-tracking/elastic-observability-apm/alternatives).

## What this page leaves out

- 2 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 1 pricing fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.

## Sources

- [S1] Vendor page: https://www.elastic.co (checked 2026-11-17)
- [S2] Legal notice — found from the homepage: https://www.elastic.co/legal (checked 2026-11-17)
- [S3] Privacy policy — found from the homepage: https://www.elastic.co/trust/privacy (checked 2026-11-17)
- [S4] Self-hosting / on-premises installation docs — found from the homepage: https://www.elastic.co/downloads/elasticsearch (checked 2026-11-17)
- [S5] Code repository (open-source licence) — found from the homepage: https://github.com/elastic/elasticsearch (checked 2026-11-17)
- [S6] Error capture, grouping & triage — found from sitemap: https://www.elastic.co/docs/solutions/observability/apm/errors (checked 2026-11-17)
- [S7] Error capture, grouping & triage — found from sitemap: https://www.elastic.co/docs/solutions/observability/apm/errors-ui (checked 2026-11-17)
- [S8] APM, tracing & profiling — found from sitemap: https://www.elastic.co/docs/solutions/observability/apm/transactions (checked 2026-11-17)
- [S9] APM, tracing & profiling — found from sitemap: https://www.elastic.co/docs/solutions/observability/apm/traces (checked 2026-11-17)
- [S10] Alerting, integrations & developer workflow — found from sitemap: https://www.elastic.co/docs/reference/integrations/apm (checked 2026-11-17)
- [S11] Alerting, integrations & developer workflow — found from sitemap: https://www.elastic.co/docs/reference/integrations/github (checked 2026-11-17)
- [S12] Data scrubbing, retention & volume control — found from sitemap: https://www.elastic.co/docs/reference/managed-inputs/rate-limiting (checked 2026-11-17)
- [S13] Access control, security & the vendor's reliability — found from sitemap: https://www.elastic.co/guide/en/cloud/current/ec-saml-sso.html (checked 2026-11-17)
- [S14] Access control, security & the vendor's reliability — found from sitemap: https://www.elastic.co/docs/deploy-manage/monitor/stack-audit-logging/enabling-audit-logs (checked 2026-11-17)

---

Cite as: whats-best.ai, "Elastic Observability APM — Error Tracking & APM", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/error-tracking/elastic-observability-apm

Corrections: https://whats-best.ai/correct/1993?target=page
