A newer version is available. For the latest information, see the current release documentation.
« Packetbeat can’t capture traffic from Windows loopback interface Packetbeat isn’t capturing MySQL performance data »
Elastic Docs ›Packetbeat Reference [7.17] ›Troubleshoot ›Common problems

Packetbeat is missing long running transactions

edit

Packetbeat is missing long running transactionsedit

Packetbeat has an internal timeout that it uses to time out transactions and TCP connections when no packets have been seen for a long time.

To process long running transactions, you can specify a larger value for the transaction_timeout option. However, keep in mind that very large timeout values can increase memory usage if messages are lost or transaction response messages are not sent.

« Packetbeat can’t capture traffic from Windows loopback interface Packetbeat isn’t capturing MySQL performance data »