[DOCS-11886] OpsManager 3.4- Multiple references to Automation Agent 2.7.0 Created: 21/Mar/17  Updated: 16/Aug/18  Resolved: 20/Jul/18

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

Type: Task Priority: Major - P3
Reporter: Charles Merrill Assignee: Anthony Sansone (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 5 years, 25 weeks, 6 days ago
Epic Link: DOCSP-1743
Story Points: 0.2

 Description   

The OpsManger documentation contains many references to "Automation Agent 2.7.0" which was only available in CloudManager.
See:
https://docs.opsmanager.mongodb.com/current/search/?query=Automation%20Agent%202.7.0

OpsManager Automation Agent went from:
Automation Agent 2.5.22.1876
Released with Ops Manager 2.0.7 on 2016-11-03
directly to:
Automation Agent 3.2.7.1927
Released with OpsManager 3.4.0 on 2016-11-29
See:
https://docs.opsmanager.mongodb.com/current/release-notes/automation-agent/

This has caused some customer confusion as Munin was used prior to Automation Agent v. 2.7.0 to gather and present hardware data for OpsManager hosts. Ops Manager monitoring of hardware via munin-node is deprecated functionality. The Automation agent now collects it's own data.
see:
https://support.mongodb.com/case/00431216



 Comments   
Comment by Githook User [ 16/Aug/18 ]

Author:

{'username': 'atsansone', 'email': 'tony.sansone@mongodb.com', 'name': 'Anthony Sansone'}

Message: (DOCS-11886): Updated to fix Munin mode issue.
Branch: v3.4
https://github.com/10gen/mms-docs/commit/dd719568394cadb8baf3b4bc8c8458b213d7f7b2

Generated at Thu Feb 08 08:03:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.