I have noticed one more issue where packetbeat is not sending data for connection timeouts on nginx running on application servers. So whenever there is any 504 on nginx logs there is no corresponding log in packetbeats.
Is that mean packetbeat is not catering connection timeouts ??
Every other http response code looks like working fine but looks like all 50X response codes got some monitoring problem.
The issue is that after 10 seconds Packetbeat stops tracking the state of a transaction. The transaction timeout is not currently configurable. I will open an issue on Github for making the timeout configurable.
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.