Monitor Jupyter Logs in Amazon CloudWatch Logs - Amazon SageMaker
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Monitor Jupyter Logs in Amazon CloudWatch Logs

Jupyter logs include important information such as events, metrics, and health information that provide actionable insights when running Amazon SageMaker notebooks. By importing Jupyter logs into CloudWatch Logs, customers can use CloudWatch Logs to detect anomalous behaviors, set alarms, and discover insights to keep the SageMaker notebooks running more smoothly. You can access the logs even when the Amazon EC2 instance that hosts the notebook is unresponsive, and use the logs to troubleshoot the unresponsive notebook. Sensitive information such as Amazon account IDs, secret keys, and authentication tokens in presigned URLs are removed so that customers can share logs without leaking private information.

To view Jupyter logs for a notebook instance:
  1. Sign in to the Amazon Web Services Management Console and open the SageMaker console at

  2. Choose Notebook instances.

  3. In the list of notebook instances, choose the notebook instance for which you want to view Jupyter logs by selecting the Notebook instance Name.

    This will bring you to the details page for that notebook instance.

  4. Under Monitor on the notebook instance details page, choose View logs.

  5. In the CloudWatch console, choose the log stream for your notebook instance. Its name is in the form NotebookInstanceName/jupyter.log.

For more information about monitoring CloudWatch logs for SageMaker, see Log Amazon SageMaker Events with Amazon CloudWatch.