Skip to content

Add tideways_redis_keys_enabled setting to Tideways documentation #460

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
poespas wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add tideways_redis_keys_enabled setting to Tideways documentation #460

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/best-practices/performance/how-to-set-up-tideways.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down