Topic Browse 0.7.0 Readme
Overview
Allows for browsing and searching for messages on a Kafka Cluster. Deserializes messages into their respective string format and allows for filtering on messages based on their string payload.
Loggers
Below is a per-package breakdown of important packages to help operators configure logging:
| Package | Logger | Description |
|---|---|---|
|
Root package |
|
|
Consumer Service |
Kafka consumer lifecycle, partition consumption coordination, and offset management |
|
Message Deserialization |
Message and header conversion from byte arrays to string representations |
|
Avro Deserializer |
Avro message deserialization |
|
JSON Schema Deserializer |
JSON Schema message deserialization |
|
Field Masker |
Sensitive data masking functionality for JSON payloads |
|
Protobuf Deserializer |
Protobuf message deserialization |
|
Kafka Client Config |
Kafka client configuration, authentication strategies (mTLS, SASL/PLAIN, SASL/SCRAM), and SSL setup |
|
Validation Service |
Request validation, topic existence checking, and access verification |
OpenTelemetry Tracing Configuration
The service uses spring-boot-starter-opentelemetry for distributed
tracing.
By default, tracing is enabled with 100% sampling, but OTLP export is disabled.
Enabling Trace Export
To export traces to an OTLP collector (such as Jaeger, Prometheus, or others), configure:
management:
tracing:
export:
enabled: true
opentelemetry:
tracing:
export:
otlp:
endpoint: http://otlp-collector:4317 # Replace with your OTLP collector URL
transport: grpc # Export protocol: grpc or http/protobuf
headers: # Custom HTTP headers you want to pass to the collector, for example auth headers.
key: value
Adjusting Sampling
The trace.sampling.probability property controls the fraction of spans
that are collected. Setting it to 1.0 means all spans will be
exported.
To adjust the sampling rate (default is 100%):
management:
tracing:
sampling:
probability: 0.1 # 10% sampling
Support for Spring Boot 3.5.x properties
The service has support for Spring Boot 3.5.x OpenTelemetry properties.
You can use the following Spring Boot 3.5.x properties to configure OpenTelemetry:
management:
tracing:
enabled: true
otlp:
tracing:
endpoint: http://otlp-collector:4317 # Replace with your OTLP collector URL
transport: grpc # Export protocol: grpc or http/protobuf
headers: # Custom HTTP headers you want to pass to the collector, for example auth headers.
key: value
The service will map each Spring Boot 3.5.x property to the corresponding Spring Boot 4.x OpenTelemetry property.
| Spring Boot 3.5.x property | Spring Boot 4.x property | Default value |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|