We are working to implement RUM agent for application pages performance monitoring.
But, if i am not wrong the RUM agent is sending data from browser to APM server by publicly exposing in internet as below format ,
https://<apm_server_ip>:8200/intake/v2/rum/events
As apm server is hosted private cloud to our company, i believe it can cause a security threat.
If you do not care about authentication and just want to keep the APM endpoint from being exposed you could run a proxy on your application server where you point the RUM agent to which just routes the traffic to the real APM server.
if you want to combine that you could implement a proxy in your application which does the redirect but also checks that the sender is already authenticated in your application.
There might be more but this is what we came up with. We are going with number 3 for now while closely watching the issue above. We have a Java Spring webapp where we created an endpoint /app/apm/route which is secured by Spring Security so only authenticated users can send to it.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.