Onbe case study: How Onbe Manages Over 20 TB of Monthly Logs and Achieved over 1,600% ROI with CtrlB

How Onbe Manages Over 20 TB of Monthly Logs and Achieved over 1,600% ROI with CtrlB

Highlights

  • Onbe's application, infrastructure and WAF telemetry was split across Dynatrace and Azure Monitor, with short retention windows.
  • Onbe retired that stack and consolidated everything into one on-prem, fully air-gapped data lake on CtrlB.
  • Total onboarding time was just two working days.
  • Telemetry moves to long-term cold archive storage and stays fully searchable, not just stored.
  • Onbe gets roughly 1600% better ROI than it did on its previous Dynatrace and Azure Monitor setup.

See it on your own data

The challenge: Fragmented telemetry and limited log retention

Onbe processes payments for thousands of businesses, making the availability and integrity of its payment systems critical. The logs generated by these systems contain sensitive operational and transaction-related information. Onbe needed a way to retain and investigate this data without moving it outside its own infrastructure.

Onbe manages approximately 20 TB of log data every month across its application, infrastructure and Web Application Firewall (WAF) environments. Previously, its telemetry was distributed across Dynatrace and Azure Monitor. This created two challenges:

  • Limited historical visibility: Short retention windows meant logs needed for investigating older incidents were no longer available.
  • Fragmented investigations: Security and engineering teams had to correlate application, infrastructure and WAF logs across different platforms when investigating suspicious activity.

Onbe wanted to consolidate its telemetry, extend log retention and reduce storage costs without compromising data ownership. Its requirements also called for an entirely on-premises and air-gapped deployment.

The solution: A unified data lake for observability and security

CtrlB was deployed within Onbe's environment to provide a centralized platform for long-term telemetry storage, search and analysis. The total onboarding time was just two days.

After months of using CtrlB in production and completing a long list of compliance audits, the infra team now uses the following structure to manage their data:

  • First 30 days: Dynatrace continues to handle recent logs.
  • Beyond 30 days: Historical logs move to CtrlB for long-term retention.
  • Compressed storage: CtrlB applies compression to reduce the storage footprint and associated costs by almost 2X.
  • Unified visibility: Application, infrastructure and WAF logs can be queried together, giving engineering and security teams a consolidated view of their telemetry.

CtrlB also provides SQL-based log querying and its AI Insight Engine to identify error spikes, anomalous traffic and unusual failure patterns.

The entire deployment runs on-premises in an air-gapped environment. No telemetry leaves Onbe's infrastructure.

See it on your own data

The results: 1,600% ROI and better visibility

The new architecture delivered measurable improvements in observability economics and data accessibility.

~1600% ROI within months of launch

Measured against the Dynatrace + Azure Monitor setup that it replaced, Onbe gets roughly 1600% better return on its telemetry spend, with application, infrastructure and WAF telemetry all on CtrlB.

Return on investment

Previous stack
1x
CtrlB
~1600%
Previous stack shown as the 1x baseline. Bars drawn to scale.

Azure Monitor completely replaced

Onbe no longer uses Azure Monitor. CtrlB now handles all long-term log storage requirements.

Long-term retention that stays searchable

Instead of the usual 30 days retention window, Onbe now enjoys a 90 day window with 100% of logs indexed and searchable within less than a second for most queries.

100% on-prem and air-gapped

CtrlB runs entirely on-premises in an air-gapped environment, keeping telemetry within Onbe's infrastructure.

Better economics for enterprise observability

Onbe demonstrates how enterprises can rethink log retention without abandoning their existing observability workflows. By moving historical telemetry to CtrlB, Onbe has reduced storage costs, consolidated access to operational and security data, and achieved significantly better ROI.

CtrlB makes it possible to retain and search historical telemetry without paying the same storage costs as traditional observability platforms.

Run observability and security on one data lake

See how CtrlB can bring your application, infrastructure and security logs onto one data lake, on-prem or in your own cloud.

Talk to our team