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?
- description: lambda function for cloudwatch logs
- log_group_name: /aws/lambda/
This is not an error.
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.
There was no delay according to the logs you shared. Are the events not making it into ES or what is the problem you see?
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?
@kvch I will be glad if you can confirm that there are no errors.
There was no delay or error based on the log lines you shared.
When creating a load, an error appears in the logs, see the picture
At the same time, there are no errors on the logstash side.
In this case, all the logs are delivered, where can this error come from?
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.