Configuring Observability Kit
Instrumentation can be configured in the agent.properties file that’s used with the Java agent.
Service Configuration
The service attributes are used to differentiate traces from services or applications which might have many instances running simultaneously, such as horizontally scaled services.
The service attributes are as follows:
service.name-
is an attribute that’s used to distinguish a service by name. The default value is
vaadin— the only attribute with a default value. It’s also the only one required. service.namespace-
helps to distinguish a group of services.
service.instance.id-
helps to distinguish instances of the same service that exist simultaneously. It must be unique for each instance of the same
service.namespace,service.namepair. service.version-
is the semantic versioning string of the service version.
The service.name attribute is configured using the otel.service.name property, either in the agent.properties configuration file as a system property, or as an environment variable.
Add the following line to the agent.properties file:
otel.service.name=myappOther service attributes are configured using the otel.resource.attributes property, either in the agent.properties configuration file as a system property, or as en environment variable. Multiple attributes are separated by commas.
Add the following line to the agent.properties file:
otel.resource.attributes=service.namespace=myservices,service.instance.id=myapp-euFor more information about service configuration, see the OpenTelemetry documentation.
Default OpenTelemetry Instrumentation
The custom distribution disables default OpenTelemetry instrumentation for Vaadin and servlets.
The default instrumentation is disabled because logging all requests for a single-page application isn’t helpful — although it does generate plenty of data. It was disabled to have control over which requests generate a trace.
The jetty, servlet, and tomcat instrumentation modules are disabled by default. To enable any of them, add the following line to the agent.properties file:
otel.instrumentation.${instrumentationName}.enabled=trueFrontend Observability Configuration
Frontend observability is enabled by default, with all the client-side instrumentation active. The configuration can be tuned in two ways: statically by editing the agent.properties file, or by providing environment variables or system properties; or dynamically by implementing the ObservabilityClientConfigurer interface, which applies changes at runtime.
With static configuration, the same settings are applied to all UI instances. Changes to the configuration require a server restart.
With dynamic configuration, the instrumentation can be enabled or disabled at runtime, without restarting the server. The configuration can also be tuned for a specific browser tab. Changes are applied when the browser page is reloaded.
Frontend Observability Static Configuration
Static frontend observability configuration can be provided by adding entries to the agent.properties file or with environment variables or system properties, as mentioned earlier.
The following properties can be used to tune frontend instrumentation:
| Property Name | Description | Default Value |
|---|---|---|
| Enables or disables all frontend instrumentation. |
|
| Enables or disables the Document Load instrumentation. |
|
| Enables or disables the User Interaction instrumentation. |
|
| Enables or disables the XML HTTP Request instrumentation. |
|
| Enables or disables the Long Task instrumentation. |
|
| Enables or disables the Frontend Error instrumentation. |
|
For more information about the frontend instrumentation, consult the Observability Kit Reference page.
Frontend Observability Runtime Configuration
By default, frontend observability enables all out-of-the-box client-side instrumentation. Observability Kit provides a way to enable, disable and tune the instrumentation at runtime.
This is done by implementing the ObservabilityClientConfigurer interface and applying the desired settings to the ObservabilityClientConfiguration instance provided to the configure method. The configuration is applied during UI initialization: The Configurer logic can access the current VaadinRequest. If a security infrastructure has been configured for a project and the user is logged into the application, the user details can also be accessed. This allows fine-tuning of observability to single-user level.
For example, the following implementation shows how to set up observability based on a mutable configuration tied to the currently logged-in user.
public class UserBasedFrontendObservability implements ObservabilityClientConfigurer {
@Override
public void configure(ObservabilityClientConfiguration config) {
var request = VaadinRequest.getCurrent();
var userSettings = fetchConfiguration(request.getUserPrincipal());
config.setEnabled(userSettings.isEnabled());
config.setDocumentLoadEnabled(userSettings.isDocumentLoad());
config.setUserInteractionEnabled(userSettings.isUserInteraction());
config.setLongTaskEnabled(userSettings.isLongTask());
config.setXMLHttpRequestEnabled(userSettings.isXmlHttpRequest());
config.setFrontendErrorEnabled(userSettings.isFrontendError());
}
private UserObservabilityConfig fetchConfiguration(Principal user) {
if (user != null) {
// fetch the configuration for the given user from some storage
// e.g. in-memory data structure, database table, properties file, ...
UserObservabilityConfig config = new UserObservabilityConfig();
config.setXmlHttpRequest(false);
return config;
}
// user not logged-in, return null or a default configuration
return new UserObservabilityConfig();
}
static class UserObservabilityConfig {
private boolean enabled = true;
private boolean documentLoad = true;
private boolean userInteraction = true;
private boolean longTask = true;
private boolean xmlHttpRequest = true;
private boolean frontendError = true;
public boolean isEnabled() {
return enabled;
}
public void setEnabled(boolean enabled) {
this.enabled = enabled;
}
public boolean isDocumentLoad() {
return enabled && documentLoad;
}
public void setDocumentLoad(boolean documentLoad) {
this.documentLoad = documentLoad;
}
public boolean isUserInteraction() {
return enabled && userInteraction;
}
public void setUserInteraction(boolean userInteraction) {
this.userInteraction = userInteraction;
}
public boolean isLongTask() {
return enabled && longTask;
}
public void setLongTask(boolean longTask) {
this.longTask = longTask;
}
public boolean isXmlHttpRequest() {
return enabled && xmlHttpRequest;
}
public void setXmlHttpRequest(boolean xmlHttpRequest) {
this.xmlHttpRequest = xmlHttpRequest;
}
public boolean isFrontendError() {
return enabled && frontendError;
}
public void setFrontendError(boolean frontendError) {
this.frontendError = frontendError;
}
}
}With the above implementation, the configuration can be fetched from a database table. This allows changes to be applied at runtime after a browser page reload.
The Configurer is loaded through the Java ServiceLoader API, by adding the file com.vaadin.observability.ObservabilityClientConfigurer to the src/main/resources/META-INF/services/ directory, with the content being the fully qualified name of the Configurer class. For this example, the file looks like this:
com.vaadin.observability.ObservabilityClientConfigurer
org.example.UserBasedFrontendObservabilityFor details on observability client settings, consult the Javadocs of the ObservabilityClientConfiguration interface.
|
Note
|
Load Configurer in Spring Project
For Spring based projects, the Configurer can be loaded by exposing the implementation as a Spring managed @Bean, without the need to register the class for the ServiceLoader API.
|