All Classes and Interfaces

Class
Description
An observation convention that will be set on the ObservationRegistry.
A marker interface for conventions of KeyValues naming.
Represents side of communication.
A special Observation that should be used only in special cases where clearing of scopes is important.
An act of viewing or noticing a fact or an occurrence for some scientific or other special purpose (According to dictionary.com).
A functional interface like Callable but it can throw a Throwable.
A functional interface like Runnable but it can throw a Throwable.
A mutable holder of data required by an ObservationHandler.
Read only view on the Observation.Context.
An arbitrary event that you can extend and signal during an Observation.
Scope represent an action within which certain resources (e.g.
Contains conventions for naming and KeyValues providing.
In order to describe your samples via e.g.
Allows to modify the Observation.Context on stopping the Observation before the ObservationHandler implementations process it.
Handler for an Observation.
Handler picking all matching handlers from the list.
Handler wrapping other handlers.
Handler picking the first matching handler from the list.
A predicate to define whether observation should be created or a NoopObservation instead.
Implementations of this interface are responsible for managing state of an Observation.
Access to configuration options for this registry.
An ObservationHandler that converts the context to text and publishes it to the Consumer of your choice.
A ThreadLocalAccessor to put and restore current Observation.
Read only view on the Observation.
Annotation to mark classes and methods that you want to observe.
AspectJ aspect for intercepting types or methods annotated with @Observed.
The aspect supports programmatic customizations through constructor-injectable custom logic.
 
Inspired by OpenZipkin Brave and OpenTelemetry.
Interface that allows to read propagated fields from a carrier.
Class that allows to set propagated fields into a carrier.
Context used when receiving data over the wire without requiring any confirmation to be sent to sender of the data.
Context used when receiving data over the wire with confirmation to be sent to sender of the data.
Context used when sending data over the wire with the idea that you'll wait for some response from the recipient.
Common interface for getting/setting the response object on Observation.Context implementations that handle a response.
Context used when sending data over the wire in a fire and forget fashion.