Is your feature request related to a problem? Please describe.
When pulling logs from a container if you do a re-deploy it will pull down the full log. This is a problem for me.
The issue is that I needed the logs for a container saved to a file locally so fail2ban could parse it and do it's thing. I noticed whenever I re-deploy in Node-RED it would send the full log contents again, writing it to my file, and making fail2ban think there was a bunch of new login attempts because they are new rows.
Describe the solution you'd like
I would like to be able to pass in msg.since and if this is present on the message the node should use this instead of it's own internal since property.
Honestly though I would like to see all of the options exposed via message variables. This way I can grab all log rows between two dates for example.
Also the node outputs a debug message with how many messages it is grabbing from since which is a bit annoying. I would like a checkbox on the node called output debug info that if unchecked will not do any sort of debugging. I'm pulling logs every 2 seconds so this message spams my node-red GUI (and I know I can silence it, but the messages honestly only need to be enabled for debugging anyways).
Describe alternatives you've considered
What I did to fix this for now is just ignore the first response back from the container logs on deploy.
Is your feature request related to a problem? Please describe.
When pulling logs from a container if you do a re-deploy it will pull down the full log. This is a problem for me.
The issue is that I needed the logs for a container saved to a file locally so fail2ban could parse it and do it's thing. I noticed whenever I re-deploy in Node-RED it would send the full log contents again, writing it to my file, and making fail2ban think there was a bunch of new login attempts because they are new rows.
Describe the solution you'd like
I would like to be able to pass in
msg.sinceand if this is present on the message the node should use this instead of it's own internalsinceproperty.Honestly though I would like to see all of the options exposed via message variables. This way I can grab all log rows between two dates for example.
Also the node outputs a debug message with how many messages it is grabbing from
sincewhich is a bit annoying. I would like a checkbox on the node calledoutput debug infothat if unchecked will not do any sort of debugging. I'm pulling logs every 2 seconds so this message spams my node-red GUI (and I know I can silence it, but the messages honestly only need to be enabled for debugging anyways).Describe alternatives you've considered
What I did to fix this for now is just ignore the first response back from the container logs on deploy.