Monitoring the LAMP Stack using Longitude

November 13, 2019 | Ken Leoni

Monitoring the LAMP Stack using Longitude

The LAMP stack is perhaps the most popular web service stack in the marketplace and as such, leveraging of technology to monitor the stack’s inner workings has become an essential prerequisite, enabling IT departments to deliver optimal end user experiences.

Monitoring the LAMP Stack using Longitude
Longitude has evolved over the years from software that originally monitored physical servers, to a platform that covers a broad set of technologies related to the physical and virtual infrastructure, networks, applications, and end user experience.

The term “stack” wasn’t always in IT’s nomenclature, years ago the hardware/software simply could not support it (remember when client/server was in vogue), but now the term is ubiquitous.

“Stack” implies (and rightfully so) the stacking of technologies to work together to deliver a specific functionality, in this case the delivering of web services. I liken the stack to a house of cards, as all it takes is a single component to fail and the whole thing falls down.

What is LAMP?

The LAMP acronym is derived from the stacking of - “L”inux, “A”pache, “M”ySQL, and “P”HP - all working together to host websites. Originally conceived as follows:

  • Linux: The operating system which is the foundation of the stack.

  • Apache: Layered on top of Linux and is the HTTP server responsible for providing website content based on web browser requests.

  • MySQL: The database that is queried with scripting to construct web content. Although typically locally resident, the database can be hosted on dedicated servers for larger deployments.

  • PHP: Sits on top of the stack. It consists of PHP/Perl/Python scripting support and is used to drive the web application.

LAMP has morphed from as term specific to the opensource platform to the more generic web services stack. Microsoft et al. were not about to cede the web services ecosystem to opensource.

Other examples included under the generic LAMP moniker include:

  • WAMP: Windows, Apache, MySQL & PHP

  • WIMP: Windows, IIS, MySQL & PHP

  • WISA: Windows, IIS, SQL &


A big win for IT is the ease at which LAMP can be deployed either leveraging pre-configured templates (i.e. AWS, Azure, and Google Cloud ) or with simple enough scripts (on-premises or cloud), making deployment of a LAMP stack almost child’s play.

Why monitor LAMP?

Why Monitor Lamp?Again, the good news is that LAMP stack is easy to deploy, but you don’t want to “black-box” it.

You really need to understand how all the components of the stack interact with each other and monitor them holistically.

  • A resource problem at the bottom of the LAMP stack (i.e. a disk resource problem or a looping process) will surely impact the web and/or database server.

  • Similarly, if the database fails then the problems will likely manifest themselves as scripting errors.

Once more, the LAMP stack is a house of cards, a problem anywhere in the ecosystem will affect the end user experience. Technology is required to monitor all the moving pieces as it isn’t humanly possible to watch the LAMP stack manually.


The Longitude Architecture and LAMP

Obviously, LAMP can operate anywhere in the IT ecosystem, be it on-premises or cloud. Longitude is equipped to handle on-premises, hybrid, and public cloud deployments.

Before delving into the details of Longitude’s LAMP monitoring capabilities it is probably a good idea to understand Longitude’s architecture. Longitude uses a variety of protocols to pull performance and availability metrics from the LAMP stack.


L - the underlying network and server operating system

  • Linux - SSH

  • Windows and Hyper-V - WMI

  • VMware- vSphere API

  • Network Infrastructure - SNMP

A - the web server

  • Apache - remote script execution

  • IIS - WMI

  • Web content - URL navigation

M - the database server

  • MySQL and SQL Server – JDBC, SSH, and WMI

  • Site specific database query result – JDBC


P - the engine that drives the web content

  • Web content checking - URL navigation

  • Log content - file parsing 


Deployment Options


Longitude is supplied as a download that is deployed on any Windows based device. The prerequisites are simple enough - a Windows OS.

Architecture Longitude


Option I - ideal for many on-premises deployments

Longitude operates from a single console to agentlessly collect, evaluate, alert, and report on LAMP stack issues.


Option II - ideal for larger on-premises and cloud deployments.

The Longitude console leverages remote statistics servers.

Remote Statistics Servers are no-cost lightweight proxies that are deployed throughout the environment to distribute the agentless collection and roll-up of key LAMP metrics/statistics to the Longitude Console. 

Distributed data collection is supported for:

  • Remote data centers and cloud deployments

  • DMZs or through a firewall

  • Workgroups and non-trusted domains


Try Longitude Live Online Demo!

Access our online demo environment, see how to set up IT monitoring, view dashboards, problem events, reports and alerts.  Please log in using the credentials below:

  • Username:   demo
  • Password:    longitude

Leveraging Longitude to monitor LAMP

Longitude’s monitoring capabilities are classified into two categories:

Out-of-the-box monitoring - encompasses Longitude’s rather extensive knowledge base. Deployment is a simple enough point and click (you may need to enter credentials or additional prerequisite detail). You are basically giving Longitude its marching orders and the technology automatically knows what key performance indicators to collect, how often to collect to them, and most importantly how to evaluate them for problems.

Site-specific monitoring – allows IT staff to embed a site-specific knowledge into Longitude. Let’s take the examples of verifying the content or timing of a web-page load or perhaps querying a database result in order to determine application health.

It is wholly impractical to boilerplate the monitoring of any LAMP infrastructure; Longitude readily supports tailoring the technology to meet your site-specific requirements.

▶ Monitoring LAMP with Longitude

L - The foundation layer consists of the server and network infrastructure. Longitude ships with an extensive built-in knowledge base that addresses:


A - The web server sits on top of the operating system. In this instance, you’ll want to use a combination of Longitude’s out-of-box and site-specific monitoring.


M - The database server is on equal footing with the web server as the two interact quite closely with each other. Leveraging a combination of Longitude’s out-of-box and site-specific monitoring provides for extensive monitoring coverage.


P - The scripting layer is atop the stack and ultimately drives the web content. No matter the scripting, be it PHP, Perl, Python, or ASP.NET – in the end it is about looking at the end user experience.


 Service Level Agreements and the LAMP Stack

Having a Service Level Agreement in place as part of a LAMP stack monitoring strategy can go a long way towards identifying the impact of problems by correlating user experience metrics with the underlying IT infrastructure and application metrics.

SLA Dashboard LAMP

 Longitude Summary SLA Dashboard


The Summary SLA dashboard above aggregates the performance of critical IT infrastructure and application components of a LAMP stack. The display pinpoints compliance issues that affect performance and ultimately end user response time.  The dashboard’s visual representation quickly shows - for the defined time period:

  1. Service Availability - What is the overall compliance of the web service being delivered?
    The pie chart shows overall SLA compliance, we clearly have an issue or set of issues that require attention.

  2. Service Availability by Hour - What is the compliance per hour?
    Each vertical bar each represent compliance per hour.  We want to see if there is a particular pattern. For example, is the compliance problem specific to only certain hours of the day?

  3. Service Condition Availability - Which KPIs are out of compliance, how badly, and for how long?

We see here that there is a correlation between web and database response time and health of the SQL infrastructure, giving IT a starting point from which to further diagnose the issue.


Want to learn more?

Stand up Longitude in just minutes and immediately start seeing how your environment is performing, receive proactive alerts, reveal root causes, automate corrective actions, and more...


Comprehensive IT Monitoring

Easy & Affordable: Try Longitude Today

Try our Live Longitude Demonstration.  Access our online demo environment, see how to set up IT monitoring, view dashboards, problem events, reports and alerts.

We value your privacy and will not display or share your email address

Sign Up for the Blog

Heroix will never sell or redistribute your email address.