Kibana version:
8.17.2
Elasticsearch version:
8.17.2
APM Server version:
8.17.2
APM Agent language and version:
dotnet, but not sure the version (added by the attacher)
Browser version:
Chrome 134.0.6998.89
Original install method (e.g. download page, yum, deb, from source, etc.) and version:
Elastic ECK and Helm
Fresh install or upgraded from other version?
Fresh
Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.
I don't think so
Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
I basically followed the steps from the Elastic documentation titled "APM Attacher" (sorry, the forum won't let me post an actual link 
)
The APM attacher seems to install into the cluster properly, and the mutation all seems to work well too, in the sense that I do see the various environment variables added to my .NET pod and at least some of the expected Agent files:
Pod Environment Variables:
Container Contents:
Based on the Elastic documentation titled "Zero code change setup on .NET Core and .NET 5+" (sorry, the forum won't let me post an actual link )
It seems as though I should just need to set the DOTNET_STARTUP_HOOKS environment variable, but that DLL seems to be missing from what was injected into the pod (see ls output above). Am I missing something in terms of the APM Attacher config to inject it properly? My APM Attacher Webhook config looks like this:
webhookConfig:
agents:
dotnet:
environment:
ELASTIC_APM_SERVER_URL: "<see screenshot above; the forum is not letting me post the actual URL>"
ELASTIC_APM_LOG_LEVEL: "Information"
ELASTIC_APM_PROFILING_INFERRED_SPANS_ENABLED: true
I do see that there are different suggestions for a Docker container, but that requires rebuilding the image to include the APM agent, which I can do but would prefer not to if the attacher can inject it.
As a sanity check for the APM agent, I do have a dummy ASP.NET Aspire application (two pods, one for the frontend and one for the API) in the test cluster pointing at that same apm address above (sorry, forum wouldn't let me use the full URL), and those both seem to work properly:
Either way, I'm clearly missing something, and figured someone here might know. Thanks in advance!
Adam