Operations | Monitoring | ITSM | DevOps | Cloud

Five worthy reads is a regular column on five noteworthy items we’ve discovered while researching trending and timeless topics. This week, we explore the concept of XAI, Explainable AI.

During research into client side attacks, we recently observed a skimmer loading on the popular Pakistani fashion website, Khaadi. Khaadi is a global brand including seven stores in the UK and the company boasts over 5.4 million followers on social media. Khaadi have faced negative press recently, after an uproar about inhuman workplace conditions in 2017, and narrowingly avoiding going into administration in 2019.

Setting and tracking key performance indicators based on the right data can help incident management teams reduce the impact of incidents and strengthen the business. But what exactly is the right data? That can be a deceptively tricky question. Incidents are complex, and no two are exactly the same – and your KPIs must reflect this complexity.

First things first, why would you want to collect logs from Palo Alto and send them to a Cloud SIEM? There are many reasons. At its core, having a centralized location with a consistent user experience for managing alerts, notifications, and information coming from the technologies securing your environment can provide value in a lot of ways. In this blog, we’ll discuss how to collect, parse, and analyze Palo Alto logs in Logz.io Cloud SIEM, and how it can help secure your cloud workloads.

If you are using our HTML to PDF conversion API and you are on .NET Framework or .NET Core we have good news! We created simple HttpClient extension method called ConvertToPdfAsync. You can use it as following.

In the first article in this series, we talked about making Kubernetes essential to your DevOps pipeline. We reviewed CI/CD and DevOps and why their relationship with Kubernetes is so powerful. In this article, I’m going to dive into another term in the application development and management mix: GitOps. We’ll cover what GitOps is, how it affects an organization and how it aligns with Kubernetes.

We’re happy to announce a new version of icingabeat, v7.5.2. With this release we ensure the compatibility with Elasticsearch 7.x and Logstash 7.x. Icingabeat is an Elastic Beat that fetches data from the Icinga 2 API and sends it either directly to Elasticsearch or Logstash. To get you data forwarded, icingabeat connects to the Icinga 2 event stream and receives all events happening within Icinga in real time.

I never used to care about the cost of the systems I built. As an engineer, why would I? Especially in the days before the cloud, infrastructure resources were purchased and procured by somebody who worked many levels above me. Even when I first started building on the cloud, I had to submit requests (again, to somebody many levels above me) for my resources.