Operations | Monitoring | ITSM | DevOps | Cloud

The digitalization of the end user experience is leading to increasingly rapid changes for both customers and business owners alike. Customers demand and depend on fast, reliable web services whether for informational purposes or to conduct e-commerce transactions. That’s why regardless of the device that is used, slow digital experiences aren’t easily forgiven. If they happen often enough, they will reflect poorly on your brand and will eventually impact your bottom line.

KPIs and Metrics are Essential Transformation Yardsticks—But So Is Experience. Although many IT leaders launch into projects with set goals, there’s no telling what sort of unexpected consequences will emerge. In episode 4 of The Change Makers podcast, you’ll see how you can plan and predict certain benefits, but several successful business outcomes arrive serendipitously. Take Lucy Hallam, Service Desk Manager at Croydon Health Services NHS Trust.

First, welcome to the new security resource center for N-able. We’re excited to have an area where we can share security-related information with our partners. I’m Dave MacKinnon, chief security officer for N-able, and my role, simply put, is to ensure that we keep our organization, our partners, and their customers’ data safe.

A common cliché in cybersecurity is, it’s not a question of if you get attacked, but when. We witnessed this firsthand when our former parent company was part of a major attack last year. While N-able products weren’t affected, it was difficult to watch friends and colleagues deal with the aftermath of an event of that magnitude.

Here at Grafana Labs, when we’re building integrations for Grafana Cloud, we’re often thinking about how to help users get started on their observability journeys. We like to focus some of our attention on the different technologies you might come across along the way. That way, we can share our tips on the best ways to interact with them while you’re using Grafana products.

The growing importance of technology in business success has forced practically all companies to hire competent, experienced IT professionals. As technology ecosystems become increasingly complex, organizations need a broader range of professionals to focus on tasks like product development, troubleshooting, and customer services. SRE and DevOps have emerged as two of the most critical approaches to success.

In this tutorial, we will go through a working example of a Python application auto-instrumented with OpenTelemetry. To keep things simple, we will create a basic “Hello World” application using Flask, instrument it with OpenTelemetry’s Python client library to generate trace data and send it to an OpenTelemetry Collector. The Collector will then export the trace data to an external distributed tracing analytics tool of our choice.

Last week, we spent some time talking to Gergely Orosz about our thoughts on what happens when an incident is over, and you're looking back on how things went. If you haven't read it already, grab a coffee, get comfortable, and read Gergely's full post Postmortem Best Practices here. But before you do that, here's some bonus material on some of our points.

With the trend towards smaller but more frequent software releases, your binaries and artifacts keep accumulating faster. Our enterprise customers each maintain an average of 20 million unique artifacts, adding 130% more each year. Eventually, a clutter of outdated binaries forms, and fInding the binaries you need becomes unwieldy, difficult, and confusing. Over time, your artifact repository’s performance can suffer from degradation.

The Docker images we provide for both Icinga 2 and Icinga Web 2 already contain quite a number of modules. For example, the Icinga Web 2 image contains all the Web modules developed by us. But one of the main benefits of Icinga is extensibility, so you might want to use more than what is already included. This might be some third-party module or a custom in-house module.