sysmonmq
Daemon that monitors status of system metrics, services and containers, and execution of local actions, via MQTT.
Features
- Send system metric, service and container status updates via MQTT.
- Trigger status checks via file (eg. syslog) or output of command (eg.
docker events). - Subscribe to MQTT topics that invoke execution of local actions via scripts or commands.
- Supports customisable sensors that runs a script or command periodically.
- Supports Home Assistant MQTT discovery auto-configuration for configured monitors.
Configuration
See the sample sysmonmq.yaml for a description of the available configuration options.
The --dump-config option will also show the full configuration with all inherited attributes.
Usage
usage: sysmonmq [-h] [-d [DEBUG]] [--dump-config] [-c CONFIG] [-v]
optional arguments:
-h, --help show this help message and exit
-d [DEBUG], --debug [DEBUG]
set debugging level
--dump-config dump full config and exit
-c CONFIG, --config CONFIG
set config file location
-v, --version show application version
Metadata
Release files for sysmonmq 0.0.1
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 |
|---|---|---|---|---|
| sysmonmq-0.0.1.tar.gz | 28.6 kB | Without provenance | Details for sysmonmq-0.0.1.tar.gz |
Release files / sysmonmq-0.0.1.tar.gz
| Download URL | sysmonmq-0.0.1.tar.gz |
|---|---|
| Size | 28.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1718e82d5e0496223420d26ddaf052f167d7881c0fcddfcc8177b0851476f7d8
|
|
BLAKE2b-256 checksum How to use checksums |
2f6291300769b6a26fe935d908150bb0d3925b39779514de19aa85fa6e8aada0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.8.6
|
Security for sysmonmq 0.0.1
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.