[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 |
||
| Issue Links: |
|
||||||||
| 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. |
| Comments |
| Comment by Githook User [ 24/Dec/13 ] |
|
Author: {u'name': u'Tim Slavin', u'email': u'TimSlavin@MongoDBs-MacBook-Pro-2.local'}Message: |
| Comment by Githook User [ 24/Dec/13 ] |
|
Author: {u'name': u'Tim Slavin', u'email': u'TimSlavin@MongoDBs-MacBook-Pro-2.local'}Message: |
| Comment by Githook User [ 24/Dec/13 ] |
|
Author: {u'name': u'Tim Slavin', u'email': u'TimSlavin@MongoDBs-MacBook-Pro-2.local'}Message: |
| Comment by Githook User [ 24/Dec/13 ] |
|
Author: {u'name': u'Tim Slavin', u'email': u'TimSlavin@MongoDBs-MacBook-Pro.local'}Message: |
| 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. |