Attention all techies! ActiveCampaign just released a blog post on how they reduced costs and improved observability with Loki, and boy, oh boy, is it exciting! ActiveCampaign is known for its all-in-one platform for customer experience automation, but now they’re turning heads with their implementation of Loki, a log aggregation system. The implementation of Loki has not only saved them a ton of money, but it has also made it easier for them to spot and troubleshoot issues in real time. Through their use of Grafana, they’ve been able to create visualizations and dashboards that have made the entire process more streamlined. So, if you’re looking for a solution to simplify your log aggregation system, be sure to check out ActiveCampaign’s blog post on how they used Loki. Happy logging!
Excerpt from the main article:
ActiveCampaign Reducing Costs and Improving Observability With Loki George Graham, Shawn Saavedra and Gladson George all contributed to this piece. As one of the 3 pillars of Observability, logs help engineers understand applications, troubleshoot anomalies and deliver quality products to customers. ActiveCampaign produces large volumes of logs and has historically maintained multiple fragmented ELK (Elasticsearch, Logstash, and Kibana) implementations across different teams and AWS accounts. Each development team was responsible for the management of their own ELK stack, which led to a wide variance of logging standards, governance, and a limited ability for correlation across ActiveCampaign platforms. This proved challenging for a few reasons. ELK is expensive at scale, requiring pre-provisioned Elasticsearch storage at a rate of $0.30/GB. Accounting for current and estimated growth, ELK datastores were forecast to grow and cost several 10s of thousands of dollars per month. In addition, log-based alerting is not an option in the
Reducing Costs and Improving Observability With Loki – ActiveCampaign was originally published on ActiveCampaign
