Following installation of OneAgent, your Apache web server must be completely restarted to enable monitoring. To do this correctly, it's important to understand the difference between "partial" and "complete" restarts. In the case of partial restarts, the main Apache process re-reads its configuration files, re-opens its log files, and then restarts its worker processes. OneAgent however, requires a complete Apache web server restart in which all workers and—most importantly—the main Apache process are shut down entirely and then restarted.
See Stopping and Restarting Apache HTTP Server for more information on the different types of available restarts.
How to perform a complete restart
You may be accustomed to restarting Apache by issuing an
apachectl restart command. However, this command only results in a partial Apache restart.
To execute a complete Apache restart and enable deep monitoring with Dynatrace OneAgent, you need to first invoke a complete shutdown using the
apachectl stop command. Only following this step can you restart the server using
apachectl start .
It's fine to use
service apache2 restart on Ubuntu systems. Note however that whatever commands you use, you'll likely need superuser rights (sudo).
On Windows, you can either use the built-in Windows Service Management or Apache Service Monitor (
httpd.exe) to restart Apache services. Restarting the Apache service with Windows Service Management guarantees the complete restart. With
httpd.exe, you may be accustomed to restarting Apache by issuing a
httpd.exe -k restart -n "Apache2.4" command. However, this command only results in a partial Apache restart.
To execute a complete Apache restart and enable deep monitoring with OneAgent, you need to first invoke a complete shutdown using the
httpd.exe -k stop -n "Apache2.4" command. Only following this step can you restart the server using
httpd.exe -k start -n "Apache2.4".