[DOCS-8639] Add "Does MongoDB Atlas expose the oplog?" to FAQ Created: 22/Aug/16  Updated: 24/Aug/16  Resolved: 23/Aug/16

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Andrew Davidson Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: https://docs.atlas.mongodb.com/faq/
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.84 Safari/537.36
Referrer: https://docs.atlas.mongodb.com/
Screen Resolution: 1920 x 1080


Issue Links:
Related
Participants:
Days since reply: 7 years, 25 weeks, 2 days ago
Story Points: 0.25

 Description   

The answer is "Yes". This is a common requirement for Meteor users (Meteor 1.4 introduced support for MongoDB 3.2 and hence MongoDB Atlas).

In order to access the oplog, a database user must have read access on the "local" database.

To create a user with the necessary read privileges for the local database, add a new user in the Security tab called, for example, "oploguser". Then restrict the privileges further by selecting the "Show Advanced Options" menu and choosing read@local in the associated role. This will restrict the user "oploguser" to perform read operations on the local database, only.


Generated at Thu Feb 08 07:56:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.