observability-and-instrumentation
Instrument Production Systems for Clear Diagnosis
Production failures are difficult to diagnose when telemetry is missing or noisy. This skill guides focused logging, metrics, tracing, alerts, runbooks, and verification.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
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.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "observability-and-instrumentation". Plan observability for a payment retry workflow.
Resultado esperado:
- Track first-attempt success, permanent failures by bounded reason, and provider latency percentiles.
- Emit structured payment events with request and payment identifiers, excluding customer data.
- Trace provider calls and alert on sustained user-visible failure rates.
Usando "observability-and-instrumentation". Review metrics that use customer identifiers as labels.
Resultado esperado:
Customer identifiers create unbounded cardinality. Keep aggregate metrics bounded and place customer-level diagnostic context in protected logs or traces.
Usando "observability-and-instrumentation". Create a runbook outline for a high error-rate alert.
Resultado esperado:
State what the alert means, provide the first diagnostic query, describe likely branches, name the escalation owner, and link relevant dashboards.
Auditoría de seguridad
SeguroAll 41 static findings are false positives caused by Markdown formatting or benign documentation examples. The skill contains no executable scripts, secret collection, path traversal behavior, system reconnaissance, prompt injection, or malicious intent.
Factores de riesgo
⚙️ Comandos externos (34)
📁 Acceso al sistema de archivos (1)
🔑 Variables de entorno (2)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/addyosmani-observability-and-instrumentation?utm_source=security_passport_badge)Insignia HTML
<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>Tarjeta para insertar
<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>Citas académicas (APA · BibTeX · CFF)
Cita APA
addyosmani. (2026). observability-and-instrumentation security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/1Cita BibTeX
@techreport{addyosmani-addyosmani-observability-and-instrumentation-2026,
author = {addyosmani},
title = {observability-and-instrumentation security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/1},
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 1)"
version: "unspecified"
type: report
authors:
- name: "addyosmani"
date-released: "2026-09-12"
url: "https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/1"
identifiers:
- type: other
value: "skillstore:addyosmani-observability-and-instrumentation:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Instrument a New Service
Add logs, metrics, traces, and alerts while building a production service.
Review Operational Readiness
Check whether a feature exposes enough evidence for reliable production support.
Improve Incident Diagnostics
Convert lessons from a slow incident into focused telemetry and current runbooks.
Prueba estos prompts
Review this feature description: [description]. List the main on-call questions, then map each question to logs, metrics, or traces.
Review these request paths and current logs: [details]. Propose stable event names, safe fields, correlation identifiers, levels, and entry-point attribution.
Given these endpoints, dependencies, SLOs, and traffic patterns: [details], design RED and USE metrics plus symptom-based alerts with justified thresholds.
Audit this architecture and instrumentation: [details]. Identify blind spots across logs, metrics, traces, context propagation, cardinality, alerts, runbooks, and verification.
Mejores prácticas
- Start with explicit operational questions and connect every signal to one question.
- Allowlist telemetry fields and verify that secrets and full personal data never enter a sink.
- Trigger staging paths and inspect actual logs, metrics, traces, alerts, and runbook links.
Evitar
- Do not add unstructured logs without stable events or correlation identifiers.
- Do not use unbounded values such as user identifiers, raw URLs, or errors as metric labels.
- Do not page on infrastructure causes when user-visible symptoms remain unmonitored.
Preguntas frecuentes
Which telemetry signal should I use?
Does this skill require OpenTelemetry?
How should correlation identifiers be handled?
How does the skill prevent metric cardinality problems?
What makes an alert actionable?
Can this skill verify production readiness?
Detalles del desarrollador
Autor
addyosmaniLicencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Ref.
5526951beaeca22519572a471618555839b53b05
Actualidad del mantenimiento
14/9/2026
Uso
0 descargas · 0 vistas
Estructura de archivos
📄 SKILL.md