File tree Expand file tree Collapse file tree 1 file changed +19
-1
lines changed Expand file tree Collapse file tree 1 file changed +19
-1
lines changed Original file line number Diff line number Diff line change @@ -18,7 +18,16 @@ Overview
18
18
As part of normal operation, MongoDB maintains a running log of events,
19
19
including entries such as incoming connections, commands run, and issues
20
20
encountered. Generally, log messages are useful for diagnosing issues,
21
- monitoring your deployment, and tuning performance.
21
+ monitoring your deployment, and tuning performance.
22
+
23
+ To get your log messages, you can use any of the
24
+ following methods:
25
+
26
+ - View logs in your configured :ref:`log destination
27
+ <log-message-destinations>`.
28
+ - Run the :dbcommand:`getLog` command.
29
+ - Download logs through :atlas:`{+atlas+} </>`.
30
+ To learn more, see :ref:`log-messages-atlas`.
22
31
23
32
Structured Logging
24
33
------------------
@@ -1470,3 +1479,12 @@ authorization cache.
1470
1479
"userCacheWaitTimeMicros": 508
1471
1480
},
1472
1481
1482
+ .. _log-messages-atlas:
1483
+
1484
+ Download Your Logs
1485
+ ------------------
1486
+
1487
+ You can use {+atlas+} to download a zipped file containing
1488
+ the logs for a selected hostname or process in your database
1489
+ deployment. To learn more, see
1490
+ :atlas:`View and Download MongoDB Logs </mongodb-logs>`.
You can’t perform that action at this time.
0 commit comments