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
1818As part of normal operation, MongoDB maintains a running log of events,
1919including entries such as incoming connections, commands run, and issues
2020encountered. 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`.
2231
2332Structured Logging
2433------------------
@@ -1592,3 +1601,12 @@ authorization cache.
15921601 "userCacheWaitTimeMicros": 508
15931602 },
15941603
1604+ .. _log-messages-atlas:
1605+
1606+ Download Your Logs
1607+ ------------------
1608+
1609+ You can use {+atlas+} to download a zipped file containing
1610+ the logs for a selected hostname or process in your database
1611+ deployment. To learn more, see
1612+ :atlas:`View and Download MongoDB Logs </mongodb-logs>`.
You can’t perform that action at this time.
0 commit comments