Rally log must contain worker or iteration ID
Bug #1401843 reported by
Ilya Shakhat
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Rally |
In Progress
|
Low
|
Kiran | ||
Bug Description
Currently it's not possible to track logs for a specific iteration, since logs from different runners are mixed. It would be helpful to have iteration ID in logs.
| tags: | added: logging |
| Changed in rally: | |
| importance: | Undecided → Low |
| status: | New → Triaged |
| Changed in rally: | |
| assignee: | nobody → Kiran (rkiran) |
| status: | Triaged → In Progress |
| Changed in rally: | |
| milestone: | none → 0.1.0 |
| tags: | added: task ux |
Revision history for this message
| Bogdan Dobrelya (bogdando) wrote | #1 |
To post a comment you must log in.
Would be nice to either IDs include a timestamp or track the itaration start near to its ID as well. This is required for "visual" evaluation of such metrics as MTBF, MTTR