Collector Authoring And Review

Start here for collector changes and reviews, then follow the affected domain or framework. Selection and action boundaries are owned by AGENTS.md#skill-selection: reading a recipe does not authorize its generation, installation, credential setup or live operations. A review uses existing design/validation evidence and reports concrete gaps.

Shared Collector Contracts

Every collector review needs the applicable shared contracts below, including a performance-focused review. These summaries point to the detailed owner sections; expand further according to changed behavior and dependencies.

For a contract-preserving parser optimization, these shared constraints and the parser/framework evidence may suffice. For ownership, caching or lifecycle costs, also expand the design references. A lens does not exempt applicable contracts or require every reference in this skill.

Route By Task

Use each row for implementation or review of that surface. Implementation-only notes and commands are not review prerequisites. In Go work, read src/go/AGENTS.md and the relevant subtree instructions first.

Expand Only The Relevant Detail

• Metrics, labels, chart shape, grouping and priorities: ./collector-practices.md#3-structuring-dashboards. SNMP, statsd, OTEL and Prometheus shaping mechanisms: ./dashboard-shaping.md.
• Remote targets and generated nodes: ./collector-practices.md#19-remote-monitored-systems-and-vnodes and the framework/design owners it cites. Multiple targets alone do not justify a vnode per target.
• Language/platform choice, build loop, eBPF migration, data types and domain patterns: ./landscape-and-domains.md. Open the relevant section; preserve its CO-RE versus legacy validation distinction.
• Implementation quality and delivery checks: ./collector-practices.md#4-production-quality-criteria--pre-pr-checklist. Reviewers use applicable criteria and existing evidence; authors complete the authorized validation.
• Other source owners: ./collector-practices.md#6-canonical-documentation-pointers.

Maintaining This Skill

Capture reusable, evidence-backed gaps under AGENTS.md#knowledge-capture. During authorized implementation, update this skill and coupled pointers in the same task; answer-only findings follow the owner's local-note route. Keep framework-specific mechanisms with their owners and preserve the domain detail when improving the entry. When a pointer misled the task, capture the reusable failure mode with its correction. Describe coupled skill updates in the PR when one is created; do not preserve obsolete instructions as current guidance.