Skip to content

Update limitations.md #1741

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 16, 2025
Merged

Update limitations.md #1741

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
656755b
Update limitations.md
theletterf Jun 16, 2025
1dc8df9
Fix links
theletterf Jun 16, 2025
514f4f1
Merge branch 'main' into theletterf-note-on-limitations
theletterf Jun 16, 2025
4c00bba
Update limitations.md
theletterf Jun 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions solutions/observability/apm/limitations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@

## OpenTelemetry logs [apm-open-telemetry-logs-intake]

* [preview] The OpenTelemetry logs intake via Elastic is in technical preview.
* The OpenTelemetry logs intake throgh the [APM Server](/solutions/observability/apm/upstream-opentelemetry-collectors-language-sdks#apm-open-telemetry-proxy-apm) is in technical preview. Note that logs ingest through the [EDOT Collector](opentelemetry://reference/edot-collector) or the [Managed OTLP endpoint](/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint) is fully supported. {applies_to}`product: preview`

Check failure on line 24 in solutions/observability/apm/limitations.md

View workflow job for this annotation

GitHub Actions / preview / build 

`/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint` does not exist. resolved to `/github/workspace/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint

Check failure on line 24 in solutions/observability/apm/limitations.md

View workflow job for this annotation

GitHub Actions / preview / build 

'reference/edot-collector' is not a valid link in the 'opentelemetry' cross link index: https://elastic-docs-link-index.s3.us-east-2.amazonaws.com/elastic/opentelemetry/main/links.json

Check failure on line 24 in solutions/observability/apm/limitations.md

View workflow job for this annotation

GitHub Actions / preview / build 

`/solutions/observability/apm/upstream-opentelemetry-collectors-language-sdks` does not exist. resolved to `/github/workspace/solutions/observability/apm/upstream-opentelemetry-collectors-language-sdks
* The application logs data stream (`app_logs`) has dynamic mapping disabled. This means the automatic detection and mapping of new fields is disabled (see issue [#9093](https://github.com/elastic/apm-server/issues/9093)).

## OpenTelemetry Line Protocol (OTLP) [apm-open-telemetry-otlp-limitations]
Expand Down Expand Up @@ -50,4 +50,4 @@

Using the [tailsamplingprocessor](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/tailsamplingprocessor) in the OpenTelemetry Collector comes with an important limitation. Elastic’s APM backend calculates span and transaction metrics based on the incoming span events. These metrics are accurate for 100% sampling scenarios. In scenarios with probabilistic sampling, Elastic’s APM backend is being informed about the sampling rate of spans and can extrapolate throughput metrics based on the incoming, partial data. However, with tail-based sampling there’s no clear probability for sampling decisions as the rules can be more complex and the OpenTelemetry Collector does not provide sampling probability information to the Elastic backend that could be used for extrapolation of data. Therefore, there’s no way for Elastic APM to properly extrapolate throughput and count metrics that are derived from span events that have been tail-based sampled in the OpenTelemetry Collector. In these scenarios, derived throughput and count metrics are likely to be inaccurate.

Therefore, we recommend using Elastic’s native tail-based sampling when integrating with OpenTelemetry.
Therefore, we recommend using Elastic’s native tail-based sampling when integrating with OpenTelemetry.
Loading