콘텐츠로 건너뛰기
DeepTokenAI 크리에이티브 스위트
홈대시보드모델프롬프트리더보드문서가격엔터프라이즈블로그
    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

    기능 스냅샷

    real-time

    request log stream

    live

    provider health board

    audit-ready

    change audit trail

    핵심 이점

    실제 프로덕션 워크플로에 매핑된 주요 가치 포인트.

    이점

    01

    Per-request visibility

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

    이점

    02

    Provider health board

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

    이점

    03

    Auditable change log

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

    권장 워크플로

    게이트웨이 호출, 라우팅 정책, 과금 제어에 이 기능을 통합하는 3단계 경로.

    단계 1

    Stream request logs

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

    1

    단계 2

    Inspect provider health

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

    2

    단계 3

    Review audit trail

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

    3

    자주 묻는 질문

    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.

    다음 단계

    이 기능을 프로덕션에 배포할 준비가 되셨나요?

    문서, 모델 카탈로그 또는 대시보드에서 시작하여 실제 트래픽으로 이 기능을 검증하세요.

    Open Observability기능 목록으로