Type to search.

Packetbeat isn't capturing MySQL performance data

Serverless

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Serverless interfaces and procedures might differ from classic Elastic Stack deployments.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

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:

    Shell 
    packetbeat.interfaces.device: lo0

  • Make sure the client programs you are monitoring run mysql with SSL disabled. For example:

    Shell 
    mysql --protocol tcp --host=127.0.0.1 --port=3306 --ssl-mode=DISABLED
Important

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.