The objective with smokeping is to purpose an alternative to the original Smokeping but with recent technos (who still want to play with cgi bins?!) and new advanced functionalities.
The objective in this feature is to monitor the latency of many hosts across the network of workers and add the possibility to create thresholds for handling alerts, trigger actions. Because we are in the 21st century, today we want to have beautiful graphs for populate our televisions in our NOCs, so we want to design a feature that anybody can plug a Grafana or an alternative.
To help us to design the feature to the good way, we need your help for:
- what do you except with a smokeping system, what do you want to make if a metric have trigger a limit (give me your uses cases and suggestions)
- Still do you need RRD png exports? 🤔
- Is better to add one more dependency to the project by adding a new time series database like InfluxDB, using an existing Prometheus or simply use the existing PostgreSQL database and add an extension (e.g. https://github.com/timescale/timescaledb) for having a timeseries optimized engine
Thank be advance for your contribution to this thread
The objective with smokeping is to purpose an alternative to the original Smokeping but with recent technos (who still want to play with cgi bins?!) and new advanced functionalities.
The objective in this feature is to monitor the latency of many hosts across the network of workers and add the possibility to create thresholds for handling alerts, trigger actions. Because we are in the 21st century, today we want to have beautiful graphs for populate our televisions in our NOCs, so we want to design a feature that anybody can plug a Grafana or an alternative.
To help us to design the feature to the good way, we need your help for:
Thank be advance for your contribution to this thread