Threat hunting is proactively identifying and thwarting unusual network activity that could indicate an attempted security breach. It's a historically manual activity, making it time-intensive and arduous. It’s no wonder, then, why most organizations don’t have the time, budget, or resources to undertake it effectively…if at all.
Being proactive is one of the key elements of a successful company. We are always seeking ways to help you perform at your best. With this goal in mind, we have been working on enhancements over the past couple of months in our alerting logic. Today, we’re proud to announce another highly anticipated feature from LogDNA: Absence Alerting!
Unicast Flooding Traffic is associated with the learning process of network switches. In fact, with this method, switches identify the MAC addresses of the devices that are accessible by each of their ports, thus constructing a table that will then be used to decide the destination of each frame that arrives at the switch.
The search-first problem-solving approach—meaning “open up the log search tool” (Splunk, ELK, Loggly, SumoLogic, Scalyr, etc)—is a costly and time-consuming operation during which the true source of a problem is rarely pinpointed in short order. Log search tools require work by the user to transform text strings into fields that are ready for statistical analysis.
Let’s set the scene – an IT professional just received a critical alert, notifying him of an urgent matter. Unfortunately, due to a distracting social event, this professional is completely unaware of the notification. Even worse, he receives incident alerts via email, a communication method which doesn’t have the ability to forward the alert to another person if he doesn’t respond within a short time frame. Maybe he should stop attending social events.
Since the beginning of Dashbird, we’ve been conducting user interviews with all the users that take the time to jump on a call with us. One of the most common requests we get is the ability to customise alerts - specifically, what failures you will get notified upon and the ability to set custom alert based on metrics. Today we announce a new part of Dashbird that takes care of that - an incident management platform.
What is log file parsing and how does structuring your logs affect parsing efficiency? Learn the difference between structured and unstructured logs, the basics of the JSON log format, what kind of information you can get when you parse log files, and which tools and utilities to use to perform log file parsing.
Configuration management is an essential process for DevOps teams. It allows engineers to manage dozens, hundreds, or even thousands of machines in a consistent and automated way. While there are many configuration management tools available, three of the most popular are Chef, Puppet, and Ansible. In this post, we’ll explain how these tools work and the unique benefits that they offer.
A few months back, I blogged about my experience arriving at Stackery after code school. Months later, each day is still interesting and challenging and I’m so glad to have decided to pursue serverless as my concentration. I credit my AWS certifications for narrowing my focus enough to lead me to this point. The serverless community puts so much emphasis on exploration and getting started on your work or experiments today that, getting some exposure to AWS, you can get started right away.
Out of the box, Sentry notifies you about crashes in your JavaScript apps and gives you useful tools to help you debug what your app was doing when it broke. If Sentry stopped there, it would still be great and valuable, but it’s possible to maximize your front-end debugging potential with just a few manual optimizations.
