Skip to content
Menu
DocumentationExplore traces
On this page
Observability

Explore traces

Open Traces after your application has exported spans. JavaScript must be enabled. Use these controls to find an operation:

  • Time range: last 15 minutes, last hour (the default), or last 24 hours.
  • Search traces: case-insensitive text in operation, service, or package names, or a complete 32-character hexadecimal trace ID. This is a text search, not a LogQL or TraceQL editor; arbitrary attributes are not searched here.
  • Package / Service: narrow the result to an instrumented package or service name. Choices come from received trace data in the selected time range.
  • Status: Error finds traces containing an error span. OK means no error span was reported; it does not prove the HTTP response succeeded. Set span status in your instrumentation.
  • Min. duration: enter milliseconds, such as 500, to find traces lasting at least half a second.

Filters update the results automatically. Select Refresh to fetch again, or Clear filters to start over. Auto-refresh runs every two seconds while you are viewing the latest results; it pauses while the tab is hidden, you select text, read older rows, or inspect a trace. Uncheck Auto-refresh to keep results steady.

For a slow-request investigation, choose a package, set Min. duration to 500, and choose Longest duration under Sort by. To investigate failures, clear the duration threshold and choose Error. Searches return at most 100 traces. Sorting, the duration chart, error rate, median, and p95 describe the returned results, not all workspace traffic. Narrow the time range or filters when the limit notice appears.

Inspect a trace

Select an operation in the table or a point on the duration chart. The detail dialog shows the full trace ID, total duration, services, and a span waterfall. Bars show span start offsets and durations relative to the trace’s start. Select a span to inspect its attributes and timestamped events. Look for long spans and error spans; concurrent spans overlap, so their durations do not add up to the total.

Copy the trace ID from the dialog to share it with someone who can access the workspace. A direct link has the form /aloha/traces?trace=TRACE-ID. It opens that trace directly rather than searching the selected time window. The trace must still exist in this workspace. Press Escape or use Close trace details to return to the search.

Connect traces and logs

Include the current trace ID in your application’s logs so you can find the same operation in both views. With the subscriber above, log it while inside an instrumented span:

use opentelemetry::trace::TraceContextExt;
use tracing_opentelemetry::OpenTelemetrySpanExt;

let context = tracing::Span::current().context();
let trace_id = context.span().span_context().trace_id().to_string();
tracing::info!(%trace_id, "Order processed");

Copy the full ID from Traces and search Logs with {kind="PackageLog"} |= "TRACE-ID", replacing the placeholder. You can also copy an ID from a log into Search traces or the direct-link URL.

The proxy’s X-Leilani-Request-ID correlates HttpRequest and HttpResponse log entries. It is separate from an OpenTelemetry trace ID. Log both in your application if you need to connect proxy events to spans. Returning an x-trace-id response header is something your application can implement; Leilani does not add one automatically.

For traces spanning multiple applications, configure W3C Trace Context propagation: extract incoming traceparent and tracestate into the request span’s parent context, and inject the current context into outbound calls. Without propagation, each application can create a separate trace for the same request. Each Leilani workspace can only view spans exported into its own workspace.

When traces are missing

  • Confirm the instrumented code ran, its spans finished, and your subscriber filter and sampler allow those spans.
  • Check the exporter protocol and endpoint, including signal-specific overrides. Sending a request to a static file served by Leilani never reaches your application and creates no application span.
  • Check Logs for exporter errors. Keep the provider alive, allow time for batches to arrive, and flush on shutdown.
  • Clear package, service, status, and duration filters; choose a wider time range. If you know the full trace ID, try the direct link while search indexing catches up.
  • Recent traces can be incomplete while more spans arrive. Close and reopen the detail view after another batch is exported. An unavailable-backend error is not an empty search result; retry once storage is available.