Anomaly Impact Alert
Anomaly Impact Alert — a lightweight Python toolkit for detecting anomalies, forecasting metrics, explaining deviations, and sending alerts (e.g. via Telegram)
Purpose
This library helps analytics and monitoring teams automatically:
- Detect abnormal metric values in time-series data
- Forecast expected ranges (with confidence intervals)
- Explain the drivers behind changes (countries, platforms, etc.)
- Send structured alerts to Telegram
Demo Notebook
Anomaly Impact Alert is a lightweight Python toolkit for:
- Anomaly detection (Z-Score, CI, STL, SESD, LOF, Isolation Forest, and more)
- Forecasting metrics (Prophet, ETS, STL ensemble)
- Explaining deviations (impact decomposition by segments)
- Sending alerts (e.g., via Telegram)
This notebook demonstrates how to use anomaly_impact_alert in practice:
- Data preparation
- Anomaly detection workflow
- Time-series forecasting
- Contribution analysis across segments
- Automated alert generation and explanations
Try it in Google Colab: 👉 Open in Colab
Example Output
Detection visualization
Shows detected anomalies (red dots), confidence intervals, and model outputs:
Telegram alert
Example of an automatically formatted alert with top contributing segments:
Quick Start
pip install anomaly_impact_alert
Try it in Google Colab: 👉 Open in Colab
Modules Overview
| Module | Description |
|---|---|
anomaly_detector |
Detects anomalies using statistical and ML methods |
forecast |
Forecasts values and confidence intervals |
impact_explainer |
Explains which dimensions cause deviations |
alert_bot_telegram |
Sends rich alerts to Telegram |
Dependencies
pandas, numpy, scikit-learn, matplotlib, prophet, tqdm, requests, python-telegram-bot
License
MIT © 2025 Alexey Voronko
Metadata
Release files for anomaly-impact-alert 0.4.12
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| anomaly_impact_alert-0.4.12.tar.gz | 26.4 kB | Without provenance | Details for anomaly_impact_alert-0.4.12.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| anomaly_impact_alert-0.4.12-py3-none-any.whl | Python 3 | none | any | Details for anomaly_impact_alert-0.4.12-py3-none-any.whl |
Total release size: 58.4 kB
Release files / anomaly_impact_alert-0.4.12.tar.gz
| Download URL | anomaly_impact_alert-0.4.12.tar.gz |
|---|---|
| Size | 26.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fcb672014d3148ccaa4d7df6b1cbd8aec1bac2ab5e4b4fcc07402e2ebac88e05
|
|
BLAKE2b-256 checksum How to use checksums |
312f01b0dedfd2ddf24254e86aec4a17e003fe3be3333aa0a54df4752ff0d588
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.0
|
Release files / anomaly_impact_alert-0.4.12-py3-none-any.whl
| Download URL | anomaly_impact_alert-0.4.12-py3-none-any.whl |
|---|---|
| Size | 32.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
821171f9ad847ad45c639d9e446565f1254106d5deabe326463abef0cc5a4d70
|
|
BLAKE2b-256 checksum How to use checksums |
d9d802ea1395dba41870231eee560ecaf9c67c86feeff799b5789c6f9f2943c8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.11.0
|
Security for anomaly-impact-alert 0.4.12
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.