@grow-codes/zipkin - v0.1.1
    Preparing search index...

    Interface ZipkinTraceQuery

    Filter of ZipkinQueryClient.getTraces (GET /api/v2/traces). Every field is optional; unset fields use the server defaults (endTs = now, lookback = 24 h, limit = 10). annotationQuery, tags and annotations are combined with and (Zipkin supports AND only).

    interface ZipkinTraceQuery {
        annotationQuery?: string;
        annotations?: string[];
        endTs?: number | Date;
        limit?: number;
        lookbackMs?: number;
        maxDurationMicros?: number;
        minDurationMicros?: number;
        remoteServiceName?: string;
        serviceName?: string;
        signal?: AbortSignal;
        spanName?: string;
        tags?: Record<string, string>;
    }

    Hierarchy (View Summary)

    Index
    annotationQuery?: string

    Raw Zipkin annotation query, e.g. http.method=GET and error.

    annotations?: string[]

    Bare terms: a tag key or an annotation value (error, cache.miss).

    endTs?: number | Date

    End of the window: a Date or epoch milliseconds. Default: server now.

    limit?: number

    Maximum number of traces. Default: server default (10).

    lookbackMs?: number

    Window length before endTs in ms. Default: server QUERY_LOOKBACK (24 h).

    maxDurationMicros?: number

    Maximum span duration in microseconds (needs minDurationMicros).

    minDurationMicros?: number

    Minimum span duration in microseconds.

    remoteServiceName?: string

    Remote service name (remoteEndpoint.serviceName) seen on serviceName's spans.

    serviceName?: string

    Local service name (matched case-insensitively).

    signal?: AbortSignal

    Cancels the call (CancelledError).

    spanName?: string

    Span name.

    tags?: Record<string, string>

    Exact tag matches (key=value). A key or value that contains and (or a key that contains =) cannot be expressed in Zipkin's syntax: that term is matched client-side after the query (so fewer than limit traces may come back).