Operations | Monitoring | ITSM | DevOps | Cloud

As software teams race to integrate AI into their development workflows, we need to ask ourselves: are AI-powered tools actually making software better? The latest research from DORA confirms what many engineers have long suspected, and what we at Honeycomb have said for a long time: AI tools don’t magically lead to better software. In fact, without careful implementation, AI can introduce a whole slew of challenges, including decreased productivity and unreliable code.

Telecommunications (telecom) is the foundation of modern connectivity, enabling the transmission of voice, data, and multimedia across vast distances. Telecom companies build, operate, and maintain extensive infrastructure that supports everything from mobile networks and broadband internet to enterprise communication systems. This infrastructure includes fiber-optic cables, cell towers, satellite systems, and data centers that work together to deliver seamless connectivity.

Playwright isn’t a testing framework. Sure it’s got assertions, scripted behaviors, even controls over environments. But testing isn’t Playwright’s only purpose. Playwright is an automation tool. It can carry out any browser-based action consistently, and carry out instructions robustly. Locators for buttons and other elements aren’t visual or CSS class-based, but based on ARIA role, and even small styling changes won’t make the scripted action fail.

Monitoring and observability are critical for ensuring system performance, stability, and reliability. New Relic and Zabbix are two widely used monitoring solutions, each catering to different needs. While Zabbix focuses on comprehensive infrastructure monitoring, New Relic excels in application performance monitoring (APM) and full-stack observability.

Healthchecks can now notify you about a failing check by opening a new issue in your chosen GitHub repository. Here is an example of how the GitHub issue might look: The technical side of creating a new issue is straightforward: GitHub has an API call for creating an issue. You make an HTTP POST request with an access token in a request header and the issue title, body, and labels in the request body. However, where do we get the access token from? The API call accepts three types of access tokens.

Need to bring back archived files in SharePoint? This step-by-step guide walks you through restoring all previously archived files in a SharePoint Online site using Squirrel, ensuring a seamless and efficient recovery process.

Managing SharePoint storage can be challenging as data grows over time. Archiving full sites ensures compliance, reduces costs, and keeps your SharePoint environment efficient without losing access to important files.

Like finicky eaters, customers look for a smooth, satisfying meal with each course fulfilling their needs. A slow server, a confused menu, or a process hiccup all take away from the entire experience. Companies require a strong tool, such as digital experience monitoring (DEM), to not only spot the problems but also to promptly fix them. Similar to the kitchen manager eagerly acquiring ingredients and presenting the food, the site owner makes sure everything goes well without a hitch.

Imagine you have one more special thing to monitor. While our Icinga 2 can observe infrastructure of almost any size, it still needs a plugin for each kind of check. Unfortunately not every command meets the monitoring plugin API: exit code 0-3 (ok, warning, critical, unknown), performance data, etc. E.g. often programs exit with 1 in case of a fatal error, which is considered just a warning by Icinga.