Operations | Monitoring | ITSM | DevOps | Cloud

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.

Network management is undoubtedly crucial as there is a constant need to pin-point as well as fix the issues quickly whether it’s on premise or on cloud. The more complex and distributed a network becomes, the more alarms or alerts the system generates. Just knowing that something has gone wrong in your network is not enough, you should know the details like why it happened, when it happened, where it started, and what triggered it.

In a previous article, we examined service meshes in detail. Briefly, a service mesh takes care of network functionality for the applications running on your platform. As Kubernetes has matured as a technology, service meshes have become a hot topic, with various products being developed to solve the challenges associated with areas like traffic management, security, and observability. This article will compare three service meshes.

Service desk or IT teams are critical to organisations for ensuring business continuity and service delivery. Hence, it becomes important for IT organizations to use a slew of metrics to measure how efficient their service desk is. With the recent advancement in IT Service Management (ITSM), the reporting capabilities offer multiple KPI metrics that can be measured and monitored. So, with the increase in service desk metrics, it becomes even more difficult to zero down on which metrics to measure.