Home / Companies / Coralogix / Blog / October 2026

October 2026 Summaries

2 posts from Coralogix

Filter
Month: Year:
Post Summaries Back to Blog
Coralogix’s migrations team has published benchmark data from more than 300 migrations and onboardings since 2023, covering over 75,000 assets, including a migration of roughly 41,000 alerts. Using an AI-assisted “agentic build” combining large language models, the CX CLI, and reusable migration knowledge, the team reports that conversion and review of 60-widget dashboards now takes under an hour for each measured source, with Splunk reduced from 12 hours to 45 minutes, New Relic from 6 hours to 40 minutes, Datadog from 3 hours to 35 minutes, and Grafana from 1 hour to 35 minutes. The company says elapsed migration time is now more often determined by data onboarding, customer validation, and changing scope than by dashboard conversion, noting a median 3.5-week period to get data flowing and a decline in median dashboard delivery time from 4.0 calendar days in early 2025 to 1.8 days in late 2026. It recommends defining essential dashboards, alerts, and SLOs before decommissioning a prior vendor, validating converted assets before activating alerts, and using migrations as an opportunity to remove unnecessary telemetry and reduce alert fatigue.
Oct 14, 2026 1,396 words in the original blog post.
Coralogix presents a CLI integration that lets coding agents such as Claude investigate production incidents directly using observability data including logs, metrics, traces, real-user monitoring, and infrastructure information. After installation and authentication, users can ask an agent to identify urgent issues or analyze a specific failure, with the agent correlating telemetry, source code, deployments, configuration changes, and historical data to propose a likely root cause. An example describes checkout failures caused by code that assumed an expired promotional coupon would always return a matching campaign, which the agent could identify and potentially address by drafting a pull request. The approach is intended to reduce manual switching among monitoring views and repetitive context-sharing while retaining engineers’ responsibility to review findings, decide on fixes, and escalate issues to other teams when appropriate.
Oct 12, 2026 1,287 words in the original blog post.