Describe the bug
While testing https://github.com/elastic/apm-server/issues/10467 an issue was discovered in which the go agent was ignoring the capture_headers option. The test was carried out with a test application and and Elastic Agent managed APM Server (without fleet).
Create an EA managed APM Server (you might want to reduce the agent config cache)
Run the example app: ELASTIC_APM_LOG_FILE=out.log ELASTIC_APM_LOG_LEVEL=debug ELASTIC_APM_SERVER_URL=<apm_server_url> ELASTIC_APM_SECRET_TOKEN=<token> go run main.go
Send a request to localhost:8080
Make sure the agent is working and you can see APM data in kibana
Update the agent settings in kibana to enable capture headers
Send a request to localhost:8080
stop the example app
open out.log and look at the warning:
{"level":"debug","message":"central config update: updated capture_body to all"}
{"level":"warning","message":"central config failure: unsupported config: capture_headers"}
{"level":"debug","message":"central config update: updated log_level to debug"}
Expected behavior
A clear and concise description of what you expected to happen.
Describe the bug While testing https://github.com/elastic/apm-server/issues/10467 an issue was discovered in which the go agent was ignoring the capture_headers option. The test was carried out with a test application and and Elastic Agent managed APM Server (without fleet).
app:
To Reproduce Steps to reproduce the behavior:
ELASTIC_APM_LOG_FILE=out.log ELASTIC_APM_LOG_LEVEL=debug ELASTIC_APM_SERVER_URL=<apm_server_url> ELASTIC_APM_SECRET_TOKEN=<token> go run main.go
Expected behavior A clear and concise description of what you expected to happen.
No warning