All Classes and Interfaces

Class
Description
One error raised in a browser, with the detail vaadin.client.errors cannot carry.
One captured user interaction worth surfacing as an insight, with everything needed to backtrack and replicate it: which route, which component, which user action, how long it took, and, for failures, which exception and where in application code it blew up.
One captured data provider query worth surfacing as an insight: which component asked for data, on which route, how much it asked for, how much came back, and how long it took.
Retains the detail of an error a browser reported, which vaadin.client.errors counts but cannot describe.
Validates and records samples emitted by the in-browser collector.
Loads a bundled client-side JavaScript resource into a UI exactly once.
One client-side measurement, deserialized by Flow's JSON codec from the browser-side collector.
Resolves the Component an RPC invocation targets.
Captures data provider queries worth surfacing: ones that threw, and ones slower than the UX budget.
Turns captured interactions into insights, and renders the payload served at /actuator/vaadin/observability.
Captures interesting client-to-server invocations as CapturedInteractions: failed ones (when error metrics are enabled) and ones slower than the UX budget (when request metrics are enabled).
Names of the meters published by Observability Kit.
Hidden helper component attached to each UI when client metrics are enabled.
Wires Observability Kit instrumentation into a VaadinService at initialization.
Dev-mode bridge between the live Micrometer MeterRegistry and the Vaadin Copilot metrics panel.
Programmatic bootstrap for standalone (non-Spring) deployments.
Immutable settings for Observability Kit instrumentation.
Span name + attribute-key constants for Observability Kit Observations.
Bounded in-memory ring buffer of errors reported by browsers.
Bounded in-memory ring buffer of captured interactions.
Bounded in-memory ring buffer of captured data provider queries.
Portable, framework-agnostic servlet filter that observes UIDL message resends and resynchronization requests (prototype, kit-only, no Flow changes).
Prototype detector that classifies an incoming UIDL request body as a normal message, a re-sent (duplicate) message, or a full resynchronization request, and records a MeterNames.RESYNC counter for the two recovery cases.
Classification of a single UIDL request.
Result of classifying a request.
Servlet-level glue shared by the resync/resend detection filters: it recognizes UIDL requests, derives the per-UI key, and drives a ResyncDetector against per-UI state kept in the HTTP session.
Maps a Flow navigation target to a low-cardinality tag value suitable for Micrometer.
Wraps the Vaadin service Executor so that the trace context (and any other ThreadLocalAccessor-backed state) active when a task is submitted is restored when the task runs; and each task gets its own vaadin.ui.access span when an ObservationRegistry is supplied.
Exposes the Vaadin view context of the request currently being handled on this thread, so instrumentation living outside the Vaadin runtime (for example a JDBC DataSource proxy) can attribute its measurements to the view that triggered them.