From eb04b455b398c5e6334cf6598a7bf71255ec97c1 Mon Sep 17 00:00:00 2001 From: Jonathan Visser Date: Mon, 9 Mar 2026 15:55:01 +0100 Subject: [PATCH] Add tideways_redis_keys_enabled setting to Tideways documentation --- .../performance/how-to-set-up-tideways.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/best-practices/performance/how-to-set-up-tideways.md b/docs/best-practices/performance/how-to-set-up-tideways.md index e11dce53..2889a59c 100644 --- a/docs/best-practices/performance/how-to-set-up-tideways.md +++ b/docs/best-practices/performance/how-to-set-up-tideways.md @@ -45,6 +45,16 @@ You can assign an environment label (for example when this node is a staging ser hypernode-systemctl settings tideways_env_name staging ``` +#### Optional: Collect Keys for Redis Instrumentation + +Enable Redis key collection to see which keys are accessed by Redis operations in your traces. This provides more detailed insights when debugging Redis-related performance issues. + +```bash +hypernode-systemctl settings tideways_redis_keys_enabled True +``` + +**Please note:** This setting can have privacy implications if your application uses personal identifiable information (such as email addresses or IP addresses) inside Redis keys. For more information, see the [Tideways documentation on Redis instrumentation](https://support.tideways.com/documentation/setup/configuration/advanced-instrumentation.html#collect-keys-for-redis-instrumentation). + ### Activation through Control Panel It’s also possible to configure Tideways in the Control Panel.