ELASTIC_APM_ environment variables not available to the Agent when the Laravel config is cached

[arkaitzgarro]

ELASTIC_APM_ environment variables not available to the Agent when the Laravel config is cached

[arkaitzgarro]

Thanks for the investigation @dstepe. We do actually cache the configuration as a part of the deployment process, but never updated the environment variables to be prefixed with ELASTIC_APM_. That can also be the reason we didn't realise about the issue.

[dstepe]

Apologies for not following up on this sooner. When considering the Laravel configuration cache behavior, I don't see how it will be practical to defer library configuration in the way I wanted. This isn't an issue with the Library, and the agent package will continue to support the environment variables to be consistent with other agent implementations. This is simply a consequence of how Laravel configuration caching works.

I'm working on fix which will utilize all of the ELASTIC_APM environment variables in the config.