Currently, agent implementations have a hardcoded list of Elasticsearch request paths patterns that define when to capture a request body, e.g.
We use the APM agent to capture requests that Kibana server sends to Elasticsearch and would like to automatically generate Rally benchmarks from these request traces. The problem that we are facing is that request bodies are only captured for a subset of requests against Elasticsearch (basically searches, but also not all of them, e.g. PIT is missing). Instead, we'd like to be able to customize for which requests the agent captures request bodies. We don't mind if this creates a lot of data because we'd only use this feature in a setup we have tight control over.
This also very loosely relates to elastic/apm-agent-nodejs#2019 as the request bodies would be captured in context.db.statement.
Currently, agent implementations have a hardcoded list of Elasticsearch request paths patterns that define when to capture a request body, e.g.
We use the APM agent to capture requests that Kibana server sends to Elasticsearch and would like to automatically generate Rally benchmarks from these request traces. The problem that we are facing is that request bodies are only captured for a subset of requests against Elasticsearch (basically searches, but also not all of them, e.g. PIT is missing). Instead, we'd like to be able to customize for which requests the agent captures request bodies. We don't mind if this creates a lot of data because we'd only use this feature in a setup we have tight control over.
This also very loosely relates to elastic/apm-agent-nodejs#2019 as the request bodies would be captured in
context.db.statement.