Here are a few pointers, let me know if you've already checked all of those:
Make sure you're not connecting locally via the socket You'll want to ensure you're running your client or your library by connecting via either 127.0.0.1 or your remote address.
When connecting over the network, you need to ensure Packetbeat is monitoring the correct network interface.
On Linux you can monitor them all with packetbeat.interfaces.device: all
On other OSes you will have to specify one network interface explicitly. If you're connecting locally, you'd have to configure something like this: packetbeat.interfaces.device: lo0. Check your interface IDs with ifconfig on Posix systems, or ipconfig on Windows.
If those don't help, can you give a few more details about your situation?
Are you installing Packetbeat on the MySQL server directly, or trying to monitor traffic remotely?
What version of MySQL and Packetbeat are you using?
The "unmatched_responses" error would be expected when Packetbeat sees responses to queries it's unaware of (e.g. MySQL queries sent just before starting Packetbeat). Unless you're trying this on a high traffic server, I wouldn't expect it to reach 2000+ while you're starting up Packetbeat. We may need to dig deeper there.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.