Operations | Monitoring | ITSM | DevOps | Cloud

The Apache HTTP Server (httpd) is a widely used, open-source web server application. Because you can easily customize it through modules, it has become the go-to choice of both individuals powering their personal blogs and enterprises running high-traffic websites and web apps. It’s a well-known fact that with high traffic, the performance of Apache web servers can take a hit, experiencing bottlenecks as your traffic scales up, which will lead to delayed responses.

What do an airline, the world’s largest retailer, the French government, Adobe, and NASA’s JPL have in common? They use the Elastic Stack to empower customers, communities, and, even, interplanetary exploration. With the Elastic Stack’s ability to take data from any source and in any format, and then search, analyze, and visualize it in real time, organizations can act quickly to improve customer experience and power critical systems.

Splunk Cloud Architect Paul Davies recently authored and released the GCP Application Template, a blueprint of visualizations, reports, and searches focused on Google Cloud use cases. Many of the reports included in his application require Google Cloud asset inventory data to be periodically generated and sent into Splunk. But HOW exactly do you craft that inventory generation pipeline so you can "light-up" Paul's application dashboards and reports?

There’s an insidious disease increasingly afflicting DevOps teams. It begins innocuously. A team member suggests adding a new logging tool. The senior dev decides to upgrade the tooling. Then it bites. You’re spending more time navigating between windows than writing code. You’re scared to make an upgrade because it might break the toolchain. The disease is tool sprawl.