WARNING: Version 1.1 of Packetbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Why is Packetbeat missing long running transactions?
editWhy is Packetbeat missing long running transactions?
editPacketbeat 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.