Operations | Monitoring | ITSM | DevOps | Cloud

Node.js was introduced over 20 years ago and remains a popular choice for web application teams with over 30 million users. Sites such as Netflix, PayPal, and Uber continue to rely on Node.js to build and maintain their applications.

Today at Google Next, Charity Majors demonstrated how to use Honeycomb to find unexpected problems in our generative AI integration. Software components that integrate with AI products like Google’s Gemini are powerful in their ability to surprise us. Nondeterministic behavior means there is no such thing as “fully tested.” Never has there been more of a need for testing in production!

Site reliability engineers (SREs) and security analysts — despite having very different roles — share a lot of the same goals. They both employ proactive monitoring and incident response strategies to identify and address potential issues before they become service impacting. They also both prioritize organizational stability and resilience, aiming to minimize downtime and disruptions.

A few days ago, I was in a meeting with a prospect who was just starting to try out OpenTelemetry. One of the things that they did was to create an observability demo project which contained an HTTP reverse proxy, a web frontend, three microservices, a database, and a message queue. Here’s a rough diagram: Their motivation was to try out OpenTelemetry and see how much effort it took for them to instrument their system.

LogicMonitor’s agentless collection has long provided customers with many benefits for collecting telemetry data directly from network devices. Recently, LogicMonitor added another feature, enabling the discovery of devices/sites and the collection of telemetry data from the Cisco Catalyst Center. Retaining options is essential due to the pros and cons associated with each approach.