argoproj / argoproj/argo-workflows

Real-time gauge metrics would be useful

Open
#12,243 4 comments 7 reactions 0 assignees View on GitHub
area/telemetry/metrics
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 20h
Merged PRs (30d)
138

Description

# Summary

It isn't possible to emit a real-time gauge metric for counting how many of a workflow are currently active. And probably other things than just workflow.duration which is the only possible one right now.

## Use Cases

If you'd like a prometheus metric per workflow category (ignoring how we define categories) you must place a dummy task at the start of a workflow run to emit that counter. It would be far saner to just emit it as a workflow level counter metric.

---

**Message from the maintainers**:

Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

Contributor guide

Open the contributing guide

Research direction

Start by tracing how the existing workflow.duration metric is emitted and how workflow-level metrics are defined. Clarify which real-time gauge metrics and workflow categories are required, then determine the tests needed to verify their values and lifecycle behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, prometheus
Domain
observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.