Skip to content

Docsp 6564 #3218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Feb 1, 2018
Merged

Docsp 6564 #3218

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
38229cf
DOCSP-6564: change reference to replica lag
skerschb Jan 26, 2018
1fc9250
DOCS-6564: simplified linking
skerschb Feb 1, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 4 additions & 7 deletions source/tutorial/troubleshoot-replica-sets.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,13 +70,10 @@ To check the current length of replication lag:
The :method:`rs.status()` method is a wrapper around the
:dbcommand:`replSetGetStatus` database command.

- Monitor the rate of replication by watching the oplog time in the
"replica" graph in the |mms-home|
and in :products:`Ops Manager, an on-premise solution
available in MongoDB Enterprise Advanced
</mongodb-enterprise-advanced?jmp=docs>`. For more information see
the |mms-docs| and :opsmgr:`Ops Manager
documentation </>`.
- Monitor the rate of replication by checking for non-zero or increasing
oplog time values in the :guilabel:`Replication Lag` graph available in
`Cloud Manager <https://docs.cloudmanager.mongodb.com/reference/alerts/replication-lag/>`_
and in `Ops Manager <https://docs.opsmanager.mongodb.com/current/reference/alerts/replication-lag/>`_.

.. include:: /includes/replacement-mms.rst

Expand Down