Key Facts
- Category
- Data Analysis
- Input Types
- textarea, file, text, select, number
- Output Type
- html
- Sample Coverage
- 4
- API Ready
- Yes
Overview
The Time Series Anomaly Detector is a powerful utility that analyzes CSV or JSON data to identify unusual spikes, drops, or outliers. By applying statistical methods like Z-Score and Interquartile Range (IQR), it automatically flags anomalies and generates a visual HTML report with a rendered chart, making it easy to spot irregular trends in your data.
When to Use
- •When you need to quickly identify abnormal spikes or drops in daily metrics like revenue, traffic, or active users.
- •When analyzing server logs or monitoring data to pinpoint latency issues or downtime events.
- •When cleaning historical datasets to remove or investigate statistical outliers before training machine learning models.
How It Works
- •Upload your time series data as a CSV, JSON, or Excel file, or paste it directly into the text area.
- •Specify the column names for your timestamps and values, then select your preferred detection method (Z-Score, IQR, or both).
- •Adjust the Z-Score threshold and seasonality window to fine-tune the sensitivity of the anomaly detection.
- •Generate a comprehensive HTML report featuring an interactive chart and a summary of all flagged anomaly segments.
Use Cases
Examples
1. Flagging a Suspicious Revenue Spike
E-commerce Analyst- Background
- An analyst is reviewing daily revenue data and notices an unusually high total for a specific week.
- Problem
- Needs to mathematically confirm which specific day is a statistical outlier compared to the rest of the week.
- How to Use
- Paste the daily revenue CSV data, set the timestamp and value columns, and select 'Z-Score + IQR' as the detection method.
- Example Config
-
Detection Method: Z-Score + IQR, Z-Score Threshold: 2.5, Seasonality Window: 0 - Outcome
- The tool generates a chart highlighting the exact day the revenue spiked to 315, confirming it as a statistical anomaly.
2. Reviewing Server Latency Drift
DevOps Engineer- Background
- A DevOps engineer is investigating intermittent slow response times on a web server.
- Problem
- Needs to separate ordinary traffic fluctuations from actual latency incidents using hourly monitoring data.
- How to Use
- Upload the server latency logs, select the Z-Score method, and apply a seasonality window to account for normal traffic patterns.
- Example Config
-
Detection Method: Z-Score, Z-Score Threshold: 2, Seasonality Window: 3 - Outcome
- The HTML report visualizes the latency trend and flags the 165ms spike at 03:00 as a true anomaly, ignoring minor fluctuations.
Try with Samples
json, csv, xmlRelated Hubs
FAQ
What data formats are supported?
You can upload CSV, JSON, or Excel files, or paste raw CSV/JSON text directly into the input field.
What is the difference between Z-Score and IQR?
Z-Score measures how many standard deviations a data point is from the mean, which is great for normally distributed data. IQR uses quartiles to find outliers and is more robust against extreme values.
How does the seasonality window work?
The seasonality window allows the tool to account for recurring patterns over a specified number of periods, helping to separate normal seasonal fluctuations from true anomalies.
Can I customize the sensitivity of the detection?
Yes, you can adjust the Z-Score threshold between 1 and 6. A lower threshold flags more points as anomalies, while a higher threshold only flags extreme outliers.
What does the output report include?
The tool generates an HTML report containing a visual chart of your time series, highlighted anomaly markers, trend slopes, and a summary of contiguous anomaly segments.