[boks1971]

Goal
Measure agent join latency step by step. That needs a time for each step of a job, and what created its dispatch.

sequenceDiagram
  participant S as Server
  participant W as Agent worker
  Note over S: Job.created_at
  S->>W: AvailabilityRequest, JobState.started_at
  W->>S: AvailabilityResponse, JobState.accepted_at
  S->>W: JobAssignment, JobState.assigned_at

Loading

Change

• Job.created_at, JobState.accepted_at and JobState.assigned_at are added. They are Unix nanoseconds, like started_at, and the state times describe the current attempt.
• AgentDispatchState.trigger sets when the user's wait starts: ADT_JOIN, ADT_ROOM_API or ADT_DISPATCH_API. Older servers leave ADT_UNSPECIFIED.
• lk.rtc.joinRequestTime is a participant attribute with the time the server received a new user's join request, in Unix milliseconds like lk.sip.inviteTime. A WebRTC user's wait starts there, before node selection and connect retries.

Tests
go build ./... and go test ./livekit/ pass.

🤖 Generated with Claude Code

[changeset-bot]

🦋 Changeset detected

Latest commit: e65bd86

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
github.com/livekit/protocol	Patch
@livekit/protocol	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR