Datadog Monitor Deployer
versions
health
stats
A powerful and flexible tool for managing Datadog monitors as code. This project enables teams to define, deploy, and manage Datadog monitors using a declarative approach, supporting both YAML/JSON configurations and Python classes.
🌟 Key Features
- 📝 Multiple Definition Formats:
- YAML/JSON with schema validation
- Python classes for programmatic creation
- Hybrid approach supporting both methods
- 🔍 Comprehensive Monitor Type Support:
- Metric monitors
- Event monitors
- Log monitors
- APM monitors
- Network monitors
- Process monitors
- ⚡ Advanced Functionality:
- Robust alerting configuration
- Multiple notification channels (Email, Slack, PagerDuty)
- Custom message templates
- Tagging and organization
- Full CRUD operations
- 🛡️ Enterprise-Ready:
- Idempotent operations
- Comprehensive testing
- Secure authentication handling
- CI/CD pipeline integration
🚀 Quick Start
- Install the package:
pip install datadog-monitor-deployer
- Set up your Datadog credentials:
export DD_API_KEY="your-api-key"
export DD_APP_KEY="your-app-key"
- Create a monitor definition (example.yaml):
monitors:
- name: "High CPU Usage Alert"
type: "metric alert"
query: "avg(last_5m):avg:system.cpu.user{*} > 80"
message: "CPU usage is above 80%"
tags:
- "env:production"
- "service:web"
options:
notify_no_data: true
evaluation_delay: 900
- Deploy your monitor:
dd-monitor deploy example.yaml
📚 Documentation
For detailed documentation, visit our Documentation Site.
🛠️ Development Setup
- Clone the repository:
git clone https://github.com/fleXRPL/datadog-monitor-deployer.git
cd datadog-monitor-deployer
- Create and activate a virtual environment:
python -m venv venv
source venv/bin/activate # On Windows: .\venv\Scripts\activate
- Install development dependencies:
pip install -r requirements-dev.txt
- Run tests:
pytest
🤝 Contributing
We welcome contributions! Please see our Contributing Guide for details.
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
🔒 Security
Please review our Security Policy for reporting security vulnerabilities.
📊 Project Status
This project is actively maintained and used in production environments. For the latest updates, see our Changelog.
Built with ❤️ by the fleXRPL team
Release files for datadog-monitor-deployer 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| datadog_monitor_deployer-0.1.0.tar.gz | 15.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| datadog_monitor_deployer-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 26.3 kB
Release files / datadog_monitor_deployer-0.1.0.tar.gz
| Download URL | datadog_monitor_deployer-0.1.0.tar.gz |
|---|---|
| Size | 15.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94a45fb6775c9859c1c8cb5f16a8430a1b975e16398f6bbef6c5cd5194651694
|
|
BLAKE2b-256 checksum How to use checksums |
4be3bf4b8f216cf02e06e8ab059d5f50c3205fa1825f7035ca1551fcbe0c91e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 17, 2025.
Transparency logRelease files / datadog_monitor_deployer-0.1.0-py3-none-any.whl
| Download URL | datadog_monitor_deployer-0.1.0-py3-none-any.whl |
|---|---|
| Size | 10.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c48a642df0019759e088e2a9a59260bb1311d10619f3d55c25dfbbe4901bb792
|
|
BLAKE2b-256 checksum How to use checksums |
0fdfe56469a8d8e74c59d0d30e0fb28582936ec61471aff97d5267b1624fbe14
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.8
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 17, 2025.
Transparency log