[DOCS-11818] Ops Manager sizing estimates need to be updated for 10 second resolution, performance advisor, hardware metrics, and flexible retention Created: 19/Jun/18  Updated: 27/Oct/23  Resolved: 02/Jul/18

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

Type: Task Priority: Major - P3
Reporter: Brian Blevins Assignee: Anthony Sansone (Inactive)
Resolution: Gone away Votes: 0
Labels: Sizing
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.opsmanager.mongodb.com/current/core/requirements/#hardware-requirements


Issue Links:
Depends
Duplicate
Related
is related to DOCS-11428 AppDB sizing needs to take into accou... Closed
Participants:
Days since reply: 5 years, 32 weeks, 2 days ago
Story Points: 0.1

 Description   

----------------------------

Original Description

https://docs.opsmanager.mongodb.com/current/core/requirements/#hardware-requirements

Ops Manager user feedback on 3.4.4 indicates that monitoring 2000 hosts/instances on a single application server with 8CPUs and 32GB of RAM is not realistic.

----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



 Comments   
Comment by Ravind Kumar (Inactive) [ 02/Jul/18 ]

We will re-generate this ticket via ETM when the cloud ticket closes.

Comment by Anthony Sansone (Inactive) [ 20/Jun/18 ]

Additional monitoring capabilities were introduced in v3.6. The documentation will not be updated until additional performance data has been collected and analyzed so the best possible information can be provided to customers.

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