Operations | Monitoring | ITSM | DevOps | Cloud

Earlier this month, we shared exciting news with our first placement in the 2022 Gartner® Magic Quadrant™ for Application Performance Monitoring and Observability: we are in the Visionary Quadrant. This research is near to my heart, as I led this research for four years; so, I wanted to reflect on why this is an accurate placement for Logz.io. The Visionary Quadrant is designated for those organizations who are pushing the boundaries of a specific market and technology.

It’s common for most CISOs to lead off a security conversation by comparing what other companies in the industry are spending on cybersecurity and simply matching that. After all, regardless of the results, the CISO can always tell the board of directors they’re following industry guidelines around security budgets. The problem is security outcomes are bad regardless of budgets. It’s not what you spend. It’s the results you get that matter.

We find ourselves submerged in a sea of software applications practically all the time. Their primary job is to make life easier and help us accomplish certain tasks. However, these applications require a lot of data. What’s more, their development requires a systematic approach with proper management of that data — and its related activities. But that’s not a straightforward and simple process. What happens if these applications stop running?

Want to improve your outlook with a splash of RUM? In our pursuit of connecting users to the right data at the right time, we’ve come to see Real User Monitoring as an invaluable tool for understanding the total picture when it comes to your web properties, apps, and cloud footprint. Do you find yourself asking any of these questions?

In Splunk Cloud Platform 8.2.2203, we're continuing to expand on interactivity capabilities and visualizations for Dashboard Studio. We've added the ability to use search results and job metadata as tokens, and pass tokens through drilldowns to other dashboards. There is a new map visualization for cluster maps and UI to match strings for dynamic coloring. And finally, we've included the ability to set a Studio dashboard as your home dashboard.

In part one of our PHP logging blog series, we discussed what logging is and covered the basics of creating logs in PHP applications using the PHP system logger. While the PHP system logger automatically records critical events like errors in code-execution, a more customized logging setup can be achieved using PHP functions. For part two, let's look at the basics of creating custom error logs by calling PHP functions.

Many years ago, I attained my private pilot’s license. This entailed completing a very structured program, similar to how most companies introduce a product to a new user. Let’s be honest, there is a really good reason for this – to avoid the crash and burn. With flight training, it’s literal, while with products it’s a bit more figurative (except when you YOLO something into production–that can cause a crash and burn–and leave for a bad first impression).