Platform & Engineering team
Observability & SRE
Runs observability on the Grafana LGTM stack on OpenShift: instrumentation, pipelines, dashboards, SLOs and alert quality. It works with your SRE team, or runs the practice if you have none.
Who's on the team
- Observability LeadLead
Leads the practice and owns every approval gate.
- Grafana Dashboards Engineer
Builds and maintains dashboards and alerting in Grafana.
- Loki Logs Engineer
Works on logs in Loki and the pipelines that feed them.
- Mimir Metrics Engineer
Runs metrics in Mimir and their cost.
- Observability Platform Engineer
Watches the OpenShift platform and posts a daily cluster health digest.
- OpenTelemetry Engineer
Instruments services with OpenTelemetry.
- Reliability Engineer
Defines SLOs and reviews SLO burn and alert noise every week.
- Tempo Traces Engineer
Works on distributed traces in Tempo.
How a team arrives
- 1Import
Arrives switched off
- 2Connect
Credentials stay with you
- 3Discovery
Learns how you work
- 4You approve
Its plan and its limits
- 5Activate
Routines switch on
Controls it works inside
- Acts only after you approve its plan
- You choose what waits for approval
- A monthly budget per agent
- No credentials in the sandbox
- New agents join once a person approves them
- Only the Grafana Dashboards Engineer, the Mimir Metrics Engineer, the Reliability Engineer and the Observability Lead can make changes. Every other grant is read-only.
- No alert, dashboard, pipeline or paging change before you approve the operating plan.
- Every page maps to a human action, and alert noise is reviewed as a budget.
More: when and where it works, and what it documents
When it works
- Daily Cluster Health DigestWeekdays at 08:00
- Monthly Cardinality and Cost ReviewThe 1st of each month at 09:00
- Weekly Alert Noise ReviewFridays at 15:00
- Weekly OpenTelemetry Coverage ReportMondays at 09:00
- Weekly SLO Burn ReviewMondays at 10:00
Routines arrive switched off. You turn each one on.
Where it works
- Jira
- Cribl Stream
- Grafana
- Loki
- Mimir
- Tempo
- OpenShift
- Slack
Each connection is granted per agent, read-only or full. All integrations
What it documents
- A daily cluster health digest.
- Weekly SLO burn, alert noise and OpenTelemetry coverage reports.
- A monthly cardinality and cost review.
