-
Notifications
You must be signed in to change notification settings - Fork 66
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
cloud-ops-agent v2.41.0 is not collecting logs. #1445
Comments
Hi @pandrian, What are those templating things in the Ops Agent config? They kind of look like ERB. If that is what was actually fed into the Ops Agent, then it won't work. If that is not the actual config that was sent into the Ops Agent, can you attach that? (Presumably it's the expanded version of this from your deployment) |
Can you please paste the config again but in ``` markdown block so it retains formatting so we can try it? |
of course
|
Thank you! I will give it a try. If I can't find anything obvious we may ask you to open a support case, since through the official support channel we are able to get proper advanced troubleshooting information. |
all right, sounds good. thank you for taking a look at it, its a bit strange cause we had this configuration working for a while now. it broke today when puppet updated to the latest package. |
We did update the underlying Fluent Bit version, so there is a possibility this is a regression our tests didn't catch. If that is indeed the case then I expect I will be able to reproduce it pretty easily. |
BTW, you can ignore the "unknown lvalue" warnings from systemd — they are an artifact of trying to accommodate the newer versions of systemd along with the older ones. Things should still work regardless. |
You might glean some more information about the "error registering chunk with tag" errors by setting the logging |
We haven't merged the change yet that prevents debug logs from sending an exponentially high number of logs; so if you turn it on, only do it for a second and immediately turn it off. |
We were unable to reproduce the failure on our end, we're actively investigating this issue and what might help is a few sample log lines from some of the mysql log paths. This might help us reproduce the issue faster. You can redact/remove any sensitive information as you please. You can also open a support ticket with us and share the data there. Please do add the support ticket number here so I can find it easily. |
Hi @braydonk , @igorpeshansky, @ridwanmsharif sorry for long late reply about this issue, it seems even on latest version v2.45.0 its still misbehaving. Would this output make any sense to you?
After we revert back to 2.40.0
and at the end this
|
Describe the bug
google-cloud-ops-agent was updated from 2.40.0 to 2.41 and its not picking up the general_logs anymore. once reverted back to 2.40.0 logs started being collected again.
Expected behavior
It should collect the logs from the vm push them to google cloud
Environment (please complete the following information):
Any ideas what could be the problem here?
Thanks
The text was updated successfully, but these errors were encountered: