Tony - I think the community would benefit from...

I think the community would benefit from an optional alarm for when node red is not running or responding. I rely on it for relays, alarms, and several other important flows for transformations, and polling other web apis. When it’s down there is no indication other than some paths are not being updated. I need a way to make a request to node red and get a response that indicates it’s running. I can’t depend on the process itself to alarm so looking for some ideas on how to do this externally. Perhaps a plugin?
6 Replies
Scott Bender
Scott Bender4w ago
Have you actually seen it down? When the rest of the server is working fine?
Tony
TonyOP4w ago
Today I experienced Signalk running but node red was not. This is from Venus OS 3.51
Scott Bender
Scott Bender4w ago
This is the node-red that runs in Signal K or the Venus Os Large node-red?
Tony
TonyOP4w ago
It’s run as a plugin in Signalk I’m thinking maybe I just need another pi to run the open telemetry stack to observe all of the systems on the network but this is a lot more work than just observing node red via Signalk
Scott Bender
Scott Bender4w ago
You need something monitoring sk then too… I just find it really odd that it stopped working In all these years, never seen that
Tony
TonyOP4w ago
Interesting that you haven’t heard of this. I am wondering if the entire stack was in some kind of stack overflow but signalk wasn’t effected quite yet. I couldn’t ssh after clicking around and ended up doing a cold reboot, which is also rare I’ll work on a separate monitoring platform since this may never be reproduced again. Thanks Scott

Did you find this page helpful?