Trace Analysis Patterns (Part 234)
When comparing traces we may be interested in their Trace Benchmarks, for example (not limited to, just a proposal):
- Performance impact (impact this trace collection has on system performance)
- Problem relevance score (was it really relevant or missed the problem repro?)
- Easy to understand (is there any room for improvement for trace messages?)
- Sensitivity (does it have any sensitive information?)
- Canonicity score (does it contain all required ATIDs?)
- Novelty score (any surprises?)
- Sufficiency (does it require supplemental log from other tools?)
- Pattern metrics (number of distinct error messages, etc., based on trace and log analysis patterns)
- Problem resolution impact (was it the trace that provided missing insights?)
This post-analysis pattern may also be useful for problem postmortems and case studies. This pattern is different from Trace Summary which is a pre-analysis information.
- Dmitry Vostokov @ DumpAnalysis.org + TraceAnalysis.org -