Spans are represented using Async Event types of chrome trace viewer.
According to the doc, the 'id' should be unique within category, scope.
https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview#heading=h.jh64i9l3vwa1
Use the index in the task's span slice as the slice id, so it
can be unique within the task. The scope is the task id which
is unique.
This fixes a visualization bug that caused incorrect or missing
presentation of nested spans.
Change-Id: If1537ee00247f71fa967abfe45569a9e7dbcdce7
Reviewed-on: https://go-review.googlesource.com/102697
Reviewed-by: Heschi Kreinick <heschi@google.com>
ctx.emit(tEnd)
// Spans
- for _, s := range task.spans {
- ctx.emitSpan(s)
+ for i, s := range task.spans {
+ ctx.emitSpan(s, i)
}
}
}
return sl
}
-func (ctx *traceContext) emitSpan(s spanDesc) {
+func (ctx *traceContext) emitSpan(s spanDesc, spanID int) {
if s.Name == "" {
return
}
Phase: "b",
Time: float64(s.firstTimestamp()) / 1e3,
Tid: s.G,
- ID: s.G,
+ ID: uint64(spanID),
Scope: scopeID,
Cname: colorDeepMagenta,
}
Phase: "e",
Time: float64(s.lastTimestamp()) / 1e3,
Tid: s.G,
- ID: s.G,
+ ID: uint64(spanID),
Scope: scopeID,
Cname: colorDeepMagenta,
}