Replies: 1 comment 1 reply
-
Hi @mastoj , Thank you for highlighting the need for richer log outputs in Next.js to enhance production debugging and system performance insight. Including To address this, I suggest the following steps:
Thanks . |
Beta Was this translation helpful? Give feedback.
-
Goals
Non-Goals
No response
Background
Open telemetry consists of three core pillars, metrics, logs and traces. I understand that metrics might not relevant from a nextjs perspective since that is more a core infrastructure part. When it comes to logs and traces it should be an easy way to enrich what is logged and structure for easier correlation between logs and traces. What I would expect to see in logs when I have instrumentation on is my logs to contain span_id and trace_id, which would enable a lot of the otel providers out there to correlate the logs with my traces.
Proposal
I'm not 100% sure if this is really nextjs or if it is vercel specific to be honest. I will definitely contribute verifying, if time allows I can try to help out developing.
Beta Was this translation helpful? Give feedback.
All reactions