Skip to content

WebSocket diagnostic channels lack request identities #4081

Open
@legendecas

Description

@legendecas

This would solve...

The diagnostic channels for WebSocket connections have no request identities to chain up diagnostic information. Listeners of these channels can not associate each diagnostic events with a certain request with the limited information.

For example, undici:websocket:socket_error only provides an error object, without a hint of which websocket request caused the error. So do channels like undici:websocket:open, undici:websocket:ping, and undici:websocket:pong.

The implementation should look like...

The WebSocket diagnostic channel should also provide a consistent request identity (object), like the WebSocket instance.

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions