The Apache check tracks requests per second, bytes served, number of worker threads, service uptime, and more.
Follow the instructions below to install and configure this check for an Agent running on a host. For containerized environments, see the Autodiscovery Integration Templates for guidance on applying these instructions.
The Apache check is packaged with the Agent. To start gathering your Apache metrics and logs, you need to:
-
Install the Agent on your Apache servers.
-
Install
mod_status
on your Apache servers and enableExtendedStatus
.
-
Edit the
apache.d/conf.yaml
file in theconf.d/
folder at the root of your Agent's configuration directory to start collecting your Apache metrics and logs. See the sample apache.d/conf.yaml for all available configuration options.
-
Add this configuration block to your
apache.d/conf.yaml
file to start gathering your Apache Metrics:init_config: instances: - apache_status_url: http://example.com/server-status?auto # apache_user: example_user # if apache_status_url needs HTTP basic auth # apache_password: example_password # disable_ssl_validation: true # if you need to disable SSL cert validation, i.e. for self-signed certs
Change the
apache_status_url
parameter value and configure it for your environment. See the sample apache.d/conf.yaml for all available configuration options.
Available for Agent >6.0
-
Collecting logs is disabled by default in the Datadog Agent, you need to enable it in
datadog.yaml
:logs_enabled: true
-
Add this configuration block to your
apache.d/conf.yaml
file to start collecting your Apache Logs:logs: - type: file path: /var/log/apache2/access.log source: apache sourcecategory: http_web_access service: apache - type: file path: /var/log/apache2/error.log source: apache sourcecategory: http_web_access service: apache
Change the
path
andservice
parameter values and configure them for your environment. See the sample apache.d/conf.yaml for all available configuration options.
Run the Agent's status subcommand and look for apache
under the Checks section.
See metadata.csv for a list of metrics provided by this check.
The Apache check does not include any events.
apache.can_connect:
Returns CRITICAL
if the Agent cannot connect to the configured apache_status_url
, otherwise returns OK
.
If you are having issues with your Apache integration, it is mostly like due to the Agent not being able to access your Apache status URL. Try running curl for the apache_status_url
listed in your apache.d/conf.yaml
file (include your login credentials if applicable).
Additional helpful documentation, links, and articles: