Operations | Monitoring | ITSM | DevOps | Cloud

On this day in 1889, William Gray patented the first coin operated telephone with the first model installed at the Hartford Bank in Connecticut.

Recently, my colleagues Pete Di Stefano, Ashley Adams, and I hosted a webcast on the topic of capacity planning and optimization. You can listen/watch it here, it was a really fun conversation. As part of the discussion, we talked about the need to measure the right things to get the correct outcome. Keep in mind my oft-repeated mantra: monitoring is simply the collection of data. You need a robust, mature tool to add context, which transforms those metrics into information.

When the Citrix architecture moved from v6 to v7, one of the main components that was introduced in the v7 architecture was the Citrix Delivery Controller (CDC). A Citrix Delivery Controller is a server-side component that is responsible for managing user access and brokering (enabling application and desktop access) and optimizing connections. Each site will have one or more delivery controllers.

Within the world of robotics and automation one of the most recurring needs is that of capturing and visualizing real-time data from hardware components such as sensors and actuators, which provide insights into how a system is behaving overall and helps diagnose any potential issues that might arise overtime.

Welcome to Part 1 of our multipart series on Distributed Tracing for Full Stack Developers. In this series, we’ll be learning the ins-and-outs of distributed tracing and how it can assist you in monitoring the increasingly complex requirements of full stack applications.

Troubleshooting production issues with virtual machines (VMs) can be complex and often requires correlating multiple data points and signals across infrastructure and application metrics, as well as raw logs. When your end users are experiencing latency, downtime, or errors, switching between different tools and UIs to perform a root cause analysis can slow your developers down.