Hi teams,
I'm trying to integrate Elastic APM server into my app. But sometimes we have this issue when access to my apps.
The singleton APM agent has already been instantiated and can no longer be configured.
Could I add the "checkElastic" for elastic APM? And please show me how can I add.
Regards,
Hi Hung Le,
The error indicates that the APM agent is designed to be instantiated only once, but it's being initialized multiple times, leading to conflicts.
Common Causes:
Multiple initialization attempts within the same application lifecycle.
Asynchronous calls or background tasks creating separate instances.
Plugin or library conflicts.
Here is full documentation available to configure/use it.
https://www.outsystems.com/forge/Component_Documentation.aspx?ProjectId=9080&ProjectName=elastic-apm-for-server
Kind regards,
Sanjay Kushwah
Hi @Hung Le ,
I also encounter same issue, and I'm sure already followed guide how to use it in documentation @Sanjay Kushwah referenced, but it not solve the issue.
In my case, this issue happened in production server which the reactive web apps run in load balance multiple server. I think maybe that's why this issue occurred because it can be called from multiple servers in same time. CMIIW.
I agree with you it should be had function "check connection" to check whether it still has active connection or not before initialize; or I think it should be automatically handled inside code function Initialize Server itself.
Dear developer team @Experts , please help for this issue.
Reference article for solution : https://www.elastic.co/guide/en/apm/agent/dotnet/current/troubleshooting.html