Azure App Service Not Displaying Next.js Server Component Logs

Question

Azure App Service Not Displaying Next.js Server Component Logs

Joel Lozano 0

I've deployed my Next.js (Node.js + React.js) app to Azure App Service (Linux), and I noticed that console.logs aren't being displayed in the Azure Log Monitor. If an error occurs in an API route, I can see the error output in the Log Monitor, but I can't see any logs from my own code. I've been trying to set up Azure Application Insights to receive the logs to work around the issue, but I can't get that to work in the cloud, although it works in my local Windows environment (I can send logs to App Insights and view them in the portal). I'm not sure, but thinking these issues may be related.

Joel Lozano 0

I've attempted the following functions in an app/api/route.ts file, but none of the outputs are shown in Azure Log Monitor.

 	console.log('Testing console.log visibility in Log Stream');
    console.error('Testing console.error visibility in Log Stream');
    logger.info('Testing logger.info visibility in LogStream');
    logger.error('Testing logger.error visibility in log stream');
    process.stdout.write('Flushing stdout test log \n');
    process.stderr.write('Flushing stderr test log\n');

Joel Lozano 0 Reputation points

2024-12-19T05:24:34.5966667+00:00

I'm using the setup from this StackOverflow post: https://stackoverflow.com/questions/79022009/how-to-send-logs-from-nextjs-to-azure-application-insights-using-opentelemetry-a

1 answer

Your answer

Joel Lozano 0 Reputation points

2024-12-18T23:09:49.9366667+00:00

I've attempted the following functions in an app/api/route.ts file, but none of the outputs are shown in Azure Log Monitor.

console.log('Testing console.log visibility in Log Stream'); console.error('Testing console.error visibility in Log Stream'); logger.info('Testing logger.info visibility in LogStream'); logger.error('Testing logger.error visibility in log stream'); process.stdout.write('Flushing stdout test log \n'); process.stderr.write('Flushing stderr test log\n');
Joel Lozano 0 Reputation points

2024-12-19T05:24:34.5966667+00:00

I'm using the setup from this StackOverflow post: https://stackoverflow.com/questions/79022009/how-to-send-logs-from-nextjs-to-azure-application-insights-using-opentelemetry-a

Answer 1

@Joel Lozano ensure that Application Logging (Filesystem) is enabled in the Azure Portal under your App Service's Diagnostics settings, and verify that the Log Level is set to the appropriate level (e.g., Information or Verbose). Use the Log Stream feature in the Azure Portal to view real-time logs, and check the LogFiles directory in your App Service's file system via the Kudu Console for any logs under /home/LogFiles. For Application Insights, double-check the instrumentation key and configurations in your next.config.js or environment variables, and ensure the SDK is initialized correctly in your application code. Sometimes, logs might not appear due to buffering issues, so try flushing the logs explicitly in your code. Finally, restart your App Service and redeploy your application to ensure all configurations are applied correctly.

Share via

Azure App Service Not Displaying Next.js Server Component Logs

1 answer

Your answer