Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exporting metdata of the collected data #10927

Closed
jainaashish opened this issue Jun 13, 2022 · 3 comments
Closed

Exporting metdata of the collected data #10927

jainaashish opened this issue Jun 13, 2022 · 3 comments

Comments

@jainaashish
Copy link

Hi

Is there a way to export metadata of the collected data from OpenTelemetry collector? Fo example, for collected metric data, I want to know what is the metric name? associated Tags? timestamp of the data? etc...

Is there already an extension which can help get this metadata? if not, is it possible to build such extension with current features? Appreciate any help or pointers in this regard.

@djaglowski
Copy link
Member

@jainaashish, there is not currently, and I'm not aware of any plans at this point.

One pattern you may find useful is the metadata.yaml file that many metric-producing components maintain. Example Perhaps some automation around these files may be sufficient.

@codeboten codeboten added the needs triage New item requiring triage label Sep 16, 2022
@evan-bradley evan-bradley added waiting for author and removed needs triage New item requiring triage labels Sep 30, 2022
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Nov 30, 2022
@github-actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants