-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.17, 3.4.18
-
Component/s: Diagnostics, Sharding
-
Server Programmability
-
ALL
-
Security 2019-02-11, Security 2019-02-25, Security 2019-03-11, Security 2019-03-25, Security 2019-04-08, Security 2019-04-22, Security 2019-05-06, Security 2019-05-20, Security 2019-06-03, Security 2019-07-01, Security 2019-09-09, Security 2019-09-23, Security 2019-10-07, Security 2019-10-21, Security 2019-11-04
Hi there,
We're using a custom application to collect and store the slow queries on our MongoDB deployments. We're using the `appName` to identify the applications making slow queries.
We're noticing missing `appName` on some queries. We did many tests on our side to isolate and replicate the issue :
- That's not query specific : the same query, coming from the same application, can be reported with and without the query
- On this application, we're 100% sure the `appName` is set
- The issue is not coming from our application : the `appName` is missing on the profiler too (I can share the profiler output privately)
We didn't find any related issue on the changelogs.
We're noticing the issue from different drivers : `globalsign/mgo`, official NodeJS and official PHP.
Can you tell us if we're missing something, or is there an issue on mongod side ? FYI, we noticed the issue only on our sharded clusters. As our replica set are less used, and less slow queries are reported on them, we don't know if there is a similar problem or not.
Thanks,
Anthony
- depends on
-
SERVER-43576 DBClientRS does not propagate applicationName
- Closed
- is related to
-
SERVER-45141 Make a test suite which always provides appName and verifies appname is always present
- Closed
-
SERVER-45142 Provide a failPoint which causes a lack of appName to cause process termination
- Closed