> 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)