Observability Kit
Insights into Flow applications at runtime and in production by monitoring application health, detecting unhandled errors and performance issues, and observing user behavior.
|
Note
|
Commercial Feature
A commercial Vaadin subscription is required to use Observability Kit in your project. |
Observability Kit provides integration with industry-leading Application Performance Monitoring (APM) and observability tools to provide insight into both the frontend and backend of an application.
At its core, Observability Kit is built on Micrometer.
It instruments the Vaadin runtime and records metrics into your application’s MeterRegistry, while emitting tracing spans through the Micrometer Observation API — so the data flows to whatever backend you already use.
With Spring Boot, it’s a drop-in: add one dependency and you’re done.
|
Note
|
Migrating From Version 4?
Earlier versions of Observability Kit were a standalone OpenTelemetry Java agent.
See the Migrating to Version 5 page if you’re upgrading an existing project.
|
Topics
- Getting Started
- Step-by-step guide on how to use Observability Kit in an application.
- Migrating to Version 5
- How to move a Vaadin application from the version 4 OpenTelemetry agent to the Micrometer-based version 5 of Observability Kit.
- Configuration
- How to configure Observability Kit and what its default settings are.
- Custom Instrumentation
- How to record your own metrics and traces alongside the kit's built-in instrumentation, using annotations, the fluent Micrometer API, or raw registry beans.
- Integrations
- Observability Kit records into a Micrometer registry, so it exports to any backend Micrometer and Spring Boot Actuator support.
- Reference
- The metrics and tracing spans Observability Kit records, with their types, tags, and attributes.
058FD664-1011-4141-9D5B-3487D6935CC5