[OTel Profiling] Document receiver configuration and datastreams

Open
#21,458 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
kubernetes
Domain
documentation

Research direction

Start by locating the OTel Profiling receiver configuration and documentation entry points, then verify the deployment guidance for EDOT, the upstream collector, Kubernetes DaemonSets, and the kube-stack operator. Document the data streams it writes to and whether profiling metrics are shipped; done means users can answer all four questions from the updated documentation.

Written by the indexing model from the issue text.

Description

The following information must be added to provide more information to users:

  • How should it be used? EDOT? Upstream collector?
  • To which data streams it writes data to?
  • How should it be deployed? k8s daemonset? k8s kube-stack operator?
  • Does it ship with profiling metrics?
Dominant language
Handlebars
Stars
334
Forks
652
Avg merge
1d 22h
Merged PRs (30d)
241

Contributor guide

Open the contributing guide

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/integrations

All issues in elastic/integrations

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.