Skip to content

Commit 16c0920

Browse files
committed
Fix broken links
1 parent 427ab41 commit 16c0920

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/integrations/databases/mongodb-atlas.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -273,10 +273,10 @@ This section demonstrates how to add a hosted Sumo Logic collector and HTTP Logs
273273
### Step 3: Configure Collection for MongoDB Atlas
274274

275275
In this section, we explore various mechanisms to collect database logs, events, metrics and alerts from MongoDB Atlas and send them to Sumo Logic, where they are shown in dashboards as part of the MongoDB Atlas app. You can configure Sumo Logic’s MongoDB Atlas collector in Amazon Web Services (AWS) using the AWS Lambda service, or by running a script on a Linux machine as a cron job. Choose the method that is best suited for you:
276-
* [AWS Lambda-based collection](#step-3a-deploy-the-sumo-logic-mongodb-atlas-sam-application) via a Serverless Application Model (SAM) application
277-
* [Script-based collection](#step-3c-configure-script-based-collection-for-mongodb-atlas) from a Linux machine
276+
* [AWS Lambda-based collection](#deploy-the-sumo-logic-mongodb-atlas-sam-application) via a Serverless Application Model (SAM) application
277+
* [Script-based collection](#configure-script-based-collection-for-mongodb-atlas) from a Linux machine
278278

279-
A single instance of the collector is responsible for collecting logs from a single project. Refer to [Configure Collection for Multiple Projects](#step-3b-configure-collection-for-multiple-projects-optional) if you have multiple projects.
279+
A single instance of the collector is responsible for collecting logs from a single project. If you have multiple projects, refer to the additional steps in these sections.
280280

281281

282282
#### Deploy the Sumo Logic MongoDB Atlas SAM application

0 commit comments

Comments
 (0)