Case Study: Monoova cut metrics usage and cost up to 50% with Logz.io Open 360
Key results
The challenge
Monoova, an Australian payment services provider, needed a unified interface for managing telemetry data and investigating incidents to reduce mean time to recovery. As a payments business where even minutes of downtime can lead to revenue loss, inconsistent approaches to problem-solving had lengthened MTTR. Its growing Kubernetes metrics footprint also risked driving up observability cost.
The solution
Monoova adopted Logz.io's Open 360 platform, using Kubernetes 360 to monitor and manage its Kubernetes environment and the Data Optimization Hub to prune metrics not linked to any dashboard. The team also uses log management, infrastructure monitoring, and distributed tracing over its OpenTelemetry data.
“There's an amazing ability to get use out of your Open Telemetry data already when you start with Logz.io.”
NTNicholas TanCTO, Monoova
The results, in context
Using the Data Optimization Hub, Monoova reduced its metrics usage by up to 50% by selectively turning off metrics not tied to a dashboard, lowering cost and creating operational headroom. Granular metrics and tracing through Open 360 also let the team pinpoint a payment-ecosystem latency issue immediately rather than through manual investigation.