The issues with the Flyte User dashboard on Grafana Marketplace are due to outdated or incorrect metric names. For example, flyte:propeller:all:workflow:success_duration_ms_count should be flyte:propeller:all:workflow:event_recording:success_duration_ms_count. Additionally, some metrics like flyte:propeller:all:workflow:accepted and flyte:propeller:all:workflow:workflow_aborted show no data, and others require the 'unlabeled_ms' version to display data, which limits filtering capabilities.

Would you like more detail on how to update the metrics or further steps to resolve these issues?

Sources:

• Fix and update scripts for generating grafana dashboards
• BUG: Grafana dashboards are outdated and make stats is failing
• Hi all I was able to scrape metrics from Flyte
• Hi everyone, I have a question about metrics produced by Flyte

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

Should we publish new versions of this dashboard on Flyte releases?

@eapolinario If we can automate it, that would be amazing

BTW, I'm actively working on this. So far:

• flyte:propeller:all:workflow:accepted - it does bring data, but it's a counter and if we do the rate[5m] it all goes to zero. More investigation is needed
• flyte:propeller:all:workflow:success_duration_ms_count - needed to be flyte:propeller:all:workflow:event_recording:success_duration_ms_count: confirmed. This is a quick fix.
• CPU/Memory limits VS quota: there's a dependency on metrics that are instrumented by the kube-prometheus-stack, both for Pod and container level metrics. I'll be experimenting with this to find the quickest path for users to make use of those metrics.