Add Elastic how-tos for tracing, metrics and logging - #5308
Open
MyMirelHub wants to merge 1 commit into
Open
Conversation
MyMirelHub
force-pushed
the
docs/elastic-observability
branch
2 times, most recently
from
September 10, 2026 13:58
d896dcc to
d0b71ad
Compare
MyMirelHub
marked this pull request as ready for review
September 10, 2026 14:04
MyMirelHub
force-pushed
the
docs/elastic-observability
branch
5 times, most recently
from
September 10, 2026 14:10
65ee38f to
17dadb2
Compare
Dapr's only Elastic-specific page today is the FluentD logging how-to. There is no Elastic page under tracing or metrics, while comparable backends have one in each section. These three pages cover sending Dapr's traces, metrics and logs to Elastic using the Elastic Distribution of OpenTelemetry Collector, which is the Elastic Agent running in otel mode reading a standard collector configuration. A single collector can carry all three signals, so the pages share a deployment shape and one credentials secret. Each page is scoped to what is specific to Elastic. General tracing behaviour stays in the tracing overview and the generic collector how-to, and the metrics page links to the scrape jobs already documented in the Prometheus how-to rather than restating them. Two requirements of this pipeline are noted, because in both cases data otherwise arrives incomplete rather than absent: - cumulativetodelta on the metrics pipeline. Dapr's histograms are cumulative and the Elasticsearch exporter accepts only delta temporality, so the dapr_*_latency and *_bytes distributions are dropped without it while counters are unaffected. - json_parser after the container parser on the logs pipeline, otherwise each line stays an escaped string in body.text and Dapr's fields are not queryable. Verified against Dapr 1.18.4 and elastic-agent 9.5.3 on Kubernetes with Elasticsearch 9.1.2. Signed-off-by: MyMirelHub <15373565+MyMirelHub@users.noreply.github.com>
MyMirelHub
force-pushed
the
docs/elastic-observability
branch
from
September 10, 2026 14:11
17dadb2 to
39e24ea
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thank you for helping make the Dapr documentation better!
Please follow this checklist before submitting:
In addition, please fill out the following to help reviewers understand this pull request:
Description
Adds Elastic how-tos to the three observability sections. Elastic currently appears only in the FluentD logging page, with nothing under
tracing/ormetrics/.tracing/otel-collector/open-telemetry-collector-elastic.mdmetrics/elastic-metrics.mdlogging/elastic-logs.mdAll three use the Elastic Distribution of OpenTelemetry Collector (EDOT), which is the Elastic Agent running in
otelmode reading a standard collector configuration. One collector can carry all three signals, so the pages share a deployment shape and a single credentials secret, and cross-link to each other.Issue reference
Closes #5307