Pre-requisite for monitoring apache server metrics
To monitor apache server, server-status URL should be enabled and access permission should be edited so that the server status url should be accessible from Applications Manager. For more informations Refer here
Enabling extended-status is mandatory for monitoring metrics like Request per second, bytes per second, bytes per request etc..
If the ExtendedStatus is not enabled. Then, follow the below steps to enable the extended status.
- Locate the line starting with ExtendedStatus in apache's httpd.conf file.
- Uncomment the line and set the status "On".
- Then save the file and restart then apache server.
Then try to connect to http://<your.server.name>/server-status and then you should be able to view the new metrics.
New to ADSelfService Plus?
Configure Apache Server running in WAMP server
Introduction: WampServer refers to a software stack for the Microsoft Windows operating system, consisting of the Apache web server, OpenSSL for SSL support, MySQL database and PHP programming language. It comes as a bundled application with all the ...
Troubleshooting - Apache Solr
If the Solr monitor can't be added, then do the following:- Ask the customer to verify whether he can access the particular Solr instance from the machine where he tries to add. Also ask the customer to access the following URLs from the machine, ...
Configure Apache "server-status" page
This error occurs when Client is denied to access "server-status" page due to the missing configuration in Apache Server. Make below changes in httpd.conf file to fix the issue Step 1: Load Status Module Search for the line "LoadModule status_module ...
Monitoring HAProxy - Configuring the HAProxy Stats page
To monitor a HAProxy instance: Open the 'stats' port for collecting the metrics. To enable metrics collection, add the following content at the bottom of the file /etc/haproxy/haproxy.cfg: listen stats :9000 mode http stats enable stats hide-version ...
Update on the Apache Log4j Vulnerability
A high severity vulnerability ( CVE-2021-44228 ) impacting multiple versions of the Apache Log4j2 utility was disclosed publicly on December 9, 2021. The vulnerability impacts Apache Log4j2 versions below 2.15.0. You can find the details of this ...