jackshirazi

note the reason we didn't see this before 1.28 was prior to 1.27 we shaded the agent dependencies so they were actually different package names

I succeeded in implementing an integration test with a dockerized container, here https://github.com/jackshirazi/apm-agent-java/tree/test-for-2373 under integration-tests/spring-boot-2-6-2. Not yet added the assertion that fails but everything else is there

Hi @tobiasstadler, could you give a little detail on why this feature addition is useful? We're more focused on enhancing our support of OpenTelemetry so that eventually that provides the...

Thanks. Couple of things. We think that if the transaction api is used to set the remote address, then that should take precedence over any discovered address - even if...

Is anyone still after this ... and if so, would you be willing to do a [community plugin](https://www.elastic.co/guide/en/apm/agent/java/current/community-plugins.html) - see an [example here](https://github.com/elastic/apm-agent-java-plugin-example)?

As there is a suggested alternative, no one currently pushing for this, no appetite for implementing as a community plugin and no prioritization within Elastic, I'll close this now. But...

I think the right time period would be per minute? Or would we just send cumulative stats? - bytes sent in the last time period - max queue size (of...

On windows (everything running on Windows) the attach from fleet failed ``` 13:24:09.785 elastic_agent.apm_server [elastic_agent.apm_server][error] Failed to download requested agent version 1.27.1, please double-check your --download-agent-version setting. 13:24:09.824 elastic_agent.apm_server [elastic_agent.apm_server][error]...

It seems to me the best option is to always use the JVM that the target service is running, to run the attacher

I think your non-continuous one sounds right. I feel like if I was designing this from scratch I would have 1. server process running as root that continuously scans for...