Skip to content

Add Elastic how-tos for tracing, metrics and logging - #5308

Open
MyMirelHub wants to merge 1 commit into
dapr:v1.18from
MyMirelHub:docs/elastic-observability
Open

Add Elastic how-tos for tracing, metrics and logging#5308
MyMirelHub wants to merge 1 commit into
dapr:v1.18from
MyMirelHub:docs/elastic-observability

Conversation

@MyMirelHub

@MyMirelHub MyMirelHub commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

Thank you for helping make the Dapr documentation better!

Please follow this checklist before submitting:

  • Commits are signed with Developer Certificate of Origin (DCO - learn more)
  • Read the contribution guide
  • Commands include options for Linux, MacOS, and Windows within tabpane
  • New file and folder names are globally unique
  • Page references use shortcodes instead of markdown or URL links
  • Images use HTML style and have alternative text
  • Places where multiple code/command options are given have tabpane

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/ or metrics/.

File Section Weight
tracing/otel-collector/open-telemetry-collector-elastic.md Tracing 1100
metrics/elastic-metrics.md Metrics 8000
logging/elastic-logs.md Logging 4000

All three use the Elastic Distribution of OpenTelemetry Collector (EDOT), which is the Elastic Agent running in otel mode 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

@MyMirelHub
MyMirelHub force-pushed the docs/elastic-observability branch 2 times, most recently from d896dcc to d0b71ad Compare September 10, 2026 13:58
@MyMirelHub
MyMirelHub marked this pull request as ready for review September 10, 2026 14:04
@MyMirelHub
MyMirelHub requested review from a team as code owners September 10, 2026 14:04
@MyMirelHub
MyMirelHub force-pushed the docs/elastic-observability branch 5 times, most recently from 65ee38f to 17dadb2 Compare September 10, 2026 14:10
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
MyMirelHub force-pushed the docs/elastic-observability branch from 17dadb2 to 39e24ea Compare September 10, 2026 14:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Observability docs have no Elastic guidance for tracing or metrics

1 participant