[DOCS-9412] MongoDB data transfer 80GB for idling DB? Created: 30/Nov/16 Updated: 03/Nov/17 Resolved: 30/Nov/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jelle Herold | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | collector-298ba4e7 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.atlas.mongodb.com/billing/ |
||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 11 weeks ago | ||||
| Description |
|
Dear MongoDB, I'm evaluating (time permitting) your product for a new service at my company. Namely, 80GB of data transfer, but this instance has effectively been idle? The costs are doable, but I am wondering where that traffic comes from... Could you help me understand how I can see what caused this big amount of traffic? It wouldn't like to get too big surprises in pricing once we go to production with this and start hitting the system hard... Thanks, Happy to supply further information where needed! |
| Comments |
| Comment by Ross Cantillon (Inactive) [ 30/Nov/16 ] |
|
Closing this ticket as a duplicate of MMSSUPPORT-12528 |