Description
Is your feature request related to a problem? Please describe.
Need to be able to hook into Splunk, so we can make sure the logs are coming in correctly. Right now the Splunk log parser gets confused. I would like to avoid all the headaches of adding crsalt and all that jazz by just having the information sent directly to the Splunk server using the same logger call the we use for the other logger applications.
using something like this: https://www.npmjs.com/package/splunk-logging
Describe the solution you'd like
https://www.npmjs.com/package/splunk-logging and just allow for another potential logger to be used like with pm2.
Describe alternatives you've considered
The alternative is trying to make sure splunk is reading the pm2 log output correctly and is parsing and sending the information correctly. Right now it really doesn't do that, one because of all the seperate logs and numbering, and two because the output is not always the same between outputs within the out and error logs which causes confusion with the splunk forwarder.
Additional context
We are seeing a log in xapi_stdout-4.log that was from several days ago, being displayed as if it came in today, even with the date next to it that shows it came in some other time. I believe this is because the pm2 output does not put the date next to the entry in a fashion splunk can read and causes issues.
The way around this, from what I can see, is to add a forwarder to the logging with in the app which will make sure the data comes in correct to Splunk. Which will save headaches and allow users another choice in central logging. because PM2 is not always an option, and splunk may already have been purchased for enterprise server monitoring.