Skip to content

Conversation

@dmathieu
Copy link
Member

Mdatagen provides a fair bunch of generated tools that would be nice to use here, such as metrics generation.

@dmathieu dmathieu requested review from a team as code owners January 15, 2026 14:55
Copy link
Contributor

@rogercoll rogercoll left a comment

Choose a reason for hiding this comment

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

I think it makes sense adding this to align with collector components. As a follow, we can migrate the internal telemetry to use mdatagen tool builder.

class: receiver
codeowners:
active:
- dmathieu
Copy link
Contributor

@rogercoll rogercoll Jan 15, 2026

Choose a reason for hiding this comment

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

Should we use the ebpf-profiler approvers/maintainers group instead?

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't think we can use groups for component codeowners. We could also ignore code owners here.

"go.opentelemetry.io/collector/component"
"go.opentelemetry.io/collector/component/componenttest"
"go.opentelemetry.io/collector/confmap/confmaptest"
"go.opentelemetry.io/collector/receiver"
Copy link
Member Author

Choose a reason for hiding this comment

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

This consumertest issue will be fixed with open-telemetry/opentelemetry-collector#14434

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants