> 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/mysql-devtools.md).

# MySQL DevTools

**A DevTools-style network tab for MySQL traffic.**

Qtap DevTools now includes a **MySQL panel** so you can inspect live MySQL operations from your browser while debugging a host. See requests, responses, timing, and source process details in one workflow.

**Released:** Feb 18, 2025

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

***

## What's New

### Dedicated MySQL Panel

View MySQL traffic alongside existing DevTools tabs in a focused, database-first interface.

### Request/Response Inspection

Drill into operation details to understand what was sent, what came back, and where failures started.

### Latency & Timing View

Track query-level timing to diagnose bottlenecks and identify slow paths during incidents.

### Process & Container Context

See exactly which service or container generated each MySQL operation.

***

## Why It Matters

Database incidents are high pressure and time-sensitive. MySQL DevTools reduces time-to-diagnosis by giving you immediate visibility without adding debug code or redeploying services.

***

## Common Use Cases

* **Live incident triage:** Catch failures while traffic is flowing
* **Root-cause analysis:** Correlate app behavior with database operations
* **Performance tuning:** Identify slow or repeated operations
* **Ownership clarity:** Confirm which service is hitting each database

***

## Feedback

We'd love your feedback on MySQL DevTools.

* **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/mysql-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.