detect-anomalies

Identify anomalies in Axiom datasets using statistical analysis on logs, metrics, and traces.

59|11|Updated Oct 19, 2020
One-click install
npx skills add https://github.com/axiomhq/cli --skill detect-anomalies
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: detect-anomalies
Source: https://github.com/axiomhq/cli/tree/main/skills/detect-anomalies
Command: npx skills add https://github.com/axiomhq/cli --skill detect-anomalies

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify anomalies in Axiom datasets using statistical analysis to reveal unusual patterns.

Core Features & Use Cases

  • Volume-based anomaly detection using z-scores to compare recent vs baseline data
  • New value detection to surface previously unseen categorical values
  • Statistical outliers and latency changes detection across time windows
  • Generate anomaly reports suitable for collaboration and alerting

Quick Start

Set up your environment and run an example anomaly check on a dataset named logs: axiom query "['logs'] | where _time >= ago(1h) | summarize count() by bin(_time, 5m)" --start-time -1h -f json

Frequently Asked Questions about detect-anomalies

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

FAQPage Schema
How do I detect anomalies in Axiom datasets using statistical analysis?

Anomaly detection in Axiom datasets uses statistical analysis to compute baselines and reveal unusual patterns. It applies z-scores to compare recent data against baselines, surfacing volume spikes, new categorical values, and latency changes across logs, metrics, and traces.

What statistical methods are used for identifying volume spikes and latency changes in observability data?

Volume spikes and latency changes are identified using z-scores to compare recent data against baseline data. This statistical approach detects deviations across time windows, surfacing unusual patterns and outliers in observability datasets like logs, metrics, and traces.

How much historical data do I need to compute baselines and detect deviations in Axiom?

Computing baselines and detecting deviations requires sufficient historical data. You need at least 30 samples per bucket and 24 hours of data in your Axiom datasets to accurately identify statistical outliers and unusual patterns.

Can I detect new categorical values that were previously unseen in my logs and metrics?

New value detection surfaces previously unseen categorical values in logs and metrics. By analyzing historical data to establish known values, the anomaly detection process identifies new entries that deviate from the established baseline.

How do I run an anomaly check on an Axiom dataset to summarize counts over a time window?

Run an anomaly check by querying your Axiom dataset to summarize counts over time windows. Use standard Axiom queries like `['logs'] | where _time >= ago(1h) | summarize count() by bin(_time, 5m)` to compute baselines and detect deviations.

What types of observability data support anomaly detection for statistical outliers?

Anomaly detection for statistical outliers applies to logs, metrics, and traces. It detects volume spikes, new values, and latency changes across these observability data types by computing baselines and identifying deviations using standard Axiom queries.