Last week I was at Monitorama and it was an amazing time! Not only where the talks fantastic, but I also had the opportunity to join Liz Fong-Jones from Honeycomb.io for a podcast with The New Stack to dig a little deeper into some of the topics in monitoring and site reliability engineering.
Pulling in data exposed via API is not one of the most common use cases for ELK Stack users but it is definitely one I’ve come across in the past. Developers wrapping their database services with REST API, for example, might be interested in analyzing this data for business intelligence purposes. Whatever the reason, the ELK Stack offers some easy ways to integrate with this API. One of these methods is the Logstash HTTP poller input plugin.
Kubernetes (K8s) is a prevalent open-source system for automating the deployment, scaling, and management of containerized applications. However, maintaining the service can be difficult and expensive. For that reason, it is easy to find platforms offering Kubernetes as a managed service. In this article, we will analyze three of the most popular services currently available: Google Kubernetes Engine, Azure Kubernetes Service, and Amazon Elastic Container Service for Kubernetes.
The ELK Stack, which traditionally consisted of three main components — Elasticsearch, Logstash and Kibana, has long departed from this composition and can now also be used in conjunction with a fourth element called “Beats” — a family of log shippers for different use cases. It is this departure that has led to the stack being renamed as the Elastic Stack.
As you may very well know, Kibana currently has almost 20 different visualization types to choose from. This gives you a wide array of options to slice and dice your logs and metrics, and yet there are some cases where you might want to go beyond what is provided in these different visualizations and develop your own kind of visualization.
Kibana is the visualization layer of the ELK Stack — the world’s most popular log analysis platform which is comprised of Elasticsearch, Logstash, and Kibana. This tutorial will guide you through some of the basic steps for getting started with Kibana — installing Kibana, defining your first index pattern, and running searches. Examples are provided throughout, as well as tips and best practices.
Distributed tracing has become a de-facto standard for monitoring distributed architectures, helping engineers to pinpoint errors and identify performance bottlenecks. Zipkin is one of the popular open source “tracers” available in the market, and I’m now happy to inform our users that we’ve recently introduced a new integration that allows users to easily ship trace data collected by Zipkin to Logz.io!
Logstash is the “L” in the ELK Stack — the world’s most popular log analysis platform and is responsible for aggregating data from different sources, processing it, and sending it down the pipeline, usually to be directly indexed in Elasticsearch. Logstash can pull from almost any data source using input plugins, apply a wide variety of data transformations and enhancements using filter plugins, and ship the data to a large number of destinations using output plugins.
Logs are unpredictable. Following a production incident, and precisely when you need them the most, logs can suddenly surge and overwhelm your logging infrastructure. To protect Logstash and Elasticsearch against such data bursts, users deploy buffering mechanisms to act as message brokers. Apache Kafka is the most common broker solution deployed together the ELK Stack.
Today I have the immense privilege of sharing the exciting news that we have raised $52M in series D funding led by General Catalyst. I am thrilled that all of our existing investors share our vision and chose to invest further in the company.
