mcpField
O
observability-cost-governance-review

observability-cost-governance-review

github.com/sylphxaiCloud & DevOps140 installsUpdated today
Repository

About observability-cost-governance-review

This skill turns observability cost governance questions into planning artifacts with owners, gates, metrics, and recovery paths. It is for teams managing logs, metrics, and traces while balancing costs, retention, privacy, and incident response needs.

Key features

  1. 01Identify telemetry sources, costs, and incident needs
  2. 02Classify signals by purpose
  3. 03Set sampling, retention, and aggregation policies
  4. 04Plan redaction, budgets, and cost allocation
  5. 05Create governance plans, checklists, and review cadence

Use cases

  1. 01Review retention periods for logs and traces
  2. 02Set cost controls for high-cardinality labels
  3. 03Balance telemetry budgets with incident response needs

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill observability-cost-governance-review

After installing, type/observability-cost-governance-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/observability-cost-governance-patterns.md

Details

From the project README

Observability Cost Governance Review

Use this skill to convert a observability cost governance, logs, metrics, traces, sampling, retention, cardinality, privacy, budgets, and incident usefulness question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify telemetry sources, owners, incident needs, cost drivers, retention requirements, sensitive fields, cardinality, and budget constraints.
  2. Read references/observability-cost-governance-patterns.md.
  3. Classify telemetry as critical signal, debugging detail, audit log, product analytics, security event, performance profile, or low-value noise.
  4. Define sampling, retention, aggregation, redaction, ownership, budgets, dashboard/alert policy, cost allocation, and deletion/exception rules.
  5. Produce observability governance plan, state machine, decision table, event schema, checklist, and cost-review cadence.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not cut telemetry that is required for incident response, security audit, billing reconciliation, or customer support without replacement.
  • Do not reduce cost by dropping trace correlation, redaction, or critical SLO signals.
  • Do not allow unbounded high-cardinality labels or raw payload logs.
  • Do not keep expensive debug logs, session replay, or traces forever without owner and retention reason.

Output format

Observability context:
Signal / owner / cost driver / incident need:

Observability cost plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Signals, retention, and budgets:
- <item> -> <policy, metric, edge case, support note>

Exception and cost-review policy:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported