Replies: 5 comments
-
I've taken a few first tiny steps towards implementing this feature. I'm thinking we should have the ability to run both local and remote scripts, so I've currently set up the config file as such:
In terms of return signal, why not implement something a little more expressive such as a JSON string?
Chiadog would then take that event, slap a priority icon on it, append the monitor's Should each of these custom monitors live in its own separate thread? |
Beta Was this translation helpful? Give feedback.
-
Yes, definitely returning some JSON (e.g. by printing it to stdout) would be much better. I just suggested the simplest thing to not make the feature unnecessarily big - but it makes perfect sense to do more than just green/red result. In my situation those scripts would be really short lived (read temp from |
Beta Was this translation helpful? Give feedback.
-
Just a quick note: Careful not to over-design the tool. At some point it might make sense to have two separate tools running side-by-side, each doing their little task. Makes maintenance easier! |
Beta Was this translation helpful? Give feedback.
-
Could we provide a one-time |
Beta Was this translation helpful? Give feedback.
-
@greimela I think that's the way to go if there is value in easily reusing the notification channels 👍 |
Beta Was this translation helpful? Give feedback.
-
E.g. I would wish to be able to define a number of scripts, each returning
0
or non-0
process exit code, so Chiadog could run them occasionally and send notification when non-zero return code is seen.Examples usage would be checking whether temperature is above threshold or disk space is below threshold etc. - in a pluginable way.
Alternatively, Chiadog could check the 2 conditions mentioned above, but over the time I would end up with much more checks.
Beta Was this translation helpful? Give feedback.
All reactions