Monitoring Apache Web Server. Using the Apache web server (see Figure 1) monitoring model, administrators can keep an eye on the overall health indicators such as the availability of the Apache web server, the data processing ability of the server, the data traffic handled by the server, etc., monitored. Figure 1: Layer model of the Apache web server. The Apache HTTP server commonly known as Apache was officially released in 1995. Nowadays is one of the most popular HTTP servers on the World Wide Web. Many organizations such as Facebook, Cisco, IBM, and of course Apache Software foundation itself uses it. Apache monitoring and alerting – server stats. Monitoring Apache stats like requests per second and worker status is useful in keeping an eye on Apache performance, and indicates how overloaded your web server is. Ideally you will be running Apache on a dedicated instance so you don’t need to worry about contention with other apps.
- How To Monitor Apache Web Server Load And Page Statistics
- Monitoring Apache Web Server Login
- Apache Web Server Versions
Monitoring the status of an Apache Web Server that is hosting your web based application is very useful in the following situations: To determine if your Web Server is accepting requests The number of connected clients, status of client workers, and requests per second. Monitoring host-level metrics from your Apache hosts can help provide a more comprehensive view of your web servers' performance. As you monitor these resources, you may find that eventually you need to either scale up or scale out your servers so that your systems can keep up with the load.
Apache HTTP Server is an open-source, cross-platform web server capable of running on Linux, Unix, or Windows environments. It’s often used in combination with Linux, MySQL, and PHP/Perl/Python. Apache currently powers around 40% of active websites, including those of Cisco and Apple.
Apache offers a modular architecture, making it appropriate for different use cases. Apache’s core functions, including sockets and request protocols, are partitioned away from the other modules. This means developers can create and configure their own modules without worrying about how the new modules will affect core processes.
- Why Is Apache Monitoring Important?
Why Is Apache Monitoring Important?
Apache monitoring is important because the server can easily fall victim to bottlenecks and other performance problems, especially as usage scales up. If your web server is slow, it takes longer for users to have their requests fulfilled—and even small slowdowns can impact your organization’s bottom line.
With Apache monitoring, you can ensure your server is configured to sufficiently handle the current scale of requests. Routine Apache monitoring can alert you to performance issues in real time and help you stop slowdowns before they affect end-user experience.
Monitoring the following Apache server metrics can help businesses keep track of website and application performance. With this information, you can optimize your system and ensure the server keeps up with new demand in the future. Certain best practices can help ensure you’re focusing on useful metrics:
Analyze Processing Time to Catch Poor Performance
How To Monitor Apache Web Server Load And Page Statistics
When processing time is high, you can be sure your performance is suffering as well. Request processing time refers to the amount of time it takes for a request to be successfully completed, down to the microsecond. The rate of request refers to the average number of client requests successfully completed per second. These two metrics fall under the broader category of throughput and latency indicators, which lets you know if your poor server performance is load-related.
Monitor Bytes to See Server Limitations
Monitoring bytes can refer to a few different metrics. Bytes per second refers to the amount of data bytes transferred to and from the server, measured by the second. This metric can tell you how much your network infrastructure can handle and if you need to deploy additional resources. Bytes per request refers to the amount of data bytes sent through the server with each request. Be careful when monitoring total bytes served—this metric refers to how many bytes should have been served and not how many bytes were successfully served, which is a common mistake new admins make.
Track Uptime for Insight into Outages
Uptime is a measure of how long a server is operational, measured in seconds. If your server’s uptime suddenly drops, this most likely means you’re experiencing a small outage or need to restart your server. Because outages have a major impact on end users, it’s critical to keep an eye on uptime.
Measure Load for a Useful Overview
Many of the other performance metrics on this list can be consolidated into a single number called load. Ideally, you want your Apache server metrics to be as granular as possible, but looking at your server’s load number can give you a place to start when it comes to Apache monitoring. In a perfect world, your server’s load is less than your number of processing cores.
Use Memory Metrics to Distribute Resources
Memory usage, as the name suggests, refers to how much memory is currently being used on your server. When memory usage is high, it’s a signal to check your infrastructure. Use this metric to help you evenly distribute network resources.
Measure Efficiency With Multi-Processing Modules
Multi-processing modules (MPM) indicate how efficiently your server is using resources to process user requests and whether or not certain resources are being under- or over-utilized. Unless you’re using Apache on Linux or a Unix-like platform, you’ll only be able to run one MPM at a time, which Apache will choose for you based on what it thinks your environment needs.
There are different kinds of MPMs, but the three most important ones are prefork MPM, worker MPM, and event MPM. On a Unix-like platform, you’ll be able to choose from these three MPMs and more, but make sure you have a full understanding of each one, so you choose the right MPM for your needs. You might end up sticking with the default. To push Apache monitoring even further, you can use MPMs to look into worker utilization.
Monitoring Apache Web Server Login
Add Resources If CPU Utilization Is High
This metric specifically refers to the processing usage of your hardware. If you notice usage rising consistently on your Apache servers, you don’t have enough resources available to handle your number of requests. If you’re using a multi-core system, make sure you’re looking at CPU usage across all cores.
Measure Bandwidth to Understand Latency
Your network’s bandwidth is another important latency and throughput indicator. Since bandwidth directly affects how quickly your website or application can process requests—which in turn directly affects end-user experience—network bandwidth is an important metric to monitor.
View Disk Usage to Ensure Sufficient Space
Apache needs space for logging and some temporary files, so make sure you’ve devoted enough disk space to your server.
Note the Error Rate to Catch Misconfigured Files
Sometimes Apache performance lags, even when resource usage and latency aren’t to blame. If you notice a high per second rate of client errors (like “404 Not Found”) and server errors (like “500 Internal Server Error”), misconfigured files could be the cause of the slowdowns.
Server Monitoring Software for Apache Monitoring
If you want to follow best practices for monitoring Apache server metrics, you should consider choosing an automated tool. SolarWinds® AppOptics™ is an Apache monitoring solution designed to help you streamline the Apache monitoring process and track critical metrics. The SaaS-based solution combines all-purpose application performance monitoring and infrastructure monitoring in one simple tool. AppOptics lets you monitor 2,000 metrics out of the box, including the ones needed to optimize Apache, although you can also configure the tool to monitor custom metrics.
With AppOptics, you can:
• Gain critical visibility into your Apache servers (and related applications)
• Ensure your Apache servers are performing to the best of their ability and keeping up with end-user requests
• Pinpoint the root cause of performance issues
• Reduce downtime
• Scale effectively, which is a prominent pain point with Apache J and j's friday chat.
If you’re looking for additional insight into your Apache server, you should consider a logging solution that records events, requests, responses, and other server actions. AppOptics integrates with SolarWinds Loggly®, so you gain useful visibility into Apache access logs and error logs. With AppOptics and Loggly, it’s easy to follow best practices for monitoring Apache HTTP Server and ensure high levels of performance.
Enterprise Manager Cloud Control enables you to discover Apache HTTP Servers in your environment, and add them for central monitoring and management. This chapter describes how to discover and monitor these Apache HTTP Server targets.
In particular, this chapter covers the following topics:
36.1 Introduction to HTTP Servers
Using Enterprise Manager Cloud Control, you can do the following with Apache HTTP Server targets:
Discover the Apache HTTP Server targets for real-time and historical availability monitoring.
Create or end blackouts to suspend or resume the collection of metric data, respectively.
View a list of metrics, their collection interval, and the last upload for each metric.
Create monitoring templates that can be used as a source for all the future installations, so that they follow a standard, consistent configuration.
Generate availability and event reports.
36.2 Supported Versions of Apache HTTP Server for Discovery and Monitoring
To search for the Apache HTTP Server versions that are supported for discovery and monitoring in Enterprise Manager Cloud Control, follow these steps:
On the My Oracle Support home page, select the Certifications tab.
On the Certifications page, enter the following search criteria in the Certification Search section.
Enter the product name Enterprise Manager Base Platform - OMS in the Product field.
Select the release number 220.127.116.11.0 from the Release list.
In the Certification Results section, expand the Middleware menu to view the certified Apache HTTP Server versions.
36.3 Prerequisites for Discovering and Monitoring Apache HTTP Server
Meet the following prerequisites for discovering Apache HTTP Servers:
The Management Agent must be installed and running on the same host where the Apache HTTP Server is being configured. Remote agent is not supported.
Ensure that the same user/role is used to install the Management Agent and the Apache HTTP Server.
Ensure that you download and install the 18.104.22.168 Fusion Middleware Plug-in for monitoring the Apache HTTP Server. You do not need any other plug-in to import or deploy this target.
36.4 Discovering Apache HTTP Servers
To discover Apache HTTP Server Servers, follow these steps:
In Cloud Control, from Setup menu, select Add Target, then select Add Targets Manually.
On the Add Targets Manually page, select Add Targets Declaratively by Specifying Target Monitoring Properties, and then click Add Host.
From the Target type menu, select Apache HTTP Server. To select the Management Agent, click on the search icon. From the Target Selector dialog box, select the target name, and then click Select.
Click Add Manually to add the Apache HTTP Server target to the host selected.
On the Add: Apache HTTP Server page, provide the target name, the directory location where the
httpd.conffile has been downloaded, and the directory location where the Apache binaries (like the bin folder) are stored. Click OK.
36.5 Monitoring Apache HTTP Servers
After adding the Apache HTTP Server target, it becomes automatically available for monitoring. For this target, only the response metrics and configuration metrics are collected or monitored.
After discovery, to access the Apache HTTP Server targets, from Targets menu, select All targets. From the Refine Search section on the left hand pane, expand Middleware. From the list, select Apache HTTP Server. Click on the target name to view the status of the target.
On the Apache HTTP Server home page, you can view general information about the server, information about the status of the server, the availability, the absolute path to the Apache server binaries, and so on.
36.6 Configuration Management for Apache HTTP Servers
The configuration data for the Apache HTTP server is collected on a daily basis.
To view the configuration data, on the Apache HTTP Server home page, from Apache HTTP Server menu, select Configuration, and then click Last Collected.
Apache Web Server Versions
The following configuration details are collected for Apache HTTP server:
Generic information like server name, listen port, and so on.
General Routing information for WebLogic/WebSphere requests.
Apache Server listen host ports and protocol.
Virtual host information which is used for routing the requests that come to Apache Server to particular host port.
36.7 Troubleshooting Apache HTTP Server Issues
Issue: Response and Configuration Metrics collection for Apache HTTP Server fails
Problem: If the process owner (Apache installation owner) is different from Management Agent user, then Apache HTTP Server target will be discovered, but the response and configuration metrics will not be collected.
Workaround: Ensure that the same user/role is used to install the Management Agent and the Apache HTTP Server.