Operations | Monitoring | ITSM | DevOps | Cloud

It’s been a while since the last update on “What’s New” series, so I will try and keep it short yet informative. Stay tuned for upcoming content on anomaly detection.

When a team, division or organization is assessing a new vendor, there are some basic questions that must be answered. At Coralogix, we look at migrations in a different way. It isn’t about transporting the current state of play into a new vendor, often called a “lift and shift”. These are the basics. There is a whole new level of onboarding and support that doesn’t just replicate value across platforms – it expands it.

It’s 2026, and developers have more tools at their disposal than at any point in the industry’s history: CI/CD platforms are richer; observability stacks are deeper; security, data, and AI tooling have exploded into crowded, competitive ecosystems. And yet, delivery is still slow, incidents are still noisy, workflows are still brittle. The problem is no longer tool scarcity or feature depth. It’s integration debt.

This guide shows you how to implement OpenTelemetry’s auto-instrumentation for complete distributed tracing across your microservices, from initial setup through production optimization and troubleshooting.

OpenTelemetry instrumentation is the foundation of modern microservices observability, but getting it right in production requires more than just enabling auto-instrumentation. This guide covers production-tested OpenTelemetry best practices that help engineering teams achieve reliable distributed tracing, control observability costs, and extract maximum value from their telemetry data.

Organizations are increasingly using agentic AI applications powered by large language models (LLMs) to automate analysis, decision-making, and operational workflows. As these AI agents take on more responsibility, they gain access to internal tools and services and can interact with them in unintended ways.

When to use JavaScript or CSS in frontend projects is a matter of continued debate among many frontend developers. JavaScript is often the default choice for frontend development, as it offers a robust collection of libraries custom-made for creating advanced UI features, such as data-based visualizations or complex animations. But JavaScript also comes with tradeoffs, particularly when it comes to performance, accessibility, and code complexity.

Event-driven systems are great at decoupling services, but they also make incidents harder to untangle. A single user request can turn into dozens (or thousands) of messages, multiple consumers, retries, and delayed acknowledgments. If your tracing only tells you that a message was sent or received, you still have to guess which upstream request produced the message, whether a batch publish fanned out cleanly, and where queue time is accumulating.

Exponential smoothing is a time series forecasting method that uses an exponentially weighted average of past observations to predict future values. In other words, it assigns greater weight to recent observations than to older ones, allowing the forecast to adapt to changing data trends. In this post, we’ll look at the basics of exponential smoothing, including how it works, its types, and how to implement it in Python.

By incorporating observability tools into your stack, you can better understand how your complex infrastructure operates, reduce downtime, and empower developers to identify and fix problems quickly. However, it now takes considerably more work, time, and money to build the best observability tools for your infrastructure and applications. According to a Splunk survey, over half of the firms polled employ eight or more observability tools.