controlling-costs

Analyze Axiom query patterns to identify ingested but unqueried data.

14|1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/axiomhq/skills --skill controlling-costs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: controlling-costs
Source: https://github.com/axiomhq/skills/tree/main/skills/controlling-costs
Command: npx skills add https://github.com/axiomhq/skills --skill controlling-costs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, axiom-query, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps operators identify data ingested but never queried, enabling cost control by surfacing waste and guiding data-management decisions.

Core Features & Use Cases

  • Query Coverage Analysis: Finds columns and field values that are ingested but rarely used, helping you prune waste.
  • Volume Estimation & Dashboards: Estimates event volumes and deploys a cost-control dashboard with ingest tracking and cost breakdowns.
  • Monitors & Optimization: Creates monitors to detect ingest spikes and query-cost anomalies, supporting proactive cost management.

Quick Start

Use the controlling-costs skill alongside axiom-sre and building-dashboards, configure your Axiom deployments, and run baseline-stats, deploy-dashboard, and create-monitors as outlined in the README to start cost optimization.

Frequently Asked Questions about controlling-costs

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

FAQPage Schema
How do I identify ingested data that is never queried in Axiom?

To identify ingested data that is never queried in Axiom, analyze query patterns using the axiom-audit and axiom-history datasets to find unqueried columns and field values, enabling targeted data pruning and waste reduction.

How do I create a cost control dashboard for Axiom data ingest?

You create a cost control dashboard for Axiom data ingest by estimating event volumes and deploying a dashboard that tracks ingest volume and breaks down costs across your infrastructure and application datasets.

Can I set up monitors to detect Axiom ingest spikes and query cost anomalies?

Yes, you can create monitors to detect Axiom ingest spikes and query cost anomalies, supporting proactive cost management by alerting you to sudden data volume increases or unusual query spending patterns across your datasets.

What prerequisites do I need to analyze Axiom query costs and data waste?

To analyze Axiom query costs and data waste, you need access to the axiom-audit and axiom-history datasets, the axiom-sre and building-dashboards skills, and command-line utilities like jq and axiom-query for data processing.

What is the best way to reduce Axiom spending on unused telemetry data?

The best way to reduce Axiom spending on unused telemetry data is to run a baseline analysis of query coverage, deploy a cost-control dashboard to surface waste, and create monitors to detect ingest spikes and query-cost anomalies.

Does the cost control workflow work with infrastructure and application datasets?

Yes, the cost control workflow works with infrastructure and application datasets, targeting them to identify data ingested but rarely used, estimate event volumes, and guide data-management decisions for cost optimization.