[SERVER-22376] Capture ftdc files from tests Created: 25/Nov/15 Updated: 29/Jan/16 Resolved: 29/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | DO NOT USE - Backlog - Test Infrastructure Group (TIG) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
Along with the logs we should collect the ftdc files which include stats from the running instances. |
| Comments |
| Comment by Kamran K. [ 29/Jan/16 ] |
|
Dupe of |
| Comment by Michael O'Brien [ 29/Jan/16 ] |
|
Moved to server, this should be doable with updates within the server's etc/evergreen.yml |
| Comment by Scott Hernandez (Inactive) [ 11/Dec/15 ] |
|
Sure, where ever it can be worked on is good. |
| Comment by Michael O'Brien [ 10/Dec/15 ] |
|
I think this would be implemented by additions to the server config file to run ftdc and attach them to the task after the test is over using s3.put, the same way we do with minidump/core files. Should we move this ticket to SERVER for now? scotthernandez |