Data / DevOps / Kubernetes / Monitoring

How ShuttleCloud Saves Time and Money by Monitoring with Prometheus

8 Dec 2016 8:57am, by

For API migration and integration platform ShuttleCloud, there was never a ‘switch’ to the open source Prometheus monitoring and alerting toolkit. Having a small team roughly 15 employees, the company originally planned on cycling through monitoring solutions until finding one that clicked. Once it got Prometheus up and running, it never got around to trying another monitoring solution.

On today’s episode of The New Stack Makers podcast, TNS founder Alex Williams spoke with ShuttleCloud software developer Ignacio Pérez Carretero, during KubeCon 2016, to hear more about ShuttleCloud’s experience working with the Prometheus open source in production and their decision to migrate their stack over to Kubernetes.

 

In getting started with Prometheus, ShuttleCloud’s first aim was to better track both internal and external metrics. Though ShuttleCloud’s employee count may be small, its clients are anything but. Carretero noted that ShuttleCloud is the tool behind Gmail’s ability to import addresses from 247 other email accounts.

“First, [Prometheus] a time series database that you can edit, and it’s very flexible. It has labels, and you don’t have to decide from the very beginning the metrics you want to have, you can add them afterwards or edit them,” said Carretero. Secondly, Prometheus does not require a messaging external service, unlike competitor Sensu, which relies on RabbitMQ.

Visualizing data in real-time is simple with the pairing of Grafana and Prometheus. “It’s pretty straightforward to put Grafana on top of Prometheus. It takes minutes to connect them. The language used to create the charts in Grafana is PromQL, which is the same as in Prometheus,” Carretero noted.

While still in the beginning stages of making the shift toward a Kuberenetes-based 12-factor infrastructure, ShuttleCloud aims to streamline how its service utilize system resources. This is an effort to save both money and time, making use of not only Prometheus but leveraging the Kubernetes container orchestration engine to group its running instances on one node, rather than having a single instance per service.

“You don’t have to have a lot of money, or a great budget to implement Prometheus,”  Carretero noted.

December 12, 2016 // New York City @ Conrad New York

December 12, 2016 // New York City @ Conrad New York

Let’s have some pancakes at Tectonic Summit! Come have a short stack with The New Stack as we discuss how enterprises are scaling containers across their organizations. What are the use cases that are emerging as companies adopt practices for application management?

Cisco sponsored this podcast.

A newsletter digest of the week’s most important stories & analyses.

View / Add Comments

Please stay on topic and be respectful of others. Review our Terms of Use.