Fähigkeiten observability-and-instrumentation
📦

observability-and-instrumentation

Inhaltsrevision r2 Sicher ⚙️ Externe Befehle📁 Dateisystemzugriff🔑 Umgebungsvariablen

Instrument Production Systems with Clear Telemetry

Production teams need reliable evidence when services fail, slow down, or behave unexpectedly. This skill helps design useful logs, metrics, traces, alerts, and verification steps.

Unterstützt: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 78 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage
Review the Skillstore skill "observability-and-instrumentation" from https://skillstore.io/skills/addyosmani-observability-and-instrumentation.md and its manifest at https://skillstore.io/api/skills/addyosmani-observability-and-instrumentation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.

Agent-lesbare Ressourcen

Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.

Markdown-Detailseite GET /skills/addyosmani-observability-and-instrumentation.md Signiertes manifest GET /api/skills/addyosmani-observability-and-instrumentation/manifest Signiertes lockfile GET /api/skills/addyosmani-observability-and-instrumentation/lockfile

Testen

„observability-and-instrumentation“ wird verwendet. A payment retry feature needs telemetry for success rate, permanent failures, and provider latency.

Erwartetes Ergebnis:

  • Use structured events for payment outcomes and provider error codes.
  • Add a latency histogram with percentiles for provider calls.
  • Trace a sampled checkout request and retain error traces.

„observability-and-instrumentation“ wird verwendet. A team wants to page on CPU usage and label metrics with customer IDs.

Erwartetes Ergebnis:

Use user-facing error rate or latency for paging, and move customer identifiers to logs or traces. Keep metric labels bounded.

„observability-and-instrumentation“ wird verwendet. A service has alerts but no runbooks or staging verification.

Erwartetes Ergebnis:

  • Link every alert to a short runbook with meaning, first check, and escalation path.
  • Test induced failures and confirm telemetry reaches the correct channel.

Sicherheitsaudit

Sicher
v2 • 19.9.2026 Versionsbericht öffnen

All 41 static findings are false positives caused by Markdown backticks, documentation syntax, benign example code, or a relative reference. The reviewed skill contains no executable commands, credential exfiltration, unsafe file access, or prompt injection.

1
Gescannte Dateien
239
Analysierte Zeilen
0
Prüfelemente
0
Falschmeldungen ignoriert

Risikofaktoren

⚙️ Externe Befehle (34)
SKILL.md:21 SKILL.md:22 SKILL.md:23 SKILL.md:31-38 SKILL.md:38-46 SKILL.md:46-56 SKILL.md:56-58 SKILL.md:58-68 SKILL.md:68-74 SKILL.md:74-75 SKILL.md:75-76 SKILL.md:76-77 SKILL.md:77-81 SKILL.md:81-89 SKILL.md:89-93 SKILL.md:93-95 SKILL.md:95 SKILL.md:102-106 SKILL.md:106-112 SKILL.md:112-114 SKILL.md:114-123 SKILL.md:123-127 SKILL.md:127-130 SKILL.md:130-138 SKILL.md:138-148 SKILL.md:148-150 SKILL.md:150 SKILL.md:156-161 SKILL.md:161-174 SKILL.md:174-178 SKILL.md:178-181 SKILL.md:181-184 SKILL.md:184-194 SKILL.md:194
📁 Dateisystemzugriff (1)
SKILL.md:238
🔑 Umgebungsvariablen (2)
SKILL.md:101 SKILL.md:101
Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.
Geprüft von: codex Audit-Verlauf anzeigen →
Diesen Bericht teilen & zitieren

Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.

Versionsbericht öffnen
Sicherheitsbewertung

Berichtslink kopieren

https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-observability-and-instrumentation/security.svg)](https://skillstore.io/skills/addyosmani-observability-and-instrumentation?utm_source=security_passport_badge)

HTML-Badge

<a href="https://skillstore.io/skills/addyosmani-observability-and-instrumentation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-observability-and-instrumentation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Einbettungskarte

<iframe src="https://skillstore.io/embed/skills/addyosmani-observability-and-instrumentation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Wissenschaftliche Zitate (APA · BibTeX · CFF)

APA-Zitat

addyosmani. (2026). observability-and-instrumentation security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2

BibTeX-Zitat

@techreport{addyosmani-addyosmani-observability-and-instrumentation-2026, author = {addyosmani}, title = {observability-and-instrumentation security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "observability-and-instrumentation security audit report (audit version 2)" version: "unspecified" type: report authors: - name: "addyosmani" date-released: "2026-09-19" url: "https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2" identifiers: - type: other value: "skillstore:addyosmani-observability-and-instrumentation:audit:2" description: "Skillstore immutable audit report identifier"

Skillstore-Score

Warum dieser Score Evidenzvertrauen: Mittel
55
Architektur
85
Wartbarkeit
87
Inhalt
65
Gemeinschaft
91
Spezifikationskonformität

Was Sie erstellen können

Instrument a New Endpoint

Define the endpoint questions, add structured logs, and select RED metrics with bounded labels.

Improve Incident Diagnosis

Add correlation IDs, distributed tracing, and actionable alerts so on-call engineers can follow a failing request.

Review Production Readiness

Use the verification checklist to assess telemetry coverage, secret handling, alert quality, and staging validation.

Diese Prompts ausprobieren

Start with Observability Questions 
Review this feature description and list two to four questions an on-call engineer must answer. Map each question to a log, metric, or trace.
Design Structured Logging 
Design structured log events for this endpoint. Include stable event names, safe fields, log levels, correlation IDs, and entry-point attribution.
Plan Service Telemetry 
Create an observability plan for this service and its dependencies. Cover RED metrics, bounded labels, OpenTelemetry traces, sampling, and symptom-based alerts.
Audit an Instrumentation Change 
Review this instrumentation diff against the observability checklist. Identify missing signals, cardinality risks, sensitive data exposure, alert weaknesses, and staging tests.

Bewährte Praktiken

  • Start from concrete on-call questions and map every signal to one question.
  • Allowlist telemetry fields and exclude secrets, tokens, passwords, and full PII.
  • Verify telemetry and alert delivery in staging before calling the work complete.

Vermeiden

  • Adding unstructured logs without a stable event name or correlation ID.
  • Using user IDs, raw URLs, or error text as metric labels.
  • Paging on infrastructure causes without a user-facing symptom or runbook.

Häufig gestellte Fragen

What does this skill help me instrument?
It guides logging, metrics, distributed tracing, alerting, runbooks, and telemetry verification for production features.
Does it recommend a specific monitoring vendor?
No. It favors vendor-neutral OpenTelemetry concepts and explains how to adapt them to common backends.
Why are structured logs important?
Structured fields make events searchable, consistent, and easier to correlate during incidents.
How should I choose metric labels?
Use small fixed sets such as route templates, status classes, and provider names. Keep unbounded values in logs or traces.
Should every alert page an engineer?
No. Page only for actionable user-facing symptoms. Use tickets for degradations that can wait.
How do I validate new telemetry?
Induce a staging failure, inspect structured logs, send test traffic, follow a trace, and test each alert and runbook link.

Entwicklerdetails

Lizenz

MIT

Skillstore-Revision

r2

Versionshinweis

Der Autor hat keine Version angegeben.

Repository

https://github.com/addyosmani/agent-skills/tree/c004a74784a08295d52749b04cda634125b9a581/skills/observability-and-instrumentation

Ref.

5d5054f8a23586f9b500fece1cb613a9dffc787b

Aktualität der Wartung

19.9.2026

Nutzung

1 Downloads · 0 Aufrufe

Dateistruktur

📄 SKILL.md