New: Passkey Benchmark 2026 · compare your rollout

Authentication Observability

Most login failures happen where your logs can't see

Between the login button and the session sit the browser, the operating system and the password manager. The debugger shows that part for one ceremony on your device. Corbado Observe shows it for every login in production, across all your authentication methods.

One login, five stages

Each stage links to the KPI that measures it.

  1. 01

    Login offered

    The user sees the login.

  2. 02

    Method started

    Passkey, password or OTP.

  3. 03Not in server logs

    Passkey prompt

    Browser and OS sheet opens.

  4. 04Not in server logs

    Authenticator

    Biometrics, PIN or security key.

  5. 05

    Session

    Your server verifies it.

Most read

The guides teams open first when logins fail.

Questions

Why don't server logs show passkey failures?
The passkey prompt, the biometric or PIN step and the password manager run in the browser and the operating system. Your server only sees the request that arrives after the user finished. A cancelled prompt or a NotAllowedError never reaches it.
Which KPIs show whether a passkey rollout works?
Passkey Enrollment Rate and Passkey Usage Rate show adoption. Authentication Error Rate and Passkey Authentication Success Rate show reliability. Time to Authenticate and Authentication Drop-Off Rate show friction.
What is authentication observability?
Measuring every login from the moment it is offered to the session, including the part in the browser, the OS and the password manager, across all authentication methods. Corbado Observe does this in production. The Passkeys Debugger shows it for one ceremony on your device.

Corbado Observe

The debugger shows one login. Observe shows all of them.

The same client-side detail for every login in production, so you see where users fail before support tickets do.

  • Every authentication method

  • Per-user journeys

  • Device readiness

  • Your existing IdP