[glen-84]

Summary

The event tables on the instrumentation page did not match the diagnostic listeners. This updates all three tables and the server listener sample:

• Removes SyntaxError and the three operation complexity events, which the execution listener does not declare, and adds AnalyzeOperationCost, OperationCost, DocumentNotFoundInStorage, UntrustedDocumentRejected, WebSocketConnectionInitialized, and the four batch dispatch coordinator events.
• Corrects when RequestError, StartProcessing, StopProcessing, RunTask, and ResolvedTaskFromCache are raised, notes that RunTask also requires EnableResolveFieldValue, and moves rows that were out of order in the request flow, keeping each error event next to its scope.
• Fixes the server listener sample, whose ExecuteHttpRequest override did not match the method's signature.

[Copilot]

🟡 Changes recommended

Unresolved documentation corrections remain for event ordering and lifecycle descriptions.

1 open issue

• Avoid fixed ordering for RequestError events · New

What changed in this PR

Updates the instrumentation documentation to align diagnostic event tables and the server listener sample with current Hot Chocolate behavior.

Changes:

• Adds current diagnostic events and removes obsolete ones.
• Corrects event descriptions, lifecycle ordering, and configuration notes.
• Fixes the ExecuteHttpRequest override signature and documents batch coordinator events.

File	Description
website/​content/​docs/​hotchocolate/​server/​instrumentation.md	Updates server, execution, and DataLoader event tables and corrects the server listener example.

_{Review effort: Lite}

[Copilot]

🔵 Needs a closer look

The reviewed event descriptions and ordering contain unresolved accuracy issues that should be corrected before approval.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Clarify StopProcessing covers all task-processing pauses

website/​content/​docs/​hotchocolate/​server/​instrumentation.md:160

StopProcessing is raised whenever WorkScheduler pauses its task loop, including while it is waiting for in-flight execution tasks or pending DataLoader dispatches, not only while waiting for resolvers. Please describe the event as pausing task processing while waiting for more work or in-flight tasks to complete so listeners do not infer that it exclusively represents resolver waits.

1 resolved since last review

• Avoid fixed ordering for RequestError events

_{Review effort: Lite}

[Copilot]

🔵 Needs a closer look

The reviewed documentation still has three event-ordering and event-behavior descriptions that need correction.

No open issues 🎉

1 previously missed issue

In code that hasn't changed since last review

Describe ResolveFieldValue as an additional resolver event

website/​content/​docs/​hotchocolate/​server/​instrumentation.md:161

RunTask is not an alternative to ResolveFieldValue for field resolvers. ExecutionTask.ExecuteInternalAsync wraps every execution task in Context.Track(this), while ResolverTask.ExecuteAsync separately wraps the resolver in ResolveFieldValue; when EnableResolveFieldValue is enabled, a resolver therefore raises both events. Please describe ResolveFieldValue as an additional event rather than saying it is raised instead.

_{Review effort: Lite}