Release Notes
Announcements
Client Configurations
Full-Link Analysis is only supported for the Spring Boot + Lettuce framework. Lettuce handles command latency collection and aggregation, while Spring Boot completes data reporting through the OTLP module. This article details client-side configuration requirements to help you properly configure reporting parameters and verify whether data collection is effective.
Environment Requirement
Environment | Feature Description | Version Requirements | Reference Documentation |
Lettuce | Lettuce performs latency statistics for each command and aggregates similar commands by statistical window. | Recommended version 6.4.2.RELEASE or above | |
Spring Boot | Spring Boot reports monitoring data through the OTLP module. | Recommended version 3.4.3 or above |
Spring Boot Configuration Parameters
In the project's application.properties configuration file, configure reporting parameters by referring to the following table.
# === Required Configuration ===# Reporting Authentication Tokenmanagement.otlp.metrics.export.resourceAttributes.token=your-token# Reporting Addressmanagement.otlp.metrics.export.url=http://10.0.0.1:8080# Reporting Mode (fixed value)management.otlp.metrics.export.aggregationTemporality=delta# P99 Latency Statisticsmanagement.metrics.distribution.percentiles.lettuce.command.completion=0.99management.metrics.distribution.percentiles.lettuce.command.firstresponse=0.99# Expose the metrics endpoint as an HTTP-accessible interfacemanagement.endpoints.web.exposure.include=metrics# === Business Identifier ===# Business Namemanagement.otlp.metrics.export.resourceAttributes.service.name=my-service# Machine Addressmanagement.otlp.metrics.export.resourceAttributes.report-addr=192.168.1.100:8080# === Optional Configuration ===# Reporting Interval (default 1 minute)management.otlp.metrics.export.step=60s
Parameter Category | Parameter | Note |
Required parameter | management.otlp.metrics.export.resourceAttributes.token | |
| management.otlp.metrics.export.url | Dedicated channel reporting address. Enabling the end-to-end feature obtained reporting address. Format: http://VIP:VPORT. |
| management.otlp.metrics.export.aggregationTemporality=delta | Data reporting mode, which must be set to delta, indicating the upload of incremental data rather than cumulative data. |
| management.metrics.distribution.percentiles.lettuce.command.completion | Enable percentile statistics of command completion latency. |
| management.metrics.distribution.percentiles.lettuce.command.firstresponse | Enable percentile statistics of first byte response latency. |
| management.endpoints.web.exposure.include=metrics | Expose the metrics endpoint of Spring Boot Actuator to make metric data accessible via HTTP. |
Business identifier | management.otlp.metrics.export.resourceAttributes.service.name=XXXXX | Business name, customizable as needed. |
| management.otlp.metrics.export.resourceAttributes.report-addr=IP:PORT | Current client IP address and PORT. |
Optional | management.otlp.metrics.export.step=XXs | Set the frequency for reporting data. Unit: seconds. Default value: 60s, meaning monitor data is reported once every minute. |
Verify Lettuce collection
After configuration, access the following endpoint to view the Lettuce client's Distributed Cache connection metrics:
View all metrics: /actuator/metrics
View Lettuce command metrics: /actuator/metrics/lettuce.command.completion.
View connection pool metrics: /actuator/metrics/lettuce.pool.active (if connection pool is enabled).
Verify OTLP reporting
Observe Spring Boot logs to confirm no errors in OTLP reporting. If errors occur, check:
Whether the Token is correctly configured.
Whether the VIP and VPORT configurations are accurate.
Whether the network is connected to the VIP.
After successful reporting, you can view end-to-end monitoring data in the CLS console. For details, see Visualization Display.
피드백