Halodoc’s journey from EFK to New Relic log management

Halodoc, a prominent digital healthcare platform in Indonesia, transitioned from using the EFK stack (Elasticsearch, FluentBit, Kibana) to New Relic log management to address the operational challenges posed by their previous log handling system. This strategic shift was driven by the need for more efficient and centralized log management, enhanced by New Relic's seamless integration with Halodoc's existing tools and its more advanced features for error debugging, log filtering, and customizable dashboards. The migration involved moving from a sidecar model to a centralized Kubernetes DaemonSet approach, which streamlined the logging process and reduced performance overheads on application containers. The transition also included the implementation of specific FluentBit configurations to optimize log data ingestion, reduce non-essential log capture, and improve multiline log handling, ultimately reducing data ingestion from 2TB/day to 550GB/day. This change significantly improved the efficiency and reliability of Halodoc's logging system, enabling engineers to debug more effectively and maintain high application performance in the fast-paced digital healthcare environment.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.