Switch to `container` resource detector in declarative configuration doc after 1.46.0 rebase

Open Beginner friendly
#683 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
75/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Find the declarative configuration documentation and read the section that names the resource detector. Update the detector name from containerid to container, as specified; done when the documentation uses container there.

Written by the indexing model from the issue text.

Description

containerid will continue to work but per specification the resource detector should be called container.

Dominant language
Python
Stars
16
Forks
20
Avg merge
1d 14h
Merged PRs (30d)
23

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/elastic-otel-python

All issues in elastic/elastic-otel-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.