import { type OtelSpan } from "@fiberplane/fpx-types";
import type { IExportTraceServiceRequest } from "@opentelemetry/otlp-transformer";
export declare const OTEL_TRACE_ID_REGEX: RegExp;
/**
 * Check if a trace ID is a valid otel trace id
 */
export declare function isValidOtelTraceId(traceId: string): boolean;
/**
 * Generate a trace ID that is compatible with the OpenTelemetry standard
 * Otel trace ids are 16 bytes long, and can be represented as a hex string
 */
export declare function generateOtelTraceId(): string;
/**
 * NOT IN USE - TEST ME
 *
 * A version of generateOtelTraceId that is compatible with the web standards
 */
export declare function generateOtelTraceIdWebStandard(): string;
/**
 * HACK - Port of the rust code that massages traces into the format we use in the UI.
 *
 * A few differences:
 *
 * - The otel js library does not expose `traceFlags` or `flags` from what I can tell,
 *   so that field is always blank.
 *
 * - `mapAttributes` simply returns the value, instead of an object whose key describes the attribute data type.
 *   By convention, we only use string and number values. Complex values are serialized.
 */
export declare function fromCollectorRequest(tracesData: IExportTraceServiceRequest): Promise<Array<OtelSpan>>;