Azure Filebeat Module - 412 error

Carolina Zamisnicu 316 Reputation points
2021-06-15T07:52:54.07+00:00

Hello,

I recently use the filebeat module from Azure and it seems that I receive the logs extremely hard.
When I try to restart the filebeat from my filebeat server, I receive the following error (print screen). The error 412 that there was a lease on the blob and the blob ID was not specified. I tried to delete the blob and restart the filebeat again and that worked, but that is not normal. I shouldn't delete and then restart the filebeat module every time I do not receive the logs in time.
Is there any possibility that the module can be modified or updated so I don't receive this error anymore?
On the internet I didn't find anything specific regarding this error or even if I find, it's outdated.
Thank you!

105688-microsoftteams-image-4.jpg

Community Center | Not monitored
0 comments No comments

Answer accepted by question author
Anonymous
2021-06-17T19:10:46.783+00:00

@Carolina Zamisnicu
Apologies for the delayed response and any inconvenience it has caused. Filebeat is supported by a separate company. I recommend posting your question on their dedicated forum for further assistance.

-------------------------------

Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Was this answer helpful?


0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.