Przejdź do treści
Biblioteka skilli
DevOps i chmura · Planowanie

observability-and-reliability

/observability-and-reliability

Czyni systemy możliwymi do debugowania i niezawodnymi w działaniu: instrumentacja, alerty warte budzenia, cele serwisowe, budżety błędów, dyżury i przeglądy poincydentalne bez szukania winnych.

Repozytorium
headcount ↗
Licencja
MIT
Ostatnia zmiana repozytorium
18.10.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
2
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 18.10.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Czyni systemy możliwymi do debugowania i niezawodnymi w działaniu: instrumentacja, alerty warte budzenia, cele serwisowe, budżety błędów, dyżury i przeglądy poincydentalne bez szukania winnych.

Oryginalny opis (EN)

Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.

Jak działa

  1. Instrument for questions you have not thought of yet
  2. Alert on symptoms, not causes
  3. Objectives and error budgets
  4. Learn from incidents
  5. Sources
  6. Tooling
  7. Never
Sekcje z nagłówków SKILL.md, w oryginale · 76 linii, 525 słów
Podgląd SKILL.md
---
name: observability-and-reliability
description: Makes systems debuggable and reliably operable — instrumentation, alerting that is worth waking for, service objectives, and learning from failure. Use this to instrument a service, fix alerting that is ignored, set error budgets or reliability targets, prepare for on-call, or run a blameless post-incident review.
---

# Observability and reliability

Monitoring tells you a thing you predicted is happening. Observability lets you ask a question you
did not anticipate. Production failures are mostly the unanticipated kind.

## Instrument for questions you have not thought of yet

Emit structured events with enough context to slice afterwards — request identifiers, user or tenant,
version, dependency, outcome, duration. Free-text logs are unsearchable at volume and become
expensive noise.

Propagate a correlation identifier across every hop. Without it, a distributed system is a set of
independent stories and reconstructing one request is manual archaeology.

Measure what the user experiences at the percentile they experience it. A p50 latency graph is
mostly a graph of the people who were not affected.

## Alert on symptoms, not causes

Alert when users are affected or imminently will be. High CPU is not an alert; requests failing or
slowing is. Cause-based alerting produces pages for conditions the system handled and no page for
novel failures that hurt.

Every alert must be **actionable, urgent and specific**. If the recipient's honest response is to
look and close it, delete the alert — it is training the on-call to ignore the page, and the ignored
page is eventually the real one.

Alert fatigue is the actual reliability risk in most organizations. Fewer, better alerts beat
coverage.

## Objectives and error budgets

Set service level objectives from what users need, then treat the remainder as a budget to spend.
This converts a sterile argument between shipping and stability into arithmetic: budget remaining
means ship, budget exhausted means the next work is reliability.

Keep the internal objective tighter than any external commitment made through
`operations:service-level-management`, so you find out before the customer does.

## Learn from incidents

Post-incident review exists to find what made the failure possible and hard to detect, not who
touched it last. Human error is a starting question, never the finding: what made the error easy,
and why did nothing catch it?

Track the time to *detect* separately from time to resolve. Long detection is an observability
defect, and it is the part that repeats.

Produce a small number of real actions with owners and dates. A review generating fifteen actions
generates none.

## Sources

`references/sources.md` in this skill lists the outside authorities that settle the questions
here — what each one is authoritative for, and what you may do with it. Check them before
answering on anything they cover, and cite what you used. Most are free to read and not free
to reproduce; the use note on each is binding.

## Tooling

Metrics and traces: Datadog, Grafana with Prometheus, New Relic, Honeycomb, and similar.
Errors: Sentry, Rollbar, and similar. Logs: Elastic, OpenSearch, Loki, Splunk, and similar.

On-call and incident management: PagerDuty, Opsgenie, incident.io, FireHydrant, and similar.

Instrument with OpenTelemetry wherever you can. Vendor-specific instrumentation is the part
that makes leaving expensive.

## Never

- Page a human for something they cannot act on.
- Alert on a cause when you can alert on the symptom.
- Report reliability as an average when users experience the tail.
- Close an incident review with the finding that someone was careless.
Pliki w paczce (2)
  • SKILL.md 4 KB
  • references/sources.md 2 KB

Wersje

W bazie nie ma innych skilli o nazwie observability-and-reliability.

Migawka bazy z 13.11.2026 · wersja paczki 2ed21911da55 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 90observability-reliability
    Projektuje i prowadzi obserwowalne systemy: logi, metryki, ślady, cele usług, alerty i praktyki incydentowe dla gotowości produkcyjnej.
  • 100observability
    Pomaga instrumentować system, gdy incydentu nie da się zdiagnozować z istniejącej telemetrii: logi strukturalne, metryki, rozproszone ślady, SLO i alerty warte budzenia człowieka.
  • 100observability-monitoring-slo-implement
    Definiuje SLI, SLO i budżety błędów oraz buduje monitoring, który równoważy niezawodność z tempem wydawania zmian.
  • 100observability-slo
    Prowadzi lekką praktykę obserwowalności i SLO: SLI, cele SLO, budżety błędów, logi, metryki, ślady i alerty dla aplikacji i potoków danych.
  • 90sre-engineer
    Prowadzi prace inżyniera SRE: cele SLO i SLI, budżety błędów, monitoring i alerty w Prometheus, Grafana i OpenTelemetry, reakcję na incydenty, runbooki i przeglądy poawaryjne.
  • 100observability-slo-and-alerting
    Definiuje i prowadzi SLI, SLO, budżety błędów, dashboardy, alerty i weryfikację wdrożeń oraz pomaga zdecydować, czy ograniczyć tempo wydań.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.