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

Describe configtelemetry levels #10286

Closed
atoulme opened this issue May 31, 2024 · 1 comment · Fixed by #10365
Closed

Describe configtelemetry levels #10286

atoulme opened this issue May 31, 2024 · 1 comment · Fixed by #10365

Comments

@atoulme
Copy link
Contributor

atoulme commented May 31, 2024

          Prior to this package's stabilization, I would love it if there were more guidance on what each of the levels are for. Right now the documentation is very vague and I think the differences between normal & detailed are not specific enough. This is almost a flavor of #7543 where that metric could have been enabled only in the "detailed" configuration, however, reserving "detailed" that way wasn't an option because we put many metrics behind "detailed" that I would argue belong more in the "normal" or "basic" levels ([ex](https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/batchprocessor/metrics.go#L65-L67) of a detailed metric that IMO should be a "normal" metric).

Originally posted by @jaronoff97 in #10277 (comment)

@atoulme
Copy link
Contributor Author

atoulme commented Jun 7, 2024

@jaronoff97 I'm trying to understand if this should block the package stability. Are you looking for better documentation and guidelines or changes to the behavior of the package content? If it's the former, I'd vouch for removing this from the 1.0 milestone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant