Life is about making choices: Coke or Pepsi? Beatles or Stones? Mac or PC? In the world of web servers, the choice used to be between open-source Apache and Microsoft’s IIS. Back in 2004, when everybody had lost interest in the World Wide Web, an upstart web server appeared out of nowhere. Now, just over fifteen years later, NGINX has been rapidly rising in popularity and currently has a 30.8% of the webserver market compared to Apache’s 44.1%.
Financial IT Technology Provider tames Microsoft Office 365.
Multinational Bank secures its Office 365 services.
Launched at KubeCon North America last December, Loki is a Prometheus-inspired service that optimizes storage, search, and aggregation while making logs easy to explore natively in Grafana. Loki is designed to work easily both as microservices and as monoliths, and correlates logs and metrics to save users money.
Nginx is an extremely popular open-source web server serving millions of applications around the world. Second only to Apache, Nginx’s owes its popularity as a web server (it can also serve as a reverse proxy, HTTP cache and load balancer) to the way it efficiently serves static content and overall performance.
When we hunt down problems in Icinga setups we ask for logs most of the time. While you get used to sifting through logs and collect some bash magic during the process there’s always the wish for this routine to be easier and especially faster. If you get logfiles from several days where each of the nodes produces millions of logfiles per day, every time you start your grep’s over and over get’s you madder and madder. So I started searching for a solution.