Automatic desentization of mongo query into the probe

[VoxValue]

trafficstars

Hi I used Appmetrics for monitoring a lot a mongo requests and it works fine. A great thanks. I will face to some data privacy issues into the log, due to the capture of effective query into the log to be externalized (to elasticsearch / kibana for my part). Have i a way to automatically desensitize / filter the requests 'inside the probe', not after their capture and before to externalize the correspondind data. Thanks in advance Fred

[tobespc]

@Fred2MTL There isn't a way to automatically desensitize the data at the moment but that is certainly a feature we could consider. What sort of data are you wanting to filter?

[VoxValue]

@tobespc Sorry for the delay. For example, I want to desensitize database id, user name/password, etc. I see that as a pattern to be defined by the database developper, then applied inside the probe (automatically) ou prior to externalize the log, ie. just after catching the event (manually). Mongoose have the marker 'selected' into schema declaration, unallowing the corresponding attribute to be put into a request answer. I don't know if it is a similar marker into API of mongo driver.

[NikCanvin]

This feature is a great idea.. does anybody else out there want the same thing? (we need a way for the appmetrics community to vote on new features)