> For the complete documentation index, see [llms.txt](https://docs.qpoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qpoint.io/release-notes/redis-devtools.md).

# Redis DevTools

**Redis visibility, now with a DevTools-style workflow.**

Qtap DevTools now includes a **Redis panel** so you can inspect Redis commands and responses in real time, directly from your browser. You get the same fast troubleshooting loop as HTTP DevTools, but for cache traffic: command, arguments, response, latency, and process attribution in one place.

**Released:** Feb 13, 2025

{% hint style="success" %}
**Available Now**: Redis DevTools is included in the latest qtap release with DevTools enabled.
{% endhint %}

***

## What's New

### Redis Panel in DevTools

A dedicated Redis view for live Redis traffic on the host you're debugging.

### Full Command Inspection

See each operation with details like:

* Command (`GET`, `SET`, `HSET`, `LRANGE`, etc.)
* Arguments and key usage
* Response type and value
* Per-command latency

### Process & Container Attribution

Know exactly which binary, process, and container made each Redis call.

### Real-Time Troubleshooting

Watch Redis traffic stream in as it happens and quickly isolate bad keys, command spikes, or unexpected writes.

***

## Why It Matters

Redis issues are often hard to debug under pressure:

* Cache misses causing latency spikes
* Wrong key patterns across services
* Sensitive values accidentally cached
* Hard-to-trace cross-container access

Redis DevTools gives you immediate, host-local visibility without adding application logging or restarting services.

***

## Common Use Cases

* **Incident response:** Find the exact command sequence causing failures
* **Performance debugging:** Spot expensive or high-frequency Redis operations
* **Security review:** Verify what data is being read/written to Redis
* **Service attribution:** Identify which workload is touching critical keys

***

## Feedback

Have ideas for Redis DevTools improvements?

* **GitHub Issues**: [qpoint-io/qtap](https://github.com/qpoint-io/qtap/issues)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.qpoint.io/release-notes/redis-devtools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.