Csongor Varga | Status Logging in Node-Red: keep an eye on your system @csongorvarga | Uploaded 9 months ago | Updated 1 day ago
Recently I published a video on how to capture exceptions in Node-Red. I realized that with a little tweaking I can reuse the error logging flow to log status messages. Like when your MQTT nodes disconnects from the server.
Since I work with more and more complex logic, this would make it much easier for me to review how the code is working, if I keep my code log the most important changes in status and this flow will just log them all for me.
My example flow: https://github.com/nygma2004/km/blob/main/status_logging.json
If you like what I do here, you can support me with Youtube Thanks, or Patreon:
https://patreon.com/csongorvarga
TikTok channel most on trains, big and small: https://www.tiktok.com/@frontendfriday
And same in Instagram: https://www.instagram.com/hamptongardenrailway/
Chapters:
0:00 Intro
0:39 What is a status message
1:28 Contents
3:20 Quick Demo
6:28 Issuing status updated
7:42 Status node
9:23 Aggregate collection
11:07 Collecting all status changes
12:09 Status email
16:55 Recap
Recently I published a video on how to capture exceptions in Node-Red. I realized that with a little tweaking I can reuse the error logging flow to log status messages. Like when your MQTT nodes disconnects from the server.
Since I work with more and more complex logic, this would make it much easier for me to review how the code is working, if I keep my code log the most important changes in status and this flow will just log them all for me.
My example flow: https://github.com/nygma2004/km/blob/main/status_logging.json
If you like what I do here, you can support me with Youtube Thanks, or Patreon:
https://patreon.com/csongorvarga
TikTok channel most on trains, big and small: https://www.tiktok.com/@frontendfriday
And same in Instagram: https://www.instagram.com/hamptongardenrailway/
Chapters:
0:00 Intro
0:39 What is a status message
1:28 Contents
3:20 Quick Demo
6:28 Issuing status updated
7:42 Status node
9:23 Aggregate collection
11:07 Collecting all status changes
12:09 Status email
16:55 Recap