New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logs Exploding with 502 errors #12
Comments
We have found out the root cause and working on a fix to avoid log explosions for all our agents. I'll get back to you when it is solved |
Hey @serkan-ozal I see that you've closed this issue. Does this mean that the 502 errors have been fixed or that only the log explosion has been fixed? |
Hi @probably-not, it has been closed automatically by Github when I merge the associated PR. I think @boroskoyo can give you more details about the issue |
Hi @probably-not, we have fixed log explosions in the agent. In case of 502 error, we haven't found anything more than one time connectivity problem. We will take further action if we encounter this problem again. |
Closing this as solved, there was on issue on the Sidekick side, an incorrect configuration. |
Starting in the last few days, my logs have exploded with the following error:
This error happens every 5 seconds.
I can't tell exactly when it started since it has been happening so much that it has caused older logs to be deleted (our log storage rolls based on storage space).
The text was updated successfully, but these errors were encountered: