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
Currently we log some errors to the Next JS server log, but we are not logging anything in a structured way. If we want to end up in a situation where our logging is somewhat standardized and we can refer to server logs for a basic record of activity (even if New Relic provides similar information), we will need to do some research into what our options are.
Some assorted ideas to consider:
if we want to log every request / response as the API does, is there NextJS middleware we can use for this?
is there a way to control logging levels with an environment variable?
what adjustments would need to make to our existing logs to make a solution work?
is this not really a thing with Next? Do we need to adjust our thinking about server logs in this case, and can we explain the rationale for that to someone that might be expecting to be able to look at our server logs?
Acceptance criteria
document created documenting options for Next Js server logging including
recommendation for next steps
pros and cons for each option
basic usage / feature sets for each option
The text was updated successfully, but these errors were encountered:
Summary
Currently we log some errors to the Next JS server log, but we are not logging anything in a structured way. If we want to end up in a situation where our logging is somewhat standardized and we can refer to server logs for a basic record of activity (even if New Relic provides similar information), we will need to do some research into what our options are.
Some assorted ideas to consider:
Acceptance criteria
The text was updated successfully, but these errors were encountered: