A large-scale monitoring estate — 400 dashboards, 2,000 monitored objects, 700 alert rules — migrated from Splunk to New Relic incrementally and without disruption. Costs were cut in half. Alerting fatigue was eliminated.
Key Results
The client had built years of monitoring capability on top of Splunk — but the platform had grown into an unmanageable estate. Hundreds of dashboards, many of them redundant or obsolete, hundreds of overlapping alert rules generating constant noise, and a cost structure that was no longer justifiable.
Leadership made the strategic decision to migrate to New Relic. The challenge was not just technical — it required careful evaluation of every dashboard, every alert, and every data pipeline, while ensuring zero degradation in monitoring quality during the transition.
400 dashboards to evaluate for compatibility and relevance before migration
2,000 monitored objects sending data via Splunk forwarders — all needed rerouting
700 alert rules, many overlapping or poorly tuned, causing alerting fatigue
Risk of doubled licensing and infrastructure costs during the overlap period
Long-running queries (10 seconds+) degrading observability platform performance
Strict data security requirements — no tolerance for data leakage or unprivileged access during cutover
RNX team ran the migration as a close, hands-on collaboration with the client's team. Rather than a risky big-bang cutover, we designed a strictly incremental process — application by application, batch by batch — applying a 'data first' policy at every step: no application was migrated until its data flows were confirmed intact in New Relic.
To accelerate the dashboard migration at scale, we built a custom JSON converter that translated Splunk dashboard configurations into New Relic-compatible imports. This eliminated weeks of manual rebuilding and ensured fidelity across the dashboard estate.
Estate analysis
Thorough review of all existing dashboards, ETL/ELT procedures, and data pipelines to map dependencies and identify what to migrate, consolidate, or retire
Custom JSON converter
Built a purpose-specific tool to convert Splunk dashboard configurations into New Relic-compatible JSON imports, dramatically reducing manual rebuild effort
Data ingest migration
Rerouted 2,000 monitored objects from Splunk forwarders to New Relic agents, validated batch by batch with zero data loss tolerance
Incremental cutover
Migration executed in controlled batches with 'data first' policy — each application verified in New Relic before Splunk decommission, preventing any doubling of costs
Alert rule redesign
700 legacy alert rules consolidated to 90 precisely tuned conditions; ML-based alerting implemented to eliminate noise and reduce false positives
Security hardening
Access controls and data routing reviewed at every stage to eliminate any risk of data leakage or unprivileged access during the transition window
The migration completed without any loss of quality of service. The client's monitoring capability came out of the project stronger than it went in — cleaner dashboards, tighter alert rules, faster queries, and a significantly lower cost base. The several-month engagement delivered improvements that will compound for years.
More implementations
A large enterprise had no centralised monitoring, no log management, and no insight into the state of its internal processes. We designed and delivered a full Elasticsearch platform on OpenShift — with 50+ Logstash pipelines, HA clustering across 4 TB of data, and alerting tunable in seconds.
View case studyA mid-market Czech e-commerce company was flying blind during peak traffic. We redesigned their observability stack and cut mean time to detect from 22 minutes to 13.
View case studyYour environment
Let's talk about your observability challenges. Free consultation, no obligations.
Book a Free Consultation