Telegraf Plugins used:
If you have your InfluxDB credentials configured in the CLI, you can install this template with:
One of the reasons why web server monitoring is so important is because it allows you to unlock far faster troubleshooting than ever before. You'll know more than just what is happening — you'll know why it's happening, all so that you can make the best and most informed choices possible moving forward.
You'll also have total visibility into your entire environment, including Windows and Linux environments, so you can quickly isolate the root cause of any web server issues you're experiencing.
All of this comes together into what is ultimately the most important benefit of all: you're able to deliver optimal performance on your webpages through proactive monitoring of your Apache and Postgres servers. This also helps enormously when it comes to delivering exceptional experiences to your users at the exact same time.
Why Apache & Postgres monitoring?
Monitoring both the uptime and performance of your Apache web server, and the supporting Postgres server, will help you easily discover underutilized servers so that you can maximize the use of your assets moving forward.
Likewise, this will also allow you to get notifications on high CPU utilization, runaway processes, and other elements that ultimately impact the performance of your environment in a negative way.
Web Server Monitoring (Apache & PostgreSQL) Dashboard
How to Use the Apache & Postgres Monitoring InfluxDB Template
Provided that you have your InfluxDB credentials configured in the CLI, you can install the Apache and Postgres Monitoring Template directly from GitHub using the command below, or from the Quick Install on the left side of this page.
influx apply -u https://raw.githubusercontent.com/influxdata/community-templates/master/apache_postgresql/website_template.yml
Once installed, this template can be used to monitor any website running on Apache HTTPd and PostgreSQL. Note that you might need to customize the input configuration to better serve your needs, including by specifying a new input value. All of this will depend on how your organization is currently running its Apache server. To find out more about collecting information from your Apache server, or to get resource data from your Linux hosts running Telegraf, consult the instructions at the following link.
Key Apache & Postgres metrics to monitor
Some of the key Apache and Postgres metrics that you can proactively collect using this template include ones like:
- Server Load
- CPU Usage
- Disk Usage
- DB Rows Queried Per Second
Note, however, that many of the metrics you choose will ultimately depend on what you're trying to accomplish. If you were specifically trying to monitor DB load, for example, you would want to use DB rows queried per second, table space sizes and others in Postgres. Likewise, the metrics you choose for general website stats in Apache will obviously vary from ones you would use if you were trying to weed out attempted attacks or exploits.