Troubleshooting QAN: Delayed Updates on Collection/Database Deletion and Client Info

[nagaa]

Hi
I enabled Query Analytics (QAN) for my MongoDB, which is set up with primary and secondary instances in a replica set. When I drop 4 or 5 collections in the database, the changes appear in QAN almost immediately. However, when I drop just one collection or an entire database, those changes do not show up in QAN, which prevents me from accessing them in the PMM dashboard.

Additionally, I’m unable to retrieve the client IP and hostname from QAN in MongoDB. How can I resolve these issues?

[anil.joshi]

@nagaa

|However, when I drop just one collection or an entire database, those changes do not show up in QAN

Did you mean those were entirely not showing in the QAN or it just during that duration it was missing ? Did you tried changing the time range to see if it visible if covering more wider time period ? It could be possible the instant change not reflects due to the monitoring/ sample collection gap or some other delays.

The point is if it entirely not showing or just in some time period earlier ?

|Additionally, I’m unable to retrieve the client IP and hostname from QAN in MongoDB. How can I resolve these issues?

In the QAN “EXPLAIN” you can found the same under “serverInfo”

E.g,

Can you show us the details where you not seeing those details ?