[DOCS-2398] Improve FAQ for Monitoring Agent Robustness Created: 11/Dec/13  Updated: 03/Nov/17  Resolved: 24/Dec/13

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Charlie Page Assignee: Tim Slavin
Resolution: Done Votes: 0
Labels: collector-298ba4e7
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Location: http://mms.mongodb.com/help/monitoring/faq/#should-i-run-more-than-one-agent
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:25.0) Gecko/20100101 Firefox/25.0
Screen Resolution: 1440 x 900
repo: REPONAME
source: monitoring/faq


Issue Links:
Related
is related to DOCS-3149 Continue to improve one-agent-is-suff... Closed
Participants:
Days since reply: 10 years, 8 weeks, 1 day ago

 Description   

Mongo: "The Monitoring agent is fairly robust, and MMS automatically sends an Agent Down alert when a Monitoring agent becomes unavailable. For most applications, a single Monitoring agent is sufficient. However, you can choose to run a second agent to provide redundancy. Larger numbers of agents do not provide significant benefit. See: Monitoring Architecture for information."

So we had these guys running a single agent that went down during Black Friday and their system went sideways. We had no time series data view into why their system failed.
We can recommend agent, you might be able to do it, but we need to recommend two. Even if the agent is perfect, machines fail, and usually under heavy load when you can least afford to miss monitoring stats.



 Comments   
Comment by Githook User [ 24/Dec/13 ]

Author:

{u'name': u'Tim Slavin', u'email': u'TimSlavin@MongoDBs-MacBook-Pro-2.local'}

Message: DOCS-2398 multiple agents Edit 4
Branch: master
https://github.com/10gen/mms-docs/commit/d6fbb3294d0b6fb51b928617eaaf55afb9a964ba

Comment by Githook User [ 24/Dec/13 ]

Author:

{u'name': u'Tim Slavin', u'email': u'TimSlavin@MongoDBs-MacBook-Pro-2.local'}

Message: DOCS-2398 multiple agents Edit 3
Branch: master
https://github.com/10gen/mms-docs/commit/fd8e6e8a2ace5813b9ef362b9f6c6186659ed815

Comment by Githook User [ 24/Dec/13 ]

Author:

{u'name': u'Tim Slavin', u'email': u'TimSlavin@MongoDBs-MacBook-Pro-2.local'}

Message: DOCS-2398 Multiple Agents Edit 2
Branch: master
https://github.com/10gen/mms-docs/commit/06eb261da53d81260c235e93a2158142469689f9

Comment by Githook User [ 24/Dec/13 ]

Author:

{u'name': u'Tim Slavin', u'email': u'TimSlavin@MongoDBs-MacBook-Pro.local'}

Message: DOCS-2398 multiple agents Edit 1
Branch: master
https://github.com/10gen/mms-docs/commit/cd98ad8e0d9e37b25fca0c4c6bdba40cba05bcd0

Comment by Angshuman Bagchi (Inactive) [ 11/Dec/13 ]

Perhaps a recommendation along the following lines:

Start out with a single Monitoring agent as it is easier to debug host discoverability/connectivity issues with just one agent. Once the cluster is all set up and being monitored correctly on MMS, consider adding a second Agent to provide redundancy. That way, if one agent fails the other can pick up and there is no break in monitoring. However, the second agent has the same connectivity requirements as the first. So in order to have a seamless transition from one agent to the next, the second agent also needs to be to connect to all monitored hosts.

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