trace-sampling

Configures trace sampling rates and retention windows for DevOps workflows.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill trace-sampling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trace-sampling
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/trace-sampling
Command: npx skills add https://github.com/AesopScott/mojo --skill trace-sampling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of ballooning storage costs and excessive token usage by implementing intelligent sampling and retention policies for system traces.

Core Features & Use Cases

  • Cost Control: Define retention budgets to automatically age out or sample traces, preventing runaway storage expenses.
  • Harness Management: Provides a structured runbook for modifying Trace harness configurations to balance auditability with resource efficiency.
  • Use Case: When debugging high-traffic API routes, use this Skill to sample only 10% of successful requests while retaining 100% of error traces to maintain visibility without the storage overhead.

Quick Start

Use the trace-sampling skill to define a new retention policy that limits trace storage to a maximum of thirty days for the production API harness.

Frequently Asked Questions about trace-sampling

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce trace storage costs for high-volume telemetry data?

Reduce trace storage costs by configuring intelligent sampling rates and retention windows to automatically age out unnecessary traces, preventing runaway storage expenses while maintaining observability.

Can I retain 100% of error traces while sampling successful API requests?

Yes, you can sample a percentage of successful requests while retaining all error traces. This maintains debugging visibility for failures without the storage overhead of keeping every successful trace.

What is the best way to configure trace retention windows for a production harness?

Configure trace retention by defining a structured policy that limits trace storage to a maximum age, such as thirty days for production, balancing auditability with resource efficiency to control costs.

How does trace sampling work to balance system observability and budget limits?

Trace sampling balances observability and budgets by selectively capturing a subset of telemetry data based on configurable rates and audit logging thresholds, ensuring operational efficiency without losing critical visibility.

Do I need specific dependencies to manage trace sampling and retention policies?

No dependencies are required to manage trace sampling and retention policies. The configuration applies directly to infrastructure engineering and DevOps workflows to handle budget-conscious telemetry management.

When should I not use aggressive trace sampling rates in my observability workflow?

Avoid aggressive trace sampling when full auditability is required for compliance or when debugging intermittent high-traffic API issues, as low sampling rates may drop the exact traces needed for root cause analysis.