You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the metric.1 log type in WGS does not support the inclusion of "Samples" (also known as exemplars) in histogram and timer measurements. This limits the ability to directly correlate metric spikes with specific trace data, making it difficult to debug and understand the root cause of issues observed in metrics.
What did you want to happen?
Add support for "Samples" (exemplars) to the metric.1 log type, specifically for histogram and timer measurements. These samples should include the last exact measurement values along with a traceId that links to the corresponding parent trace. This will enable users to quickly find and examine sampled traces when looking at metrics, especially useful for analyzing latency and investigating slow requests.
Background
Exemplars allow you to quickly find sampled traces when looking at metrics, providing valuable context for understanding metric spikes. They are particularly useful when investigating latency issues, as they help correlate specific high-latency requests with trace data.
A raw metric generally represents a statistical aggregation of numerous values with the same labels over a scraping interval (30s in our case). In contrast, an exemplar is a single exact measurement of that value, along with its actual timestamp. By selecting a sampled measurement with span information available, users can easily look up the trace in the trace viewer.
Proposed Changes
Extend the metric.1 log type to include a samples field for histogram measurements.
Define the samples field as a list of Sample objects.
Each Sample object should include:
value: The exact value of the sample.
time: The RFC3339Nano UTC datetime string of when the sample was taken.
traceId: The optional Zipkin trace id associated with this sample, if available.
What happened?
Currently, the
metric.1
log type in WGS does not support the inclusion of "Samples" (also known as exemplars) in histogram and timer measurements. This limits the ability to directly correlate metric spikes with specific trace data, making it difficult to debug and understand the root cause of issues observed in metrics.What did you want to happen?
Add support for "Samples" (exemplars) to the
metric.1
log type, specifically for histogram and timer measurements. These samples should include the last exact measurement values along with atraceId
that links to the corresponding parent trace. This will enable users to quickly find and examine sampled traces when looking at metrics, especially useful for analyzing latency and investigating slow requests.Background
Exemplars allow you to quickly find sampled traces when looking at metrics, providing valuable context for understanding metric spikes. They are particularly useful when investigating latency issues, as they help correlate specific high-latency requests with trace data.
A raw metric generally represents a statistical aggregation of numerous values with the same labels over a scraping interval (30s in our case). In contrast, an exemplar is a single exact measurement of that value, along with its actual timestamp. By selecting a sampled measurement with span information available, users can easily look up the trace in the trace viewer.
Proposed Changes
metric.1
log type to include asamples
field for histogram measurements.samples
field as a list ofSample
objects.Sample
object should include:value
: The exact value of the sample.time
: The RFC3339Nano UTC datetime string of when the sample was taken.traceId
: The optional Zipkin trace id associated with this sample, if available.Example Exemplar
The text was updated successfully, but these errors were encountered: