Media
2 items
Description
Inspect ASP.NET Core SignalR messages, invocation flows, and connection timelines in DevTools. Debugging SignalR in a busy network log means decoding protocol frames by hand and matching requests across transports. SignalR Inspector adds a focused panel to Chrome DevTools that turns ASP.NET Core SignalR traffic into readable messages, invocation flows, stream groups, and a connection timeline. Use SignalR Inspector to: • Detect SignalR from the protocol handshake without assuming a hub URL. • Inspect formatted JSON and MessagePack Hub Protocol messages. • See WebSocket traffic, incoming Server-Sent Events, and incoming and outgoing HTTP Long Polling messages. • Pair invocations with completions, errors, cancellations, and observed duration. • Group stream items with item counts, delivery rates, and collapse controls. • Follow negotiation, transport changes, handshake state, keep-alives, reconnects, closes, acknowledgements, and sequences on a timeline. • Filter by endpoint, payload, direction, SignalR message type, and transport. • Keep routine protocol pings out of the Messages view by default and reveal them on demand. • Navigate directly between related messages, including filtered rows and collapsed stream groups. • Export a bounded trace to a versioned JSON file and import it later for offline review or a reproducible bug report. How to use it: 1. Open Chrome DevTools on the application you want to inspect and select SignalR Inspector. Opening DevTools starts passive Long Polling observation for that tab. 2. Click the SignalR Inspector toolbar icon to enable WebSocket and Server-Sent Events instrumentation for the current tab. The page reloads so the connection handshake can be captured from the beginning. 3. Use the application normally, then inspect messages in the Messages and Timeline views. Privacy and permissions: Captured traffic stays in a bounded, per-tab in-memory log unless the developer explicitly exports it to a local JSON file. SignalR Inspector has no analytics, advertising, telemetry, remote services, data synchronization, or remotely hosted code. It does not sell or transmit captured data. Connection IDs, connection tokens, and common access-token parameters are removed from displayed and exported endpoints. Payload bodies larger than 256 KiB are not retained. Exported files preserve application payloads and remain under the developer's control. The activeTab permission grants temporary access only after the toolbar icon is clicked. The scripting permission installs the extension's packaged instrumentation in that activated tab. SignalR Inspector declares no host permissions and does not request access to every website. Current limitations: • Outgoing Server-Sent Events HTTP posts are not captured. • WebSocket and Server-Sent Events traffic created inside iframes or Web Workers is not captured. • Non-SignalR binary payloads and malformed or incomplete MessagePack frames fall back to Base64 and hex previews. • Page code can detect or bypass page-level instrumentation, so this is a diagnostics tool rather than a security monitor. SignalR Inspector is an independent, open-source developer tool and is not affiliated with or endorsed by Microsoft. What's new in 0.11.1: • Added versioned JSON export for the current bounded SignalR trace. • Added locally validated, atomic session import for offline review and reproducible bug reports. • Removed transient tab and row IDs, replaced browser document IDs with session-local pseudonyms, re-sanitized endpoint tokens, and assigned fresh local identities during import. • Kept permissions unchanged and added no telemetry, remote services, synchronization