Operations | Monitoring | ITSM | DevOps | Cloud

Imagine this: Your IT team has invested in cutting-edge observability tools to keep systems running smoothly. But does that imply you are following observability best practices? As your business grows, so does the flood of logs, traces, and metrics—along with a skyrocketing cloud bill. What started as a way to gain better visibility is now a major expense, and suddenly, you’re asking: Are we paying too much for too little value? This challenge is becoming all too common.

Kentik and ServiceNow are teaming up to bring network intelligence to the ServiceNow AI Platform. This integration enables ServiceNow ITOM customers, even those without deep network expertise, to answer questions about connectivity, performance, and more.

I’m delighted to share that you can now run Redgate Monitor’s data repository on PostgreSQL with TimescaleDB, achieving dramatically improved performance and scalability at reduced cost.

In the world of log management and security analytics, one thing is abundantly clear: data volumes fluctuate. Yet most pricing models haven’t caught up. Traditional ingest-based licensing models force organizations to size their license needs based on a worst-case capacity scenario—the “high-water mark”—whether those spikes are rare and/or expected.

Docker containers isolate application environments, making performance monitoring essential for visibility and stability — especially at scale. To manage production effectively, teams need clear insights into resource usage, bottlenecks, and failure points. This guide covers key Docker metrics, how to collect them, and how to use that data to keep your containerized systems running smoothly.

Fat bills from observability vendors and tons of not-so-insightful telemetry data have turned out to be a very common issue today. This often leaves teams having to explain the lack of clear ROI, despite the growing costs. If you’re using OpenTelemetry to record your observability data, there are some practical methods you can apply to keep those costs from piling up.

Managing infrastructure drift doesn't always start with your code. Changes are often made directly to cloud resources—whether through urgent security hotfixes, manual fixes, or automated optimization and security tools. To ensure your Infrastructure as Code stays fully aligned, env0 now suggests a pull request based on those cloud-side changes, allowing you to easily review, merge, and sync your environments. This enhancement expands drift remediation to cover the full lifecycle.