You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! We're trying to leverage pino logger at a large enterprise with a very specific logging JSON format that needs to be sent to STDOUT and STDERR in order to be scraped by our PaaS system and processed by the ELK stack.
Looking through the docs, I see that you can use formatters to transform individual pieces of the logs. However, in our case, this would not be sufficient. Is there anything in the library outside of a custom transport that will allow us to transform the entire log message at once?
Here's a rough example of how our log message format needs to look:
{"applog": {// <- Our logs need to be nested under a specific root key"log_level": ...,"context": "...","http_request": {
...
},
...
}}
Any help would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered:
Hi! We're trying to leverage pino logger at a large enterprise with a very specific logging JSON format that needs to be sent to STDOUT and STDERR in order to be scraped by our PaaS system and processed by the ELK stack.
Looking through the docs, I see that you can use formatters to transform individual pieces of the logs. However, in our case, this would not be sufficient. Is there anything in the library outside of a custom transport that will allow us to transform the entire log message at once?
Here's a rough example of how our log message format needs to look:
Any help would be appreciated. Thanks!
The text was updated successfully, but these errors were encountered: