View and Download MongoDB Logs
On this page
Each mongod
, mongos
, and
mongosqld
tier keeps an account of its activity in its own log file. Atlas
retains the last 30 days of log messages and system event audit messages for each tier in a cluster. The Performance
Advisor retains at most 7 days of logs for each process in a cluster.
You must have Project Data Access Read Only
privileges
or greater to download logs.
M0
free clusters and M2/M5
shared clusters do not provide downloadable logs.
Procedure
To download the logs for a single process in a given cluster:
In the Download Logs modal, edit the following fields:
If you have not set a project time zone, the returned log data may not respect the configured date range. See Manage Project Settings.
Field | Content | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Select process | Select the process for which you want logs. Valid options are:
| ||||||||||||
Select server | Select the server in the cluster whose logs you want to retrieve. | ||||||||||||
Start Time | Specify the date and time in your group's time zone defining the
inclusive lower bound of log activity to return. The start time
must be less than 30 days ago. | ||||||||||||
End Time | Specify the date and time in your group's time zone defining the
inclusive upper bound of log activity to return. |
For information on reading MongoDB logs, refer to the Log Messages documentation in the MongoDB manual.
Database Access Logs
This feature is not available for M0
free clusters, M2
, and
M5
clusters. To learn more about which features are unavailable,
see Atlas M0 (Free Cluster), M2, and M5 Limitations.
You can view authentication attempts that were made against your cluster. Both successful and unsuccessful attempts are logged, including the timestamp of the attempt and which user tried to authenticate.