Saltar al contenido
DeepTokenSuite creativa con IA
InicioPanelModelosIndicacionesTabla de classificaçãoDocsPreciosEmpresasBlog
    Observability

    Observability & Audit

    Per-request logs, provider health, and audit trail for every change

    Inspect latency, success rate, token counts, and provider behavior per request. Every routing, key, and billing change is recorded for compliance and post-mortem.

    Open ObservabilityView Pricing
    Per-request visibilityProvider health boardAuditable change log

    Resumen de capacidades

    real-time

    request log stream

    live

    provider health board

    audit-ready

    change audit trail

    Beneficios principales

    Puntos de valor clave asignados a flujos de producción prácticos.

    Beneficio

    01

    Per-request visibility

    Latency, retries, fallback hops, token counts, and error categories are recorded for every request.

    Beneficio

    02

    Provider health board

    Track success rate, latency percentiles, and rate limit events per provider over rolling windows.

    Beneficio

    03

    Auditable change log

    Routing, key, member, and billing changes are stored in an append-only audit trail with actor and timestamp.

    Flujo de trabajo recomendado

    Un camino simple de 3 pasos para integrar esta capacidad en llamadas de pasarela, políticas de enrutamiento y controles de facturación.

    Paso 1

    Stream request logs

    Open the live log view to follow active traffic and recent errors in real time.

    1

    Paso 2

    Inspect provider health

    Drill into each provider for latency, success rate, and rate limit pressure.

    2

    Paso 3

    Review audit trail

    Filter the audit log by actor, resource, and action to investigate incidents and reconcile changes.

    3

    Preguntas frecuentes

    How long are request logs retained?

    Retention is plan-dependent and ranges from 7 days on Free up to 90 days on Pro. Enterprise plans support longer retention.

    Are request payloads stored?

    Metadata is always stored. Full payload storage is opt-in per organization and respects provider data policies.

    Siguiente paso

    ¿Listo para poner esta función en producción?

    Comience desde la documentación, el catálogo de modelos o el panel y valide esta capacidad con tráfico de producción real.

    Open ObservabilityVolver a funciones