Operations | Monitoring | ITSM | DevOps | Cloud

Last week, an article from SiliconAngle came out detailing the challenges facing cybersecurity professionals. Companies are in desperate need of solutions to deal with cloud-native applications that exist in fast-paced environments. The security and IT teams monitoring these applications need scalable and flexible solutions that drive actionable insights. That’s why we built Cribl Stream.

When a startup is in its very early stages, rapid iteration and dynamism are at the top of its priorities. The ability to do so, while maintaining a stable and high-quality product, is a big challenge facing the R&D group. We want to release features as quickly as possible, but this rapid velocity cane cause conflicts when writing in-depth, comprehensive tests.

I always tell people "Observability is not logs, metrics, and traces! Observability is empowering your team to ask questions." That's very aspirational and sounds good, but it's not at all clear. I now have a self-contained story that perfectly explains it!

The rolling thunder of cybersecurity warnings has built to a crescendo this year. According to HelpNetSecurity, cybercriminals launched over 9.75 million DDoS attacks in 2022. The Cloudflare Attack Trends 2022 Q1 Report published yesterday shows an alarming increase in application-layer DDoS attacks. And our own Doug Madory has been sharing analysis on the impact of cyberattacks, too.

AWS Lambda is a compute service that lets you run code on high-availability infrastructure without any server provisioning. You can perform tasks such as maintenance of servers and operating systems, capacity provisioning, automatic scaling, and code logging and monitoring. When using AWS Lambda, you are just responsible for your code. Lambda manages the resources needed to run your code, like CPU, network infrastructure, and memory.

I was intrigued by two recent IoT related survey and reports. They emphasize use cases about efficiencies and return on investments but, surprisingly, there is no mention of people-safety nor productivity. I think it is imperative to place people at the heart of the IoT universe. Today, people related use cases have been greatly understated. We will be doing a great injustice if we continue to ignore the human angle.

Debugging JavaScript is an inevitable part of web development, and not the nicest one. Debugging jobs always seem to pop up when you’re already buried under piles of work, and a teammate pings you about an issue that was overlooked in testing and has been causing frustrations since your last release. That’s why it helps to be prepared for that eventuality, and equipped with the developer tools to help you debug faster.

In 2020, we started an internal project to price our data center systems to understand what they might cost to run in the AWS or Azure cloud environments. We initially used some of the online pricing tools available from these vendors, but they were slow and difficult to use in bulk. You can find the public cloud tools here: AWS and Azure. We were forced to add individual systems one at a time and pick options for each because of the nature of these tools.

As most developers know, alert-fatigue is real, and the last thing you want is another feed of notifications. Read on to learn how the new Alert Details view helps you filter out notifications for Issue Alerts you don’t care about, and how it can help you focus on the ones that do. When you get started with Sentry, you’ll likely create an Alert for every Issue.

Before we dive into the Collector, let’s cover the components that make up the OpenTelemetry project. If you missed it, our post What is OpenTelemetry gives a high level introduction to OpenTelemetry and the key components of OpenTelemetry project: The OpenTelemetry collector is optional when using a SaaS service like Scout. Even so, knowing what the Collector can do and when to use it is helpful to understand.