Tracing Gantt Chart

The Tracing Gantt Chart plugin provides Gantt chart visualization for distributed tracing data in Perses dashboards. This panel plugin displays trace spans in a timeline format, making it easy to visualize trace duration and dependencies.

See also technical docs related to this plugin:

Item actions#

Item actions let you trigger events or webhooks with the details of a span, for example to open the logs of a span in another plugin or application. Actions are configured in the Item Actions tab of the panel editor:

  • Enable Item Selection: adds a checkbox to each span row, and a checkbox in the table header to select all spans of the trace. The checked spans are exposed as the panel selection. The selection is cleared when another trace is loaded.
  • Display Actions with Each Item: shows the actions as buttons in the span detail pane, below the span name. These actions are executed with the span opened in the detail pane only.
  • Display Actions in Panel Header: shows the actions in the panel header. Requires Enable Item Selection: these actions are executed with the checked spans, either once per span (individual batch mode) or once for all spans (batch batch mode).

Each action receives the data of a span and its trace, as { "span": { ... }, "trace": { ... } }. Fields can be referenced in URL and body templates with ${__data.fields["<path>"]}, e.g. ${__data.fields["span.name"]}:

FieldDescription
span.traceId, span.spanId, span.parentSpanIdIdentifiers of the trace, span and parent span
span.name, span.kindSpan name and span kind
span.startTimeUnixMs, span.endTimeUnixMsStart and end time of the span, in milliseconds
span.status.code, span.status.messageSpan status
span.scope.name, span.scope.versionInstrumentation scope
span.resource.serviceNameService name
span.resource.attributes, span.attributesResource and span attributes, as OTLP key-value lists
span.events, span.linksSpan events and links, with their attributes
trace.traceId, trace.spanCountIdentifier of the trace and its number of spans
trace.startTimeUnixMs, trace.endTimeUnixMsStart and end time of the whole trace, in milliseconds

Object fields are interpolated as JSON, e.g. ${__data.fields["span.attributes"]}. Attributes are lists of OTLP key-value pairs (e.g. [{ "key": "http.method", "value": { "stringValue": "GET" } }]), so they cannot be referenced individually with a field path: use the whole list, or the full data with ${__data:json}. In batch mode, ${__data.fields["<path>"]} joins the values of all spans (CSV by default), and ${__data[<index>].fields["<path>"]} references the span at this index.

An event action dispatches a CustomEvent on window, allowing any plugin or application to handle it. Without body template, the event detail is a JSON string, which depends on the batch mode of the action:

  • individual: one event per span, with { "id": <spanId>, "data": { "span": ..., "trace": ... } }
  • batch: one event for all spans, with { "items": [{ "span": ..., "trace": ... }, ...] }

For example, a listener of an individual event action:

window.addEventListener('span-logs', (event) => {
  const { data } = JSON.parse((event as CustomEvent<string>).detail);
  openLogs({ traceId: data.span.traceId, spanId: data.span.spanId, service: data.span.resource.serviceName });
});

And a listener of a batch event action:

window.addEventListener('spans-logs', (event) => {
  const { items } = JSON.parse((event as CustomEvent<string>).detail);
  openLogs(items.map((item) => ({ traceId: item.span.traceId, spanId: item.span.spanId })));
});