Flyte enables production-grade orchestration for machine learning workflows and data processing created to accelerate local workflows to production.

Flyte

hi y’all! I am using <https://grafana.com/grafana/dashboards/13980> and see that the workflow query uses
```label_values(flyte:propeller:all:collector:flyteworkflow, wf)```
When I look at my propeller prom metrics however the `wf` label is empty. Why?

```# HELP flyte:propeller:all:collector:flyteworkflow Current FlyteWorkflow levels per instance of propeller
# TYPE flyte:propeller:all:collector:flyteworkflow gauge
flyte:propeller:all:collector:flyteworkflow{domain="development",project="testproject",task="",wf=""} 1```

<@USPH1DVD2>, it seems it has the domain right?
```flyte:propeller:all:collector:flyteworkflow{`domain="development"`,project="testproject",task="",wf=""}```


cc <@U029U35LRDJ> do you know this off the top?

unfortunately no. i should probably spend a bit cycling through all the emitted metrics. i can look into it?

OK, it looks like the `flyte:propeller:all:collector` metric is used for "metrics that show the current number of Flyte workflows, by project and domain". So basically, we periodically <https://github.com/flyteorg/flytepropeller/blob/abc8a898536dc6905f02df866d09f6d057fa97cf/pkg/controller/controller.go#L250|list all FlyteWorkflow CRDs> and <https://github.com/flyteorg/flytepropeller/blob/abc8a898536dc6905f02df866d09f6d057fa97cf/pkg/controller/controller.go#L260-L261|emit a metric> showing aggregate numbers for project / domain combinations. Since we are showing combined counts over project / domains populating a wf and task value doesn't really make sense in this context. I'm not sure if the `task` and `wf` labels have been orphaned by updates, or if they have been applied incorrectly ... looking a little deeper.