Release Notes and Announcements

Release Notes

Announcements

User Tutorial

Product Introduction

Overview

Product Strengths

Use Cases

Storage Engine

Product Series

Product Versions

Specifications and Performance

Read/Write Separation

Multi-AZ Deployment

Regions and AZs

Terms

Service Regions and Service Providers

Purchase Guide

Billing Overview

Pricing Center

Instance Purchasing

Renewal (Yearly/Monthly Subscription)

Refund (Yearly/Monthly Subscription)

Overdue Payments

Switching from Pay-as-You-Go to Yearly/Monthly Subscription

Getting Started

Quickly Creating an Instance

Connecting to Redis Instance

Operation Guide

Operation Overview

Connecting to a Database Instance

Managing Instances

Upgrade Instance

Management Node (Redis/ValKey Edition)

Multi-AZ Deployment Management

Backup and Restoration

Managing Accounts

Parameter Configuration

Slow Query

Access Management

Network and Security

Monitoring and Alarms

Event Management (Redis/ValKey Edition)

Data Migration

Global Replication for Redis Edition

Database Audit

Performance Optimization

Sentinel Mode

Development Guidelines

Naming Rules

Basic Usage Guidelines

Design Principles of Key and Value

Command Usage Guidelines

Design Principles of Client Programs

Connection Pool Configuration

Command Reference

Command Reference Overview

Redis Edition and Valkey Edition Command Compatibility

Version Command Usage Differences

Differences Between the Proxy Architecture and Direct Connection Mode

More Command Operations (Redis/Valkey Edition)

Memcached Edition Command Compatibility

Practical Tutorial

Building TencentDB for Redis® Client Monitoring Based on Spring Boot

Redis Client Connection Configuration Policy and Practice

Global SCAN Guide for Cluster Architecture

Eliminating Instances Securely

Hot Key and Big Key

AZ Migration Scheme

Troubleshooting

Connection Exception

Exception Analysis and Solution of Redisson Client Timeout Reconnection

Performance Troubleshooting and Fine-Tuning

API Documentation

History

Introduction

API Category

Making API Requests

Instance APIs

Parameter Management APIs

Other APIs

Backup and Restoration APIs

Region APIs

Monitoring and Management APIs

Log APIs

Data Types

Error Codes

FAQs

General

Connection and Login

Purchase

Service Agreement

Service Level Agreement

Glossary

Client Configurations

PDF

Focus Mode

Font Size

Last updated: 2026-03-25 10:28:29

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
Lettuce Latency Tracing
Spring Boot
Spring Boot reports monitoring data through the OTLP module.
Recommended version 3.4.3 or above
Micrometer OTLP
OpenTelemetry Spring Boot
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 Token
management.otlp.metrics.export.resourceAttributes.token=your-token
# Reporting Address
management.otlp.metrics.export.url=http://10.0.0.1:8080
# Reporting Mode (fixed value)
management.otlp.metrics.export.aggregationTemporality=delta
# P99 Latency Statistics
management.metrics.distribution.percentiles.lettuce.command.completion=0.99
management.metrics.distribution.percentiles.lettuce.command.firstresponse=0.99
# Expose the metrics endpoint as an HTTP-accessible interface
management.endpoints.web.exposure.include=metrics
# === Business Identifier ===
# Business Name
management.otlp.metrics.export.resourceAttributes.service.name=my-service
# Machine Address
management.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
Reporting authentication credential, the Token obtained by enabling the end-to-end feature.
﻿
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.

Help and Support

Was this page helpful?

You can also Contact sales or Submit a Ticket for help.

Help us improve! Rate your documentation experience in 5 mins.

Feedback

tencent cloud

Tencent Cloud Distributed Cache (Redis OSS-Compatible)

Client Configurations

Environment Requirement

Spring Boot Configuration Parameters

Verify Lettuce collection

Verify OTLP reporting

Help and Support

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	Lettuce Latency Tracing
Spring Boot	Spring Boot reports monitoring data through the OTLP module.	Recommended version 3.4.3 or above	Micrometer OTLP OpenTelemetry Spring Boot

Parameter Category	Parameter	Note
Required parameter	management.otlp.metrics.export.resourceAttributes.token	Reporting authentication credential, the Token obtained by enabling the end-to-end feature.
		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.
Business identifier		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.