Let’s face it, Kibana and Grafana were naturally meant to go together, right? They’re both great individually, but sparks really start to fly when they work together! Each has their own strengths but combined they cover all the monitoring and troubleshooting use cases you need. So what is keeping these two highly compatible technologies apart? Nothing. Anymore.
Every year, we take time out of our everyday activities to join thousands of techies just like us for the biggest event of the season–AWS re:Invent. For one week at the end of November, industry leaders gather in Las Vegas to learn about new technologies from AWS as well as other partners in the cloud, DevOps, and IT spaces. The new technology, innovative ideas, and smart, ambitious people we have met over the past few years have been priceless for all of us at Logz.io.
Application Performance Monitoring, aka APM, is one of the most common methods used by engineers today to measure the availability, response times and behavior of applications and services. There are a variety of APM solutions in the market but if you’re familiar with the ELK Stack or are a Logz.io user, this article describes using a relatively new open source-based solution — Elastic APM.
Last month, we announced Logz.io Security Analytics — a security app built on top of the ELK Stack, offering out-of-the-box security features such as threat intelligence, correlation, and premade integrations and dashboards. In this article, I’d like to show an example of using both the ELK Stack and Logz.io Security Analytics to secure an AWS environment.
In our last blog post, we learned what the Distributed Denial of Service (DDoS) attack is, and examined the DDoS picture globally. As we walked through some recent and well-known cases, we also surveyed a range of attack types and drilled down to specific examples. In this article, we’ll study the mitigation techniques you’ll need to resist these attacks. You’ll learn: 1. How to avoid becoming a bot; 2. How to prepare your own network for the possibility of an attack and finally; 3.
Addressing compliance requirements for monitoring and logging can be a challenge for any organization no matter how experienced or skilled the people responsible are. Compliance requirements are often not well understood by technical teams and there is not much instruction on how to comply with a compliance program. In this article, we’ll discuss what some of these new compliance programs mean, why they are important, and how you can comply with your logging and monitoring system.
Imagine the following scenario: you’re running a small corporate website, and suddenly, your service becomes unreachable, throwing a 503 (service unavailable) http error at your customers and website visitors. The irritated messages start flooding in to support. Worried, you walk through the usual administrative checks, to make sure it’s not what you think it is. Is the webhost up?
Boston and Tel Aviv, October 24, 2018 — Logz.io, the leader in AI-powered log analysis, releases the first robust security application built on the open source ELK Stack, bringing powerful and scalable security monitoring and analysis directly into the DevOps workflow.
