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
Trace analytics considered using SQL/PPL for its queries, but some graphs rely on joining two indices (span index and service map index) together which is not supported by SQL/PPL. Trace analytics was implemented with DSL + javascript, would be good if join being added to SQL could support this use case.
Schema
There will be at least 2 indices, otel-v1-apm-span-* (large) and otel-v1-apm-service-map (small).
Relevant fields from indices:
otel-v1-apm-span-*:
traceId - A unique identifier for a trace. All spans from the same trace share the same traceId.
spanId - A unique identifier for a span within a trace, assigned when the span is created.
parentSpanId - The spanId of this span's parent span. If this is a root span, then this field must be empty.
durationInNanos - Difference in nanoseconds between startTime and endTime. (this is latency in UI)
serviceName - The resource from the span originates.
traceGroup - The name of the trace's root span.
otel-v1-apm-service-map:
serviceName - The name of the service which emitted the span.
destination.domain - The serviceName of the service being called by this client.
destination.resource - The span name (API, operation, etc.) being called by this client.
target.domain - The serviceName of the service being called by a client.
target.resource - The span name (API, operation, etc.) being called by a client.
traceGroupName - The top-level span name which started the request chain.
For each service, join span index on service map index to calculate metrics under different type of filters.
This sample query calculates latency when filtered by trace group client_cancel_order for the order service. I only have a subquery example, don't have the join version of the query..
Trace analytics considered using SQL/PPL for its queries, but some graphs rely on joining two indices (span index and service map index) together which is not supported by SQL/PPL. Trace analytics was implemented with DSL + javascript, would be good if
join
being added to SQL could support this use case.Schema
There will be at least 2 indices,
otel-v1-apm-span-*
(large) andotel-v1-apm-service-map
(small).Relevant fields from indices:
otel-v1-apm-span-*
:latency
in UI)otel-v1-apm-service-map
:Full schemas are defined in data-prepper repo:
otel-v1-apm-span-*
,otel-v1-apm-service-map
Sample documents
Run the following commands to dump sample documents for the two indices to localhost:9200:
Requirement
Support
join
to calculate the following:For each service, join span index on service map index to calculate metrics under different type of filters.
This sample query calculates latency when filtered by trace group
client_cancel_order
for theorder
service. I only have a subquery example, don't have the join version of the query..The text was updated successfully, but these errors were encountered: