Is your feature request related to a problem? Please describe.
Hi,
I don't know if it is "easy / possible", but as pulseV6 is more generic/flexible ....
Could it be possible to define a generic sensor at the client side ( AKA pulse agent) to report some numeric value and to the server side ( Pulse serve) ?
It could be usefull to report
- global DB status ( postgre or sqlite...)
- pending system updates ( apt)
- In fact, anything that could be performed and reported using a bash script...
Describe the solution you'd like
The global idea would be something like:
A "yaml?" at the Pulse Agent side describing:
- Sensor name reported to pulse server ( eg "Pending APT actions" )
- Local shell script path to be executed ( eg: "/get_pending_apt_actions.sh"). This script should return a integer/float. Anything else is assumed to be an error / message. ( We could report a JSON if it's more convenient)
- sensor refresh interval ( eg: 600s)
- warning treshold ( eg: 5 )
- error / critical treshold ( eg: 20 )
That way we could report anything that can be retreived by the OS to the "Pulse server": multiple fan speeds, gpu(s) info, "/var/log" disk usage, ping averages, DB info, apt, anything ....
=> The sky is the limit.
=> Up to the user to create/test/search/validate...
=> If user want to share, of it it has to be integrated as a "standard pulse sensor", at least you don't start with nothing ;-)
It could be a win-win approach to strange/exotic requirements :-)
Thanks already for the fantactic job you've done!
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Is your feature request related to a problem? Please describe.
Hi,
I don't know if it is "easy / possible", but as pulseV6 is more generic/flexible ....
Could it be possible to define a generic sensor at the client side ( AKA pulse agent) to report some numeric value and to the server side ( Pulse serve) ?
It could be usefull to report
Describe the solution you'd like
The global idea would be something like:
A "yaml?" at the Pulse Agent side describing:
That way we could report anything that can be retreived by the OS to the "Pulse server": multiple fan speeds, gpu(s) info, "/var/log" disk usage, ping averages, DB info, apt, anything ....
=> The sky is the limit.
=> Up to the user to create/test/search/validate...
=> If user want to share, of it it has to be integrated as a "standard pulse sensor", at least you don't start with nothing ;-)
It could be a win-win approach to strange/exotic requirements :-)
Thanks already for the fantactic job you've done!
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.