Operations | Monitoring | ITSM | DevOps | Cloud

Elastic Cloud Serverless provides the fastest way to start and scale security, observability, and search solutions — without managing infrastructure. Today, we are excited to announce the general availability of Elastic Cloud Serverless on Microsoft Azure — now available in the EastUS region. Elastic Cloud Serverless provides the fastest way to start and scale security, observability, and search solutions without managing infrastructure.

SLOs are key for improving user satisfaction, prioritizing engineering projects, and measuring overall performance. Given the important role that SLOs play in determining organizational benchmarks, teams need to ensure that SLO metrics—also called service level indicators (SLIs)—are reported accurately and maintained consistently within an acceptable range.

As we previously reported on April 26, 2025, we had a security incident via an insecure GitHub Action and we have since published a post-incident review. We have confirmed that there has been no code modification, unauthorized access to production systems, exposure of customer data, or access to personal information.

The Prometheus CloudWatch exporter pulls AWS CloudWatch metrics into your Prometheus setup, giving you a unified view of your infrastructure alongside application metrics. If you're already running Prometheus and need visibility into AWS services like EC2, RDS, or Lambda, this exporter handles the integration without forcing you to switch monitoring stacks.

How do you use ArgoCD and a GitHub workflow together with an external CI/CD tool (Jenkins in our case) to trace a specific PR/commit hash code in a GitHub repository that’s external to ArgoCD? The term ‘commit tracing’ comes from Michael Crenshaw – one of the lead developers of Argo.

The more organizations depend on collaboration solutions like Microsoft Teams for productivity, the more IT departments are expected to ensure a seamless experience every time. That demands more than just rapid troubleshooting when issues occur: it requires IT teams to get ahead of problems and keep them from affecting users in the first place. For that, synthetic testing is a must.

Few things hold IT teams back more than a lack of visibility. It’s exponentially harder to solve issues when they originate in parts of the environment you can’t see. That’s one of the big limitations of native tools for monitoring and managing Microsoft Teams. Microsoft Call Quality Dashboard, Admin Center and Service Dashboard, and Meeting Room Pro Dashboard are all constrained to the aspects of Teams that Microsoft controls directly.

An operations team at one of the Asia-Pacific’s largest managed service providers (MSPs) was drowning in their own success. Years of investment in monitoring tools and automation had created comprehensive visibility—and comprehensive chaos. Engineers opened dashboards each morning to find thousands of alerts waiting, with critical incidents buried somewhere inside. The scale of the problem was overwhelming their capacity to respond effectively.