Batch jobs finish and disappear, while the evidence needed to investigate them must remain usable.
The customer needs a low-friction deployment pattern, and the pattern must preserve enough context for an SRE to find the right owner.
Who you’d be doing this for
“By the time someone asks about a failed job, the pod is gone and we’re chasing labels.”
Florencia Souza · Platform Engineer
Operates the Kubernetes platform where batch jobs run and supports SREs during failed-run investigations.
What is at stake
Four customer workshops surfaced the same gap: failed Kubernetes jobs emit metrics but lack a consistent owner and investigation view. You must weigh a simple deployment kit against the context SREs need after short-lived workloads disappear.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- simple installation vs investigation-ready context
- customer flexibility vs pattern reuse
- field learning now vs broader roadmap certainty
- telemetry coverage vs operational clarity
Why Grafana
Grafana and Prometheus provide the shared investigation surface for Kubernetes batch-job telemetry that customers currently assemble case by case.
Written with these in mind
Not your kind of problem? 24 more at Grafana, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.