Case study
Business Reporting Restored After an Incomplete Migration for a US IT Provider
How SquareShift resolved synchronization delays and configuration gaps left after a Splunk-to-Elastic log migration, building Dead Letter Queues to isolate failed records and restore consistent business reporting.
Book a session →
Client
A US IT services provider that manages a global infrastructure and log management footprint for its customers.
Industry
Technology
Services
Stack
Splunk · Elastic Stack · Dead Letter Queue (DLQ) pipeline pattern
How SquareShift delivered it.
The challenge
After the client moved its log platform from Splunk to Elastic, synchronization delays between local agents and the central cluster put data integrity at risk. Some records reported as lost were actually tangled up with duplicates created by a leftover filter, and no one could tell the two apart with confidence.
What we delivered
SquareShift ran diagnostic analysis on the system logs to separate genuine data loss from the duplicate records caused by the leftover filter configuration, then built Dead Letter Queues to isolate failed records going forward instead of dropping them silently.
The team developed enrichment logic to propagate event headers across multi-line documents for full traceability, and realigned the transformation configs the legacy dashboards depended on. Finishing a log platform migration? See our Elasticsearch migration services.
The outcome
The pipeline now runs on a stabilized Elastic base, with the local-agent-to-cluster lag resolved and consistent business reporting restored for the dashboards that depend on it.
After a migration, the scariest failures are the silent ones — a dropped record nobody notices until a report doesn't add up. Building somewhere for failed records to go, instead of letting them vanish, is what makes a migration trustworthy afterward.
Observability & Reliability Practice Lead, SquareShift


