Skip to content

Implement pipeline instrumentation #12676

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

Open
jade-guiton-dd opened this issue Mar 19, 2025 · 1 comment · May be fixed by #12812
Open

Implement pipeline instrumentation #12676

jade-guiton-dd opened this issue Mar 19, 2025 · 1 comment · May be fixed by #12812
Assignees
Labels
collector-telemetry healthchecker and other telemetry collection issues

Comments

@jade-guiton-dd
Copy link
Contributor

The "Pipeline Component Telemetry" RFC defines generic metrics and logs to monitor the data passing through the interface between pipeline components, as well as a mechanism for capturing this telemetry. It now needs to be implemented, probably as a wrapper around the Consumer interface inserted at the pipeline graph level.

This new telemetry should include the component-identifying attributes defined in the same RFC. Instead of rederiving these attributes, it should make use of the implementation of #12217.

@jade-guiton-dd jade-guiton-dd added the collector-telemetry healthchecker and other telemetry collection issues label Mar 19, 2025
@jade-guiton-dd
Copy link
Contributor Author

jade-guiton-dd commented Mar 19, 2025

cc @djaglowski

If I'm not mistaken there isn't already an issue tracking this right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
collector-telemetry healthchecker and other telemetry collection issues
Projects
Status: In Progress
3 participants