Operations | Monitoring | ITSM | DevOps | Cloud

For so many, the unknown sucks. Knowing or knowing what to expect is best. Why? Because it puts us at ease, and peace and gives us a calm sense of knowing without having experienced it yet. That’s part of my mission here at Cribl. I talk to a lot of people and the one consistent part of these conversations is the unknown.

I’ll get right to the point: Not uniting testing and monitoring is costing you expensive engineering time, sales, and customer confidence. Below you’ll find an all too familiar scenario that outlines the problems of traditional testing and monitoring approaches and what the benefits are of a united approach to testing and monitoring through monitoring as code (MaC).

Seeing your website flagged as deceptive by Google or other search engines is enough to spoil anyone's day. You've spent long hours creating a site, only for users to be informed that it is a cybersecurity risk. But what can you do? Should you scrap the whole thing and start again? Today we'll explore why your website has been flagged as deceptive. We'll also look at what you can do to overcome the issue.

Grafana Loki 2.8 is here — and it’s at least 0.1 better than Loki 2.7! Jokes aside, this release includes a number of improvements users will appreciate. In addition to graduating our TSDB index from Experimental to General Availability, we’ve added a number of nifty LogQL features, and we’ve made the Loki deployment and management experience much easier. This also marks the release of Grafana Enterprise Logs (GEL) 1.7.

TL;DR—This is a fundraising post! Yes, even in this economy. Here at Honeycomb, we've always focused more on the problems we help our customers solve rather than playing the meta game of posturing in startup-land—so these fundraising blog posts are usually the least fun to write (and read, probably). But this one is a little different.

Logs record digital actions within your IT system to let you know where errors or unauthorized access attempts originated. However, having only a partial log management plan — or lacking one entirely — can leave you with a mess of unstructured data that doesn’t provide the insights you need. Fortunately, following log management best practices can make tracking your digital actions or modifying your current log management plan a straightforward process.

While many of the popular tools for observability in software are open source, one thing they lack is open design. Most of these solutions, from Nagios to Prometheus, started as a product with an opinionated design, which happened to work well for many people. These became the de facto standards. That position of de facto standard is what every open-source project and every commercial product tries to be.

As a company born in the Amazon Web Services (AWS) cloud, we understand that operating at cloud scale requires balancing security, compliance, and operational safety with your commitment to innovation, speed, and agility. From cost optimization at scale to operational resiliency to application modernization, we know you’re facing various challenges and need reliable solutions.

Everything you need to know about creating a log management program Businesses create, collect and have access to more data than ever before. Some of this log data, the record of events that occur in your digital spaces, can help DevOps and security teams assess the performance and reliability of their systems, evaluate weaknesses and troubleshoot any issues that may be occurring.