A command-line and Python utility that sends multi-channel notifications for command completion, code execution, and system monitoring events.
Telert is a command-line and Python utility that sends notifications when terminal commands or Python code complete, and monitors processes, log files, and network endpoints. It solves the problem of needing to constantly watch long-running tasks or remote servers by alerting users across multiple channels like messaging apps, email, and desktop notifications.
Developers, system administrators, and DevOps engineers who run long-running commands, scripts, or need to monitor system health and receive alerts without manual oversight.
Developers choose Telert for its multi-channel support, ease of integration into existing workflows, and comprehensive monitoring capabilities—all in a single, lightweight tool that works across platforms and deployment environments.
Command‑line and Python utility that alerts on command completion, code execution and system monitoring events
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports a wide range of providers including Telegram, Slack, Email, Pushover, and desktop alerts, allowing users to choose their preferred notification method as detailed in the Notification Providers section.
Available as a CLI tool, Python library, Docker container, GitHub Action, and deployable API server, making it simple to drop into existing workflows without major changes.
Can monitor processes, log files, and network endpoints with configurable thresholds, reducing the need for separate monitoring tools, as shown in the Monitoring section with examples for each type.
Works on macOS, Linux, and Windows with platform-specific notification support, ensuring broad usability across different development environments.
Process monitoring requires psutil, which can be tricky to install on some platforms like Apple Silicon or Windows, as noted in the troubleshooting section with platform-specific workarounds.
Monitors do not automatically restart after system reboots, requiring manual intervention or additional setup with init systems like systemd, which adds complexity for production use.
Managing API keys, webhooks, and provider settings across multiple channels can become cumbersome, especially for teams needing consistent configurations across environments.
At version 0.2.7, the tool is still in beta, which might lead to breaking changes or missing features compared to mature alternatives like cron hooks or dedicated monitoring services.