Lightstreamer Workbench

Inspect Lightstreamer activity and test Item Updates or Client Messages in Chrome DevTools.

Lightstreamer Workbench adds a Chrome DevTools panel for applications that use the official Lightstreamer Web Client. It captures clients, Sessions, Subscriptions, listeners, Item Updates, snapshots, and COMMAND key lifecycles. The workspace has Runtime Scope, Ordered Evidence, and Context. Key features: - Select the page, client, Session, Subscription, item, or listener in Runtime Scope. You can inspect retired objects, but you cannot use them as Local Injection targets. - Read events in retained order. Each row shows its event number, time, Source, phase, operation, object, and key. - Use Find, Filter, selection, Capture, Coverage, and Live or Frozen independently. - Select an event to inspect its Fields, raw Evidence, Source, COMMAND details, and limits in Context. - Capture outbound Client Messages and their normal listener outcomes as ordered Evidence. - Review active conditions and recent Lightstreamer diagnostics in Notifications. Dismiss hides only the footer message. - Trace COMMAND ADD, UPDATE, and DELETE operations. Use Fields, diagnostics, and Checkpoints for more detail. - Create one protected Local Injection Draft from captured Evidence or from a live COMMAND Scope. - Edit raw JSON and validate the Draft. Captured Drafts compare Source and Draft by default, then inject directly from that preview. - Use a Local Injection Scenario for ordered Steps, immutable reviewed Runs, serial controls, Checkpoints, and results for each Step. - Deliver an Item Update to the exact live Subscription in the inspected page. Workbench reports delivered, failed, partial, unknown, and stale-target results. - Create a protected Server Injection Draft from captured Client Message Evidence, author one for an exact live client and Session, or start from an application-owned Message Recipe. - Review every LightstreamerClient.sendMessage argument, then send the Client Message once through the inspected application's normal client-to-server path. - Treat Processed as a Lightstreamer message outcome, not proof of an application business effect or later Server Update. Workbench never retries an Unknown outcome automatically. - Use WebSocket/TLCP fallback diagnostics when the primary Web Client instrumentation is not available. - Keep one temporary Event History for each Panel Session. IndexedDB can keep 100,000 records or 256 MiB. The memory fallback can keep 5,000 records or 32 MiB. - Use the Committed Evidence Boundary to find the end of complete History. Retention removes the oldest accepted prefix while Capture continues and reports the resulting Evidence Gap explicitly. - A controlled Close tries to erase Event History. An abnormal stop can leave residual data until Chrome runs the extension again. A new Panel Session starts empty. - Usage analytics helps improve feature adoption and reliability. It sends fixed feature names, engagement time, coarse outcomes, and a random installation identifier to Google Analytics. It is on by default and can be turned off in More actions → Help & resources → Usage analytics. Captured data, inspected URLs, and typed text stay local. - No advertising, account sign-in, or maintainer-operated collection backend. - Help links open the project documentation, privacy policy, and support page. Use this extension to inspect and test Lightstreamer behavior in Chrome DevTools.