AgentSkillsCN

instrumentation-planning

规划 Web 应用程序中要测量的内容。适用于开始可观测性或优先安排仪器时使用。

SKILL.md
--- frontmatter
name: instrumentation-planning
description: Plan what to measure in web applications. Use when starting observability or prioritizing instrumentation.
triggers:
  - "planning telemetry"
  - "prioritize instrumentation"
  - "what should I track"
priority: 1

Instrumentation Planning

Strategic guidance for what to measure in web applications.

Core Question

For each user job, ask:

  • •Did it complete? → completion rate
  • •How long? → duration (p50, p95, p99)
  • •What failed? → error type, context
  • •Did they give up? → drop-off rate
  • •How smooth? → Core Web Vitals, friction signals

Priority Tiers

TierFocusPriority
1Errors + source mapsP0 - Day 1
2Core Web VitalsP0 - Day 1
3User context + breadcrumbsP0 - Week 1
4Route transitions + API tracingP1 - Week 2
5Business metrics + synthetic testsP2 - Month 1

Core Web Vitals Thresholds

MetricGoodNeeds ImprovementPoor
LCP≤2.5s≤4.0s>4.0s
INP≤200ms≤500ms>500ms
CLS≤0.1≤0.25>0.25

OTel-Compatible Naming

Use now for easier migration later:

  • •http.request.method not method
  • •http.request.duration not apiCallTime
  • •url.path not page

Anti-Patterns

See references/anti-patterns.md for:

  • •Measuring everything (noise, bundle bloat)
  • •Skipping source maps
  • •Blocking main thread
  • •PII in breadcrumbs

Implementation Details

See references/instrumentation-patterns.md for:

  • •Detailed 5-tier checklist
  • •Span naming conventions
  • •Sampling strategies

See references/jtbd.md for Jobs-to-be-Done framework.

Related Skills

  • •skills/core-web-vitals - Tier 2 implementation
  • •skills/error-tracking - Tier 1 implementation
  • •skills/source-map-setup - Tier 1 implementation