Operations | Monitoring | ITSM | DevOps | Cloud

Application Performance Monitoring (APM) refers to the practice of tracking, analyzing, and optimizing the performance and availability of software applications. When it comes to Go (Golang), a language known for its concurrency, speed, and efficiency, APM becomes crucial to ensure that your applications stay fast, reliable, and scalable under real-world loads. APM in Go involves monitoring the runtime behavior, request response times, system resource usage, and error patterns across your application.

Top tips is a weekly column where we highlight what’s trending in the tech world and list ways to explore these trends. This week, we're talking about what it really means to start fresh, stay curious, and make space to be a beginner again—even when your calendar’s packed. If your calendar is crammed with back-to-back meetings, messages that never stop, and deadlines breathing down your neck, you're not alone.

Redux remains a cornerstone of React state management, but developers continue to encounter persistent bugs and new challenges. State mutation errors remain the most common Redux bug, affecting over 70% of Redux applications, while new issues emerge with Redux Toolkit 2.0, TypeScript integration, and React 18/19 compatibility. This comprehensive guide explores the most prevalent Redux debugging challenges and provides practical solutions for modern development.

Following the popularity of our existing GitHub integration, we’ve extended similar capabilities to GitLab users. You can now ingest GitLab events directly into Mezmo Telemetry Pipelines and route them to any destination. This provides a powerful new way to monitor, alert, and react to activity within your GitLab repositories.

Kubernetes provides a wealth of telemetry data from container metrics and application traces to cluster events and logs. OpenTelemetry offers a vendor-neutral, end-to-end solution for collecting and exporting this telemetry in a standardised format.

As organizations migrate their legacy web applications from containerized or server-based deployments to serverless environments, they often run into a critical compatibility challenge. Traditional web frameworks like Flask, Express, or SpringBoot are designed to run on persistent HTTP servers, not event-driven, stateless environments like AWS Lambda. The AWS Lambda Web Adapter bridges this gap by allowing teams to run web server-based applications inside Lambda with minimal changes.

When something goes wrong in a client’s infrastructure, MSPs are expected to fix it—fast. But there’s one area most teams still overlook, and it’s often the first point of failure: DNS. Misconfigured DNS doesn’t always break things immediately. It’s subtle. It lingers. And when it finally causes an outage, broken email, or a security issue, it’s often too late. Here are the DNS misconfigurations MSPs can’t afford to ignore—and what to do about them.