Cyber threats are becoming more sophisticated, and enterprise security teams are under constant pressure to improve and enhance their threat detection and response capabilities. But as security teams expand their security logging tools and capabilities, the burden of monitoring those tools and investigating alerts grows exponentially.

Telemetry data can provide businesses with valuable insights into how their applications and systems are performing. However, leveraging this data optimally can be a challenge due to data quality issues and limited resources. Our recent webinar, "Unlocking Business Performance with Telemetry Data", addresses this challenge.

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.

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.

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.