Mongodb Atlas receiver not able to pull logs issue #31978
Labels
Comments
preshit1505
added
bug
|
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Potentially related: #28851 |
|
What could be the solution for this? |
|
Below is something which I saw in the logs as well.
|
|
Any suggestions here? |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
@crobert-1 ?? |
|
Unfortunately I don't have any experience with this component, so I don't have any more information here. I was simply pointing out another issue that looked similar. 👍 |
|
I don't see anything obviously wrong with the config. Maybe @schmikei has ideas. |
|
Looking at the logs it seems like this is still running v0.88.0 of the collector? Just like in #28851, Is there any way we can upgrade the collector to v0.89.0 at a minimum to pull in the changes from #29084 to see if that helps gleam anything about the host that is getting EOF'ed? Another debug tool we can use is the https://www.mongodb.com/docs/atlas/cli/stable/command/atlas-logs-download/#atlas-logs-download to further help debug the request once we get more information from the logs. |
|
The version has been updated to 0.101.0 but I still seeing those log errors |
|
|
Seems like the problem is more on the later error though right?
perhaps the host is running out of memory while trying to decode the logs? Are you able to provide deployment information around how much memory is provisioned to the collector? |
|
|
|
My assumption is that is the culprit, if there is a way to temporarily up the memory allocation to see if that resolves your issue, that might be at least a quick sanity check. |
|
@schmikei I tried to increase the resource limit (500m cpu and 3Gi memory) but it is still not getting the logs. But i dont see the error for memory usage. This is what logs say: 
|
|
Hmm could you try to download those logs via the mongodbatlas CLI to see what the logs look like for that host? The "attempted to retrieve host logs but received 0 logs" could just be valid for the request that the receiver is making. if there is a difference from the expected format I could imagine a change to make, however it could also very well be that those files have nothing to process and is expected behavior |
|
@schmikei This is the log file i downloaded from the console |
|
|
Those logs are all from the June 10th, the receiver's request that is EOFing (I assume correctly) is for Tue Jun 11 2024 18:43:19 GMT+0000 If you want you can limit your console download for that period to see if it's a valid EOF which I now am at least assuming it is. |
|
@schmikei Here is the logs |
|
@schmikei Any suggestion after looking at the logs? 🤔 |
Unfortunately I'm kind of stumped, those look like the correctly formatted JSON logs we are expecting... The only thing I could suggest to help troubleshoot more is rather than using the UI to download that we try to use the CLI to better replicate what the receiver is doing and if that gleams anything obvious thats going on here... If still unable to replicate, and if you're willing, you can try to clone down the repository and make modifications/print statements if it helps debug: opentelemetry-collector-contrib/receiver/mongodbatlasreceiver/logs.go Lines 158 to 184 in 5bd5a1b Always happy to help collaborate on a PR but I'm coming up stumped in this circumstance :/ |
|
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
|
Any updates on this issue? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Component(s)
receiver/mongodbatlas
What happened?
Description
I have setup the mongodb atlas receiver for getting the logs but I am not seeing any logs coming into the collector
Steps to Reproduce
Expected Result
Expected to be getting the logs
Actual Result
{"level":"warn","ts":1711471695.0430725,"caller":"[email protected]/logs.go:259","msg":"Attempted to retrieve audit logs but received 0 logs","kind":"receiver","name":"mongodbatlas","data_type":"logs","error":"EOF","log":"mongodb-audit-log.gz"}
{"level":"warn","ts":1711471693.930057,"caller":"[email protected]/logs.go:229","msg":"Attempted to retrieve host logs but received 0 logs","kind":"receiver","name":"mongodbatlas","data_type":"logs","error":"EOF","log":"mongos.gz"
Collector version
mongodb atlas version 6.0.14
Environment information
No response
OpenTelemetry Collector configuration
Log output
{"level":"warn","ts":1711471695.0430725,"caller":"[email protected]/logs.go:259","msg":"Attempted to retrieve audit logs but received 0 logs","kind":"receiver","name":"mongodbatlas","data_type":"logs","error":"EOF","log":"mongodb-audit-log.gz"} {"level":"warn","ts":1711471693.930057,"caller":"[email protected]/logs.go:229","msg":"Attempted to retrieve host logs but received 0 logs","kind":"receiver","name":"mongodbatlas","data_type":"logs","error":"EOF","log":"mongos.gz"Additional context
Audit logs are already enabled from atlas UI
The text was updated successfully, but these errors were encountered: