[SERVER-30823] Allow FTDC output directory to be configured Created: 24/Aug/17 Updated: 08/Sep/20 Resolved: 08/Sep/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Joe Caswell | Assignee: | Mark Benvenuto |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | move-sec | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Sprint: | Security 2020-09-21 | ||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
Currently FTDC output is hardcoded to dbpath/diagnostic.data. Allowing this location to be configurable would simplify excluding diagnostic data from database backups. |
| Comments |
| Comment by Joe Caswell [ 13/Sep/17 ] |
|
This request was originally from customer who was having trouble with backups failing due to hash mismatch. Worked with them to switch to use gnu tar for the backup, which does provide pattern based exclusion, so this is no longer an issue for them. |