Filter error traces in OSprofiler to separated place
Registered by
Tovin Seven
Filter and classify error traces in OSprofiler to separated place.
For example, with redis driver, we can store all error traces in other db (db 0 for normal traces, db 1 for error traces).
This ability can be configured.
Some work items:
- Construct list of error status code/exception
- Add tags to span context. Pack/unpack data
- Method to move all related spans to separated place
- CLI option to retrieve all error traces
- Add configurations for choosing backend/how to store error traces
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Tovin Seven
- Direction:
- Needs approval
- Assignee:
- Tovin Seven
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
[WiP] Filter traces that contain error/exception
(?)
