WardenBot
This is a goddamn bot
WHY
In Grafana, you have the option to bind an alert from your metrics data, to a Telegram Bot (see doc).
This is convenient to be alerted via instant messaging (no delay, few of configuration needed…)
HOW
Bot examples are given here.
By reading the official docs, you should have get a Bot Token. Store it in a secure way and retrieve it in your code (I personally store the bot token in an environment variable in a container)
Dont forget to install the python-telegram-bot package when copy/pasting examples :)
When the code of your bot is ready, deploy it or launch it : python your_bot.py. If dockerized, use docker run -d warden_bot.
In Telegram Messaging App, you should be able to start a new group, and to add your bot in.
The last thing you need is the Chat ID of the group you just created. To retrieve it, checkout the Telegram Api : https://api.telegram.org/bot{BOT_TOKEN}/getUpdates
In case of troubles, see this post.
Then, just put the chat ID and the bot ID in your Grafana alert handler and test it.
Metadata
Release files for WardenBot 0.62
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 |
|---|---|---|---|---|
| WardenBot-0.62.tar.gz | 3.1 kB | Without provenance | Details for WardenBot-0.62.tar.gz |
Release files / WardenBot-0.62.tar.gz
| Download URL | WardenBot-0.62.tar.gz |
|---|---|
| Size | 3.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f5672203283b918691f878835371a96de5735a644cd312803f84a795fc8bf5c7
|
|
BLAKE2b-256 checksum How to use checksums |
a654205128994bed3fcca7c7180a60d4b248d09c3aace2cd206305e71345eaa4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.33.0 CPython/3.7.4
|
Security for WardenBot 0.62
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.