CORS Error in APM integration
See original GitHub issueHi!
I’m using @elastic/apm-rum v5.12.0
I’ve spent a lot of time trying to figure out why the CORS integration to send RUM events to elastic doesn’t work for me, and I still really don’t know what’s wrong or missing in the configuration.
The Elastic Cloud Agent Policy is the follow:
I mean, in theory it is allowing communication with any origin, however I get a cors error and I can’t send the events.
Any help please?
Issue Analytics
- State:
- Created a year ago
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Configure CORS | APM Real User Monitoring ... - Elastic
If APM Server is deployed in an origin different than the page's origin, you will need to configure Cross-Origin Resource Sharing (CORS).
Read more >Getting CORS error while connecting to NerdAPI
Hi, I'm facing a CORS error while integrating the new relic's Nerd Graph API. The error details are: Access to XMLHttpRequest at ...
Read more >Troubleshoot CORS errors from API Gateway - AWS
Cross-Origin Resource Sharing (CORS) errors occur when a server doesn't return the HTTP headers required by the CORS standard. To resolve a CORS ......
Read more >Re: CORS error on agentless RUM page with JavaScript tag ...
Apps, Extensions and Customization. Explore the Dynatrace Hub to see how we're open, extensible, and easily integrate with all major cloud platforms and ......
Read more >REST API: Cross-Origin Resource Sharing (CORS) - TechDocs
These multi-origin scenarios include integrations between resources enabling ... Error: Explanation: Corrective Action: Cross-Origin Resource Sharing (CORS) ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @devcorpio,
I opened a support case and the APM engineering team told me that there were many values in the agent policy that were wrong (we suspect that after a version update in the APM agent it was corrupted). They recommended reinstalling the apm fleet policy via this script, and that resolved the issue.
Thank you very much for the support.
Francisco
Hi @reny122010,
Thanks for reaching out.
Would you mind opening a new issue to talk about that there? This issue turned out not to be related to a CORS defect in the end and I would advocate to focus only on one topic here.
Thanks, Alberto