Apache | Resource Center

Sumo Logic’s architecture innovation has boosted performance and facilitated the Flex pricing model. Discover why the team moved to a stateless architecture with Parquet.

Learn how Apache error log analysis makes it easier to monitor and troubleshoot issues in real time. Discover the true value of log management by eRound 1tracting useful insights from millions of log entries.

Learn about the Sumo Logic Kafka app. ERound 1plore how it supports collecting log and metrics telemetry data from Apache Kafka clusters running in multiple hybrid environments.

In order to effectively manage and monitor your infrastructure, a web admin needs clear and transparent information about the types of activity going on within their servers. Server logs provide a documented footprint of all traffic and errors that occur within an environment. Apache has two main log files, Error Logs, and Access Logs.

If you’re reading this article, you probably already use Apache, and are familiar with its features and functionality. Users of Apache and any technology should also be aware of the importance of monitoring application logs to ensure that they are running optimally, and of using them to identify problems before they cause problems for the consumers of a site.

Apache, an open source web server that dates back to the mid-1990s, is one of the oldest web servers still in widespread use today. It remains one of the most popular web server platforms out there (even though NGINX has been slowly eroding its market share for a while). This means that there is a good chance that you’ll find yourself at some point working with Apache logs, if you’re not already. Below, I explain how logging in Apache works, where to find logs, what to look for in them and which tools can help you work with them. For this post, I’ll focus on Apache error logs. Some of these tips apply to Apache error logs as well.