Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

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.

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.

With observIQ’s latest contributions to OpenTelemetry, you can now use free open source tools to easily monitor Cloudflare. The easiest way to use the latest OpenTelemetry tools is with observIQ’s distribution of the OpenTelemetry collector. You can find it here. In this blog, the Cloudflare receiver is configured to monitor logs locally with OTLP– you can use the receiver to ship logs to many popular analysis tools, including Google Cloud, New Relic, OTLP, Grafana, and more.

DevOps teams are used to working with data that is spread out across lots of different systems and environments. In organizations that have achieved tight collaboration with security teams to transition to DevSecOps, this is even more true! Log management is part of how all these teams keep track of information and make vital business decisions. It’s important to take a moment to understand what is meant by log management.

Cyber crimes are expected to cost the world roughly $10.5 trillion per year by 2025, according to Cybersecurity Ventures. And these attacks don’t just cost money. Businesses impacted by these kinds of crimes can expect to experience not only financial losses but also loss of productivity, damage to their reputation, potential legal liabilities and more.

Faced with an important business decision? Do you have the data you need to make it? Odds are, you probably don’t. Or, if the data is captured somewhere, can you count on it being in one place and easily accessible? This is a common issue, easily solved by proper log management. This practice is vital for data-driven businesses, helping you maintain security, troubleshoot operations more quickly and enhance user experience.