observability-and-instrumentation

仓库创建 2026年2月16日最近提交 21 小时前SkillHot 收录 20 天前

▸ 精选理由

提前植入遥测，显著提升排障与运维效率。

这个 Skill 做什么

为代码添加日志、指标与追踪，使生产行为可观测可诊断。

给代码埋日志、metrics 和 tracing，让线上行为可观测、可追溯，便于定位故障和设置告警。适合所有要上线到生产的功能，或当现有数据不足以解释问题时使用。特点是把可观测性和埋点在开发时一并写好，不把它当成事后补丁，并支持 alerting 与事件链路追踪。

▸ 展开 SKILL.md 英文原文

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.

开发编程可观测性日志指标追踪通用

8.1w

Stars

8.7k

Forks

仓库内 Skill

+10.0k

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/addyosmani/agent-skills/main/skills/observability-and-instrumentation/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/addyosmani/agent-skills/main/skills/observability-and-instrumentation/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Observability and Instrumentation

## Overview

Code you can't observe is code you can't operate. Observability is the ability to answer "what is the system doing and why?" from the outside, using the telemetry the code emits. Instrumentation is not a post-launch add-on — it's written alongside the feature, the same way tests are. If a feature ships without telemetry, the first user-reported bug becomes archaeology instead of a query.

## When to Use

- Building any feature that will run in production
- Adding a new service, endpoint, background job, or external integration
- A production incident took too long to diagnose ("we couldn't tell what happened")
- Setting up or reviewing alerti

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有