Support record collection name in db.bind_vars for java mongodb-agent

[suninuni]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

db.bind_vars is correctly show but not record the collection name, which is may be useful.

Another questions is why only the mongodb-3.x and mongodb-4.x use db.bind_vars? I think they should be db.statement according to the development guide. https://skywalking.apache.org/docs/skywalking-java/latest/en/setup/service-agent/java-agent/java-plugin-development-guide/#tag-keys-dbstatement-and-dbtype

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[wu-sheng]

Please use GitHub correctly. Discussion is the place to discuss uncertain features.

[wu-sheng]

I think db.statement or db.bind_vars is determined by the plugin. db.statement is only required when the statement should be sampled according to slow threshold. In your case, it is very clear, it is not a statement, it is just a collection of parameters in MongoDB operation.
So, I believe the current tag use is correct.

[wu-sheng]

collection operation actually is the endpoint name, a.k.a. span's operation name.

[suninuni]

So it' seems there is no existed tag for the collection name.

For example, there is a mongodb statement db.getSiblingDB("test").account.find({id:""}), the span's endpoint whill be MongoDB/FindOperation, db.bind_vars will be {id:""}, and there should be a new tag to record the collection name account and the database name test?

[wu-sheng]

I was thinking to add a db.table as we may analyze table-based metrics. But, after evaluating apache/shardingsphere#8208, it seems the performance is not enough.
So, we canceled that plan. If you are willing to contribute, I think we could accept this new tag.