You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Argo Workflow metrics for Prometheus do not include the workflow name. This omission makes it challenging to filter metrics by specific workflows, hindering detailed workflow monitoring in Prometheus. Adding the workflow name to these metrics would enable more granular monitoring capabilities for users.
Use Cases
This feature would be useful in cases where users need to monitor individual workflows in Prometheus. For instance, if a user has multiple workflows running, they could filter by workflow name to track metrics such as duration, success rates, and resource usage for specific workflows. This feature would be invaluable for users aiming to achieve in-depth observability and better performance tracking for their workflows.
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered:
Summary
Currently, Argo Workflow metrics for Prometheus do not include the workflow name. This omission makes it challenging to filter metrics by specific workflows, hindering detailed workflow monitoring in Prometheus. Adding the workflow name to these metrics would enable more granular monitoring capabilities for users.
Use Cases
This feature would be useful in cases where users need to monitor individual workflows in Prometheus. For instance, if a user has multiple workflows running, they could filter by workflow name to track metrics such as duration, success rates, and resource usage for specific workflows. This feature would be invaluable for users aiming to achieve in-depth observability and better performance tracking for their workflows.
Message from the maintainers:
Love this feature request? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: