← All insightsObservability

Monitoring and observability for Argo Workflows

Nir Geier, CodeWizard · 28 October 2025 · 3 min read · Intermediate

You cannot operate what you cannot see. Here is how to get useful signals out of Argo Workflows and turn them into alerts that mean something.

Argo Workflows runs container-native, DAG or step-based workflows directly on Kubernetes - great for CI, data processing and ML pipelines where each step is a container.

What to watch

  • Set limits and activeDeadlineSeconds on templates
  • Use workflow GC (TTL) to clean up finished runs
  • Store artifacts in object storage, not the cluster
  • Track error rate and latency, not just up/down
  • Alert on symptoms tied to user impact

Operate and inspect

bash
argo submit -n argo build.yaml --watch
argo list -n argo
argo logs -n argo @latest

Keep it healthy

  • Scope the workflow ServiceAccount with least-privilege RBAC
  • Use separate namespaces per team/tenant

Want senior help putting Argo Workflows to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult