[DOCS-3945] Automation cluster configuration: monitoringVersions and backupVersions now both take a logRotate section Created: 25/Aug/14  Updated: 16/Mar/15  Resolved: 17/Sep/14

Status: Closed
Project: Documentation
Component/s: Cloud Manager
Affects Version/s: None
Fix Version/s: v1.3.11

Type: Improvement Priority: Major - P3
Reporter: Timothy Olsen (Inactive) Assignee: Bob Grabar
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 9 years, 25 weeks, 2 days ago

 Description   

In the automation agent's cluster configuration (http://mms.mongodb.com/help/reference/automation-agent/), both monitoringVersions and backupVersions both now take an optional "logRotate" key which points to an object:

"logRotate" : <obj> // spec to rotate the logs for an agent

{ "sizeThresholdMB" : <number> // (required) max size in MB for an individual log file before rotation "timeThresholdHrs" : <int> // (required) max time in hours for an individual log file before rotation "numUncompressed": <int> // (optional) max number of total log files to leave uncompressed (including current log file) // default : 5 "percentOfDiskspace" : <number> // (optional) max percent of total disk space all log files should take up before deletion // default : .02 }

 Comments   
Comment by Louisa Berger [ 25/Aug/14 ]

cc bgrabar

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