Logging about http-event-collector HOT 4 CLOSED

I just noticed that my node-red-out.log was 27G because of the logging. It would be great if this did not log anything and had an output for success and failure, in that way something could be logged to Splunk and then continue in the flow which could be to log the output or fail and another action could be taken. Another feature that caused me to use my own http request node to log to Splunk is I want to remove the additional message structure so just the raw payload data is logged and able to be referenced by name without the additional cumbersome and uneeded message.payload json references in Splunk. So the option would be to log the payload only as-is to the index.

from http-event-collector.

I have a fork where I have fixed both of these things, I've added a config node where you can set the default log level among other things, but then also adjust it via the msg object (msg.LogLevel) if you need to do something special.

I've also added a checkbox for console logging on/off. I haven't added a pull request here because there is one sitting from a few years back, but also because I removed the metrics part of it as I don't require it.

from http-event-collector.

@rXc3NtR1c

Sorry, I have been inactive on here. I am going to be more active now. Feel free to make a pull request.

from http-event-collector.

Node has been updated

from http-event-collector.