Join us

How We Improved Our Monitoring Stack With Only a Few Small Changes

How We Improved Our Monitoring Stack With Only a Few Small Changes

The article discusses the process of improving the monitoring system at Riskified.

The team identified pain points and goals, including bottleneck on changes in the monorepo, crashing Prometheus, inability to silence alerts easily, and removing hardcoded secrets in Alertmanager config.

They considered various options to improve the system, including a single Alertmanager, Thanos ruler , and Prometheus-operator. Ultimately, they chose to use Prometheus-operator to split the Alertmanager configuration for each team and use a native Alertmanager configuration file stored in a Kubernetes secret.

They also used Pager Duty to manage alert silences. The team learned that small changes can make a big difference and encourages others to share their experiences to improve and optimize their own monitoring systems.


Let's keep in touch!

Stay updated with my latest posts and news. I share insights, updates, and exclusive content.

Unsubscribe anytime. By subscribing, you share your email with @faun and accept our Terms & Privacy.

Give a Pawfive to this post!


Only registered users can post comments. Please, login or signup.

Start writing about what excites you in tech — connect with developers, grow your voice, and get rewarded.

Join other developers and claim your FAUN.dev() account now!

Avatar

The FAUN

FAUN.dev()

@faun
The FAUN watches over the forest of developers. It roams between Kubernetes clusters, code caves, AI trails, and cloud canopies, gathering the signals that matter and clearing out the noise.
Developer Influence
3k

Influence

302k

Total Hits

3711

Posts