Observability in App Router
Unanswered
Rough harvester ant posted this in #help-forum
Rough harvester antOP
We’re in the process of moving from Pages Router to App Router. Our QA and engineers use the
When moving to App Router, I understand that we can no longer do that. What’s the state of the art for doing this kind of thing with App Router? I’m thinking one way to do this that don’t involve opening a backdoor is to store the fetch logs in something like ELK stack, and have a correlation ID to link the page request to the log. But I’m curious to hear if there’s an easier solution.
__NEXT_DATA__.props.pageProps to quickly check when things go wrong. This was an easy and valid method to debug where the fault lies, frontend or backend.When moving to App Router, I understand that we can no longer do that. What’s the state of the art for doing this kind of thing with App Router? I’m thinking one way to do this that don’t involve opening a backdoor is to store the fetch logs in something like ELK stack, and have a correlation ID to link the page request to the log. But I’m curious to hear if there’s an easier solution.