When running lambda, I always see "retry" first, and then immediately connect to backoff.
How to make logs sent on first connection?
Is there any way to enable more readable logs?
This is not an error. backoff and retryer are internal elements of the publisher pipeline. All publishers contain a backoff and retry functionality and what you see in the logs are messages from the code files with those names. There is no error at that point.
The logs are just letting you know that Functionbeat is connecting to a URL and it has backoff enabled and it will retry if there is an error during connection.
Can you tell me how can I find out why there was a delay? For me, this is important and I would like to make sure that everything is done the first time.
I would like to make sure that the log is sent as quickly as possible.
Therefore, I want to make sure that the logs are sent the first time and there are no errors.
Because the words "backoff" and "retryer" indicate that the logs are sent at least the second time.
Can you confirm that the logs are sent the first time, on the first connection, without errors?
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.