Skip to content

document app_server resource detector with declarative config#2898

Open
SylvainJuge wants to merge 3 commits into
open-telemetry:mainfrom
SylvainJuge:app_server-dc
Open

document app_server resource detector with declarative config#2898
SylvainJuge wants to merge 3 commits into
open-telemetry:mainfrom
SylvainJuge:app_server-dc

Conversation

@SylvainJuge
Copy link
Copy Markdown
Contributor

The app_server resource provider is compatible with declarative configuration but lacks documentation about it.

This PR provides a sample yaml configuration to document usage with declarative configuration.

@github-actions github-actions Bot requested review from breedx-splk and laurit June 2, 2026 12:29
@SylvainJuge SylvainJuge marked this pull request as ready for review June 2, 2026 13:21
@SylvainJuge SylvainJuge requested a review from a team as a code owner June 2, 2026 13:21
Copilot AI review requested due to automatic review settings June 2, 2026 13:21
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds documentation describing how to configure the app server resource detector via OpenTelemetry declarative YAML config.

Changes:

  • Documented declarative YAML configuration for the app server resource detector
  • Clarified detector ordering (app_server before service) and precedence vs resource.attributes

Comment on lines +45 to +46
The `app_server` detector needs to be listed before the `service` detector to allow overriding
the `service.name` attribute with the `OTEL_SERVICE_NAME` environment variable. Also, the resource
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in the resource detectors, the last has higher priority over the previous detectors, so the order is correct.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants