Open diegoauad opened 1 year ago
Hi @diegoauad, thank you for opening an issue. I have been investigating some similar issues other users have reported with MongoDB logging. Particularly we have seen issues with particularly complicated nested logs coming from MongoDB.
Would you please open a support case so that we can assist in greater detail? In the support case, if you could include the output from our diagnostic tool as well as some representative Mongo logs if possible. You can also mention this GitHub Issue in the case.
If you do open a support case, please respond here with the case number so we can investigate.
I think this is not solved yet. We have almost 200+ VMs with Mongo workload. On some new VMs, we have the latest ops-agent 2.48.0, where we see a similar issue, and the other VMs with the earlier versions do not show this kind of issue.
Describe the bug google-cloud-ops-agent-fluent-bit.service fails to start. A 'segmentation fault' error is shown in journalctl logs.
To Reproduce Steps to reproduce the behavior:
Expected behavior All Agent Ops services working correctly, or at least an informative error message about what's misconfigured.
Environment (please complete the following information):
Additional context We are running MongoDB as a standalone replica, with authentication enabled. Monitoring works fine, we are experiencing issues with logging only.