# Monitor Amazon Batch
<a name="logging-and-moritoring-batch"></a>

Monitoring is an important part of maintaining the reliability, availability, and performance of Amazon Batch and your Amazon solution.

We strongly encourage you to collect monitoring data from all parts of your Amazon solution to make it easier to debug a multi-point failure, if one occurs. Start by creating a monitoring plan that answers the following questions. If you're not sure how to answer these, you can still use Amazon CloudWatch Logs to establish your performance baselines.
+ What are your monitoring goals?
+ Which resources will you monitor?
+ How often will you monitor these resources?
+ Which monitoring tools will you use?
+ Who will perform the monitoring tasks?
+ Who should be notified when something goes wrong?

Your next step is to establish a baseline of normal Amazon Batch performance in your environment by measuring performance at various times and under different load conditions. As you monitor Amazon Batch, keep historical monitoring data so that you can compare it with current performance data. This will help you identify normal performance patterns and performance anomalies, and devise methods to address issues.

The topics in this section can help you start logging and monitoring Amazon Batch.

**Topics**
+ [Using CloudWatch Logs with Amazon Batch](using_cloudwatch_logs.md)
+ [Using CloudWatch Metrics with Amazon Batch](using_cloudwatch_metrics.md)
+ [Amazon Batch CloudWatch Container Insights](cloudwatch-container-insights.md)
+ [Use CloudWatch Logs to monitor Amazon Batch on Amazon EKS jobs](batch-eks-cloudwatch-logs.md)
+ [Tutorial: Collect host-level logs with Fluent Bit](batch-host-logs-fluentbit.md)
+ [Amazon Health Planned lifecycle events](batch-planned-lifecycle-events.md)