> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Monitor Your Clusters

**Note:**

This page applies to both Atlas Infinite and Atlas Core.

Atlas provides built-in tools, alerts, charts, integrations, and logs to help you monitor your clusters. Atlas provides the following ways to monitor your clusters and improve performance.

To learn about recommendations for monitoring and alerts, including important metrics to monitor and recommended alert configurations, see [Recommendations for Atlas Monitoring and Alerts](https://www.mongodb.com/docs/atlas/architecture/current/monitoring-alerts.md#std-label-arch-center-monitoring-alerts-recs) in the Atlas Architecture Center.

## Slow Queries

To optimize your query performance, [review the best practices for query performance](https://www.mongodb.com/docs/atlas/analyze-slow-queries.md#std-label-query-best-practices). You can also [analyze slow queries](https://www.mongodb.com/docs/atlas/analyze-slow-queries.md#std-label-analyze-slow-queries) and troubleshoot slow operations executed on your clusters.

Use the following built-in tools:

- [Monitor and improve slow queries](https://www.mongodb.com/docs/atlas/performance-advisor.md#std-label-performance-advisor) with the Performance Advisor.

- [Monitor collection-level query latency](https://www.mongodb.com/docs/atlas/namespace-insights.md#std-label-namespace-insights) with Namespace Insights.

- [Monitor query performance](https://www.mongodb.com/docs/atlas/tutorial/query-profiler.md#std-label-profile-database) with the Query Profiler.

- [Monitor real-time performance](https://www.mongodb.com/docs/atlas/real-time-performance-panel.md#std-label-real-time-metrics-status-tab) with the Real-Time Performance Panel.

## Schema Design

To optimize your schema design, review our frequently used [schema design patterns](https://www.mongodb.com/docs/manual/data-modeling/schema-design-patterns/). You can also improve your schema based on recommendations from the [Performance Advisor](https://www.mongodb.com/docs/atlas/performance-advisor.md#std-label-performance-advisor) and the [Atlas UI](https://www.mongodb.com/docs/atlas/atlas-ui/databases.md#std-label-atlas-ui-dbs). For more information, see [Schema Design Anti-Patterns.](https://www.mongodb.com/docs/manual/data-modeling/design-antipatterns/)

## Alerts

To trigger alerts based on [alert conditions](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions) and to help ensure cluster performance, [configure alerts and resolve them promptly](https://www.mongodb.com/docs/atlas/alerts.md#std-label-alerts). You can configure alerts based on specific conditions for your databases, users, accounts, and more. When you resolve alerts, you should fix the immediate problem, implement a long-term solution, and monitor your progress.

Before you get started with alerts, review the [Alert Basics.](https://www.mongodb.com/docs/atlas/alert-basics.md#std-label-alert-basics)

## Deployment Metrics

To monitor your cluster performance, [view cluster metrics](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics). View historical throughput, performance, and usage metrics for your databases. To learn more, [review the available metrics.](https://www.mongodb.com/docs/atlas/review-available-metrics.md#std-label-review-available-metrics)

## Third-Party Integrations

To receive Atlas alerts in various external monitoring services, [integrate with third-party monitoring services.](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations)

## MongoDB Logs

Atlas provides several methods for accessing your [log messages](https://www.mongodb.com/docs/manual/reference/log-messages/) and [system event audit messages.](https://www.mongodb.com/docs/manual/reference/audit-message/)

- [View and download your MongoDB logs](https://www.mongodb.com/docs/atlas/mongodb-logs.md#std-label-mongodb-logs) directly from the Atlas UI, API, or CLI for manual inspection and troubleshooting.

- [Export logs in near real-time](https://www.mongodb.com/docs/atlas/export-logs-external-sinks.md#std-label-export-logs-external-sinks) to AWS (Amazon Web Services) S3 (Simple Storage Service) buckets.

- Use the Atlas Administration API to [pull log data](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/group/endpoint-monitoring-and-logs) every 5 minutes or [pull monitoring data.](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/group/endpoint-monitoring-and-logs)

**Note:**

Atlas continues to support the following legacy methods for log and metric integration:

- Use the legacy [push-based log export](https://www.mongodb.com/docs/atlas/push-logs.md#std-label-mongodb-logs-push) feature to send logs to an AWS (Amazon Web Services) S3 (Simple Storage Service) bucket. For new S3 (Simple Storage Service) integrations, we recommend using [the Atlas export feature](https://www.mongodb.com/docs/atlas/export-logs-external-sinks.md#std-label-export-logs-external-sinks) instead.

- Configure push-based [monitoring integrations](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) for Atlas with Datadog to send metrics.

- Configure pull-based logging integrations with jSonar (which can push to other services like Splunk) and SumoLogic.