Docs » Monitor Database Query Performance » Scenario: Skyler investigates Redis performance issues using Database Query Performance

Scenario: Skyler investigates Redis performance issues using Database Query Performance 🔗

Skyler, the lead site reliability engineer at Buttercup Games, has to troubleshoot high latencies reported by customers in the new advertisement service, which uses a Redis database.

  1. Check the Redis infrastructure

  2. Jump to the service in Splunk APM

  3. Examine the latency of Redis commands

  4. Dig into spans and related commands

Check the Redis infrastructure 🔗

Skyler starts by checking the Redis infrastructure in Splunk Infrastructure Monitoring. They notice that the commands processing rate has drastically dropped, and that the total number of commands processed by the server diminished.

Infrastructure view of a Redis service in Splunk Observability Cloud, with related content highlighted.

This might mean that one or more commands are causing the latency issues. To further investigate this, Skyler selects the Related Content tile at the bottom of the screen to jump to Splunk APM.

Jump to the service in Splunk APM 🔗

The service map of Splunk APM appears. Skyler immediately selects the Redis database and see at a glance which commands are the slowest. The latency and request and errors charts provide a view of the performance trend.

View of a Redis service in the Splunk APM service map.

Skyler selects Database Query Performance to get to the root of the issue.

Examine the latency of Redis commands 🔗

After opening Database Query Performance from the service map, Skyler sees the list of Redis commands, sorted by total time. For each command, they can see the requests and latency, as well as tag spotlight data.

Animation of Redis commands in Database Query Performance.

Skyler knows that commands operating on many elements, like SORT, LREM, and SUNION can be slow. They identify a command with a problematic latency, and selects the latency chart to load example traces.

Sample traces for a Redis command, as loaded from Database Query Performance.

Skyler selects the example trace to find out more about the latency of that particular span.

Learn more 🔗

See the following links for more information about Database Query Performance: