/**
 * Timespan resolution for Log Analytics queries.
 *
 * The Azure Monitor Logs API treats the request-level timespan as the OUTER
 * BOUND on a query: the effective window is the intersection of the timespan
 * and any ago() filter inside the KQL. A timespan narrower than the query's
 * own ago() silently clips the results.
 */
export interface ResolvedTimespan {
    effectiveTimespan: string;
    timespanWarning?: string;
}
export declare function resolveEffectiveTimespan(query: string, explicitTimespan?: string): ResolvedTimespan;
//# sourceMappingURL=timespan.d.ts.map