Typically users don't trace the web server itself. There's no established pattern for "middleware" to trace requests inside of Apache web server. Apache would need to add traceparent headers to be included in a distributed trace.
Once RUM is implemented, you'll see the entire distributed trace from the user's browser, through your web server, and into the traces you already have from Zope. Then you can see if there are latency issues between the user's request and your Zope application (which might be web server issues).
We do have a filebeat module which allows for easy collection of Apache logs.
There is a quite bit challenge in implementing Angular < 1.2 with RUM. The Javascript code provided by Elastic APM - RUM does have a problem in running.
I don't think we have an easy way to trace the webserver, unfortunately. We rely on having both sides of the webserver traced, and then we get the webserver (the gap between the traces) for free.
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.