Skip to content
Skills Library
DevOps & cloud · Analysis

outage-tracking

/outage-tracking

Track outages for trends: taxonomy, budget impact, and planning inputs per Google SRE. Use for reliability reporting and quarterly planning.

Licence
MIT
Last repository change
30.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Track outages for trends: taxonomy, budget impact, and planning inputs per Google SRE. Use for reliability reporting and quarterly planning.

Original author description

Track outages for trends: taxonomy, budget impact, and planning inputs per Google SRE. Use for reliability reporting and quarterly planning.

How it works

  1. When to use
  2. Principles
  3. Workflow
  4. Decision guide
  5. Output template
  6. Anti-patterns
  7. Related skills
  8. Canonical references
  9. Agent notes
Original SKILL.md headings · 56 lines, 184 words
SKILL.md preview
---
name: outage-tracking
description: >-
  Track outages for trends: taxonomy, budget impact, and planning inputs per Google SRE. Use for reliability reporting and quarterly planning.
---

# Outage Tracking

**Domain:** `operations`  
**Sources:** SRE Book 1e Ch16, Workbook App C

## When to use

- Building outage database / scorecards
- Quarterly reliability review

## Principles

- What gets tracked gets improved — with care to avoid vanity metrics.
- Tag by cause class, detection, mitigation, CUJ, budget burn.
- Use trends to fund reliability themes, not blame teams.

## Workflow

1. Define mandatory outage record fields.
2. Ensure every Sev/postmortem feeds the tracker.
3. Monthly rollup: top classes, MTT* , budget consumers.
4. Feed top classes into planning as P0 themes.

## Decision guide

- If scorecards are gamed → shift to outcome SLOs + learning quality.

## Output template

```markdown
# Outage rollup
- Window:
- Count by severity/class:
- Worst budget burns:
- Themes for planning:
```

## Anti-patterns

- Weaponized scorecards without context.

## Related skills

`learning-from-incidents`, `error-budget-policy`, `production-meetings`

## Canonical references

- [Tracking Outages](https://sre.google/sre-book/tracking-outages/)

## Agent notes

- Prefer live data (metrics, tickets, pages) over generic advice.
- Cite which Google SRE source informed a recommendation when useful.
- Keep outputs tactical: decisions, owners, next actions.
Files in this package (2)
  • SKILL.md 1 KB
  • reference.md 1 KB

Versions

The database has no other skills named outage-tracking.

Database snapshot: 13.11.2026 · package version 8182d35be0a9 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100cloud-reliability
    Apply SRE in cloud and hybrid environments: shared responsibility, managed services, multi-cloud observability, and platform trends from Google SRE 2e and sre.google/cloud. Use for cloud architecture and ops model design.
  • 90reliability-sre
    Apply SRE principles (SLO, Error Budget, Chaos Engineering). Use when: sre, reliability, slo, sli, error budget, chaos engineering, postmortem, incident, oncall.
  • 100sre-foundations
    Teach and apply core Google SRE foundations: reliability as a feature, software engineering applied to operations, sociotechnical systems, and when SRE is the right model. Use when onboarding SREs, explaining what SRE is, framing reliability work, or starting a learning path.
  • 91sre-reliability-engineering
    Use when building reliable and scalable distributed systems.
  • 100sre-incident-response
    Use when responding to production incidents following SRE principles and best practices.
  • 100sre-expert
    Expert-level site reliability engineering, SLOs, incident management, and operational excellence. Use when the user mentions reliability, monitoring, incident management, SLOs, or observability, or when the task involves SRE Fundamentals, Reliability Practices, SRE Principles, or On-Call.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.