Q&A: Add Apache Web Server to your Unified Monitoring Toolkit

By | | 4 min read

Read more to learn about AppDynamics Unified Monitoring capabilities with Apache Web Server.

Last month Amod Gupta and I presented in a webinar titled “Add Apache Web Server to your Unified Monitoring Toolkit”.

I kicked off the webinar by providing an overview of AppDynamics Unified Monitoring solution and an overview of Apache Server Monitoring solution.

Screen Shot 2015-09-09 at 11.23.17 PM.png

Figure 1. Application Flow Map with Business Transaction starting from an Apache Server

Amod followed me to discuss how the Apache Web Server Agent, a key part of AppDynamics Unified Monitoring Solution, lets enterprises:

  • Discover and check the health of your Apache web server(s)
  • Alert in the case of any anomalies
  • Perform a root cause analysis on issues quickly

Here is the presentation that was used during the webinar.

We had a very interactive sessions after the prepared content was presented. We answered many questions asked during this Q&A, but many of these questions remained unanswered. We responded to all the unanswered questions to the individuals who asked the questions.

Here are the top unanswered questions and answers from the webinar. You can listen to the questions and answered that were covered during the webinar at the on-demand recording of the webinar.

Q: What are the costs for the apache module?

A: Current pricing for Apache Server Monitoring solution is $3,300 per OS instance (Pricing as of September 08, 2015)

You could get volume discount in case you need to purchase more than 10 licenses. In addition, first time customers purchasing 1-10 units can get starter discount.  You can find latest pricing and more details at .

As you may know, AppDynamics offers a freemium pricing model with complete access to AppDynamics product for free for 15 days. After 15 days of free trial period, customers can either purchase the products or keep evaluating the product forever under lite plan.

Q: If we multiple instances of Apache Server running on the server, do we create multiple proxy for each? Or will one proxy support multiple apache instances?

A: One proxy will handle all the instances. Our proxy has built in support for multi-tenancy.

Q: What about reverse-proxy, does it capture any performance metrics?

A: Yes it captures the same performance metrics.

Q: How does the mod_appdynamics work in case of security agents like siteminder agent or Oracle Access Manager agent?

A: It treats calls going out to siteminder as exit calls and shows you the time spent on mod_sm  which translates as the time spent by a request in the authentication module.

Q: At what priority level is the agent loaded? and does it determine the time taken between modules…. example Webserver->Siteminder agent->webserver->mod_ajp->webserver?

A: It shows you the time spent by a request in each module and it shows you the time spent by request in apache. It doesn’t show the time spent between one module and another.

Q: Do we have separate agent and machine agent for Apache web server like java agent?

A: Yes, that’s correct.

Q: Where can we find documentation for apache web server configuration?

A: Documentation for Instrumenting Apache Web Server monitoring can be found at . Additional details on the Apache Web Server monitoring solution can be found at .

Q: Do we require only one license for multiple web server agents running on a single box?

A: Yes, that’s correct.

Q: Are you referring to the Apache HTTP Server that comes with the RedHat Linux? We don’t use the default Apache that comes with the OS instead we installed our own Apache at a separate location on the server. Will AppDynamics detect this apache server?

A: Yes, it will detect and monitor your Apache Server. It doesn’t have to be the web server that comes bundled with any OS. It doesn’t even have to be on RedHat Linux.

Q: Do you support an environment where F5 load balancer is load balancing in front of apache server?

A: Yes, in this case, we’d start monitoring the requests when they hit apache server. We also have an extension for F5 Load Balancer that can help you monitor the metrics from F5 and then you can correlate them with rest of your application environment metrics in AppDynamics.

Q: Is there any business transaction detection we need to configure for the web server agent? Any special instrumentation that’s needed, or should we expect things to work out of the box? I’m using apache 2.4.

A: You should expect things to work out of the box. You can configure Business Transactions naming based on URL segments but by default you should expect to see automatic business transactions being detected and named using the last two segments of the URL.

Q: How much overhead we should expect while having AppDynamics agent on webserver?

A: AppDynamics agent does not add significant overhead. Overhead depends heavily on the hardware and load on the box.


To learn more about the Apache Web Server Monitoring solution, please watch the webinar at the on-demand recording of the webinar .