技能 observability-and-instrumentation

📦

observability-and-instrumentation

Name: observability-and-instrumentation
Author: addyosmani

内容修订 r2 安全 ⚙️ 外部命令📁 文件系统访问🔑 环境变量

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.

支持: Claude Codex Code(CC)

🥉 78 青铜

使用我的智能体安装

将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。

智能体请求

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.

你的智能体仍应展示其计划，并按安全策略请求必要确认。

Agent 可读资源

当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。

Markdown 详情 GET /skills/addyosmani-observability-and-instrumentation.md 已签名 manifest GET /api/skills/addyosmani-observability-and-instrumentation/manifest 已签名 lockfile GET /api/skills/addyosmani-observability-and-instrumentation/lockfile

测试它

正在使用“observability-and-instrumentation”。 A payment retry feature needs telemetry for success rate, permanent failures, and provider latency.

预期结果:

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”。 A team wants to page on CPU usage and label metrics with customer IDs.

预期结果:

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

正在使用“observability-and-instrumentation”。 A service has alerts but no runbooks or staging verification.

预期结果:

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

安全审计

安全

v2 • 2026/9/19 打开版本化报告

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.

已扫描文件

239

分析行数

复核项

已忽略误报

最新一次完成的静态与语义审计未检测到已确认的安全发现。这并不能证明该 Skill 没有副作用。

审计者: codex 查看审计历史 →

分享与引用此报告

分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。

打开版本化报告

复制报告链接

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

Markdown 徽章

[![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 徽章

<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>

嵌入卡片

<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>

学术引用 (APA · BibTeX · CFF)

APA 引用

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 引用

@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 评分

评分依据证据置信度: 中

架构

可维护性

内容

社区

规范符合性

你能构建什么

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.

试试这些提示

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.

最佳实践

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.

避免

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.

常见问题

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.

开发者详情

作者

addyosmani

许可证

MIT

Skillstore 修订

版本提示

作者未声明版本。

仓库

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

引用

5d5054f8a23586f9b500fece1cb613a9dffc787b

维护新鲜度

2026/9/19

使用量

1 次下载 · 0 次浏览

文件结构

📄 SKILL.md

addyosmani 的更多技能

查看全部

📦

code-review-and-quality

从五个质量维度审查代码

代码变更可能隐藏正确性、安全性、架构、可读性和性能问题。此技能采用结构化审查流程，并提供按优先级排列、可执行的反馈。

编码与开发查看

📦

interview-me

Clarify User Intent Before You Build

Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.

沟通查看

📦

planning-and-task-breakdown

Plan Work Into Verifiable Tasks

Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.

效率查看

📦

documentation-and-adrs

Document Decisions and Architecture Clearly

Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.

文档查看

📦

frontend-ui-engineering

Build Accessible, Production-Ready Frontends

Frontend work can become inconsistent, inaccessible, or difficult to maintain. This skill guides component architecture, responsive layouts, state handling, and polished user experiences.

设计与创意查看

📦

security-and-hardening

Harden Applications Against Security Risks

Security reviews can miss trust boundaries and unsafe data flows. This skill supplies threat-modeling prompts, OWASP patterns, and practical review checklists.

安全与合规查看

查看全部

📦