Operations | Monitoring | ITSM | DevOps | Cloud

Audit logs, or audit trails, answer a simple question: who did what, where and when? So, in this article, we’ll answer our own simple question: How can you use audit logs, and what use cases do audit logs best support?

Log aggregation is the process of consolidating log data from all sources — network nodes, microservices and application components — into a unified centralized repository. It is an important function of the continuous and end-to-end log management process where log aggregation is followed by log analysis, reporting and disposal. In this article, let’s take a look at the process of log aggregation as well as the benefits.

Imagine that a critical incident — a major outage, cyberattack or disaster — occurs out of nowhere in your company. In such a case, you'll try to minimize the damage and get back to normal operations as quickly as possible. But how will you do that? You've no idea how to manage such incidents. This is where incident commanders come in. They're trained professionals who lead the response to critical incidents.

In the world of software engineering, monitoring and logging are two essential processes that help developers keep track of the performance and behavior of their applications. To facilitate this process, several logging formats have been developed over the years, including the Common Event Format (CEF). In this blog post, we will take a closer look at what the Common Event Format is, how it works, and why it is important.

Data analytics refers to the discovery, management and communication of meaningful insights from historical information to drive business processes and improve decision making. The process involves: So, let's take a look at data analytics today, specifically the 4 types you need and what they'll tell you about your organization.

Systems going down because of an unforeseen incident? Got problems with your app or website? Is your audience missing out on products and services because your load times are too slow? Then monitoring and observability (and telemetry) should be of interest to you! In this long article, we’re covering everything! I’ll start with the concepts and how they work.

On their own, enterprise applications and systems are not always straightforward. Writ large, they are complex, integrated environments, full of multiple data formats and structures. You spend a great deal of effort and time to define and maintain diverse data models among these integrated components. A Canonical Data Model helps reduce that burden significantly — by promoting a standard and consistent data model between connecting components. This article describes a few things to get you started.

DORA (the Digital Operational Resilience Act) recently came into force and will soon impact thousands of financial services organisations across the European Union (EU). In this blog, my colleague Clara Lemaire and I share some insights about the requirements of DORA, as well as how Splunk can support financial services organisations on their resilience journey. Let’s explore DORA!

DevOps gained popularity in order to combat siloed workflows, decreased collaboration and a lack of visibility across the software development lifecycle. While establishing a culture of DevOps has helped teams collaborate better and deliver reliable software faster, DevOps teams don’t necessarily have someone specifically dedicated to developing systems that increase site reliability and performance. That’s where a site reliability engineer (SRE) comes into the picture.

The ability to continue business operations for the foreseeable future is a key metric from a financial standpoint. But from a risk management perspective, all dimensions of an organization’s strategic and operational framework must be analyzed in order to… The last part relates to business resilience — and it’s what we’re going to explore here. (This article was written by Joseph Nduhiu. See more of Joseph’s contributions to Splunk Learn.)