> 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-protocol-support.md).

# MySQL Protocol Support

**See what your MySQL traffic is actually doing.**

Qtap now supports **MySQL protocol parsing** with command/query visibility and **STARTTLS-aware inspection**, so you can troubleshoot database traffic with the same depth you've had for HTTP and Redis.

**Released:** Feb 16, 2025

{% hint style="success" %}
**Available Now**: MySQL protocol support is included in the latest qtap release.
{% endhint %}

***

## What's New

### MySQL Protocol Parsing

Decode MySQL traffic into structured operations so you can inspect activity beyond connection metadata.

### STARTTLS Support

When MySQL sessions upgrade to TLS via STARTTLS, Qtap continues protocol-aware visibility for supported environments.

### Query and Response Context

Analyze requests and server responses with timing to pinpoint slow paths and failing operations.

### Process Attribution

Tie MySQL activity back to the exact process/container making the call.

***

## Why It Matters

Before this release, MySQL debugging often required app-level logging, slow-query logs, or manual correlation.

Now you can quickly answer:

* Which service issued this query?
* Which operations are timing out?
* Did the session switch to TLS?
* What changed during the incident window?

***

## Common Use Cases

* **Production troubleshooting:** Isolate failing queries quickly
* **Performance analysis:** Find expensive patterns and latency spikes
* **Security/compliance:** Validate encrypted session behavior with STARTTLS
* **Dependency mapping:** See which workloads actually use each database

***

## Feedback

Tell us what MySQL workflows you want next.

* **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-protocol-support.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.