Open arggh opened 6 years ago
I would say it is intentional in the component which captures the stack traces (callsite and/or tracekit): filog does not act on the stacks itself. However, since this can lead to high data volume, you can add a processor to your logger to slice or otherwise reduce the context volume during logging.
Notice that there is ongoing work in #23 and #27 to structure the context better. The current situation, especially for combined logging chains with processors on both client and server, leads to context formats that are a bit strange.
Our main app using filog is being modified these days to have a completely custom context format using a bespoke processor on the server in order to have exactly what we want in logs, and not more, to reduce the work done to post-normalize them in Logstash: this is something you might want to consider too.
I'm wondering, is it intentional to include app source code in the log messages?