Capture config per framework/instrumentation

[pavolloffay]

The capture config should be configurable per framework/instrumentation but also globally (

agent-config/config.proto

Line 37 in eb054cd

message DataCapture {

).

For instance I want to disable body capture for servlet but still have it enabled for okhttp client.

[jcchavezs]

While I see the consequences of the use case legit, I'd really like to run some discussion around this as I believe people is not too interested on enable/disable per library but probably per use case (e.g. client, server, remote service, etc). Any thoughts on this @davexroth @mohit-a21 ?

[pavolloffay]

The use case I had in mind was that particular body instrumentation can be problematic so it could be disabled without affecting others.

[davexroth]

Exactly, it will mostly be something used by us in the field if a particular framework causes issues in a customers application.

But as it will be more of an internal config, we may be able to have a different config block such as message Frameworks { map of framework name to options }