IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.

« Packetbeat is missing long running transactions Packetbeat uses too much bandwidth »

› › ›

Packetbeat isn’t capturing MySQL performance data

edit

Packetbeat isn’t capturing MySQL performance data

edit

You may be listening on the wrong interface or trying to capture data sent over an encrypted connection. Packetbeat can only monitor MySQL traffic if it is unencrypted. To resolve your issue:

Make sure Packetbeat is configured to listen on the lo0 interface:
```
packetbeat.interfaces.device: lo0
```
Make sure the client programs you are monitoring run mysql with SSL disabled. For example:
```
mysql --protocol tcp --host=127.0.0.1 --port=3306 --ssl-mode=DISABLED
```

When SSL is disabled, the connection between the MySQL client and server is unencrypted, which means that anyone with access to your network may be able to inspect data sent between the client and server. If MySQL is running in an untrusted network, it’s not advisable to disable encryption.

« Packetbeat is missing long running transactions Packetbeat uses too much bandwidth »