Epoch microseconds of this event. For example, 1502787600000000 corresponds to 2017-08-15 09:00 UTC
Usually a short tag indicating an event, like "error" While possible to add larger data, such as garbage collection details, low cardinality event names both keep the size of spans down and also are easy to search against.
Generated using TypeDoc
Associates an event that explains latency with a timestamp. Unlike log statements, annotations are often codes. Ex. "ws" for WireSend Zipkin v1 core annotations such as "cs" and "sr" have been replaced with Span.Kind, which interprets timestamp and duration.