From aee164d88269f2a5af8d1b8d109c33def9560051 Mon Sep 17 00:00:00 2001 From: Martijn Atema Date: Sun, 18 Apr 2021 12:58:55 +0200 Subject: [PATCH] Demo proposal: cloudprobe --- contributions/demo/atema-siper/README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 contributions/demo/atema-siper/README.md diff --git a/contributions/demo/atema-siper/README.md b/contributions/demo/atema-siper/README.md new file mode 100644 index 0000000000..c5202ac2bb --- /dev/null +++ b/contributions/demo/atema-siper/README.md @@ -0,0 +1,12 @@ +# Monitoring availability using Cloudprobe and Prometheus + +## Members + +Martijn Atema, atema@kth.se, GitHub: Atema +Simon Persson, siper@kth.se, GitHub: altaired + +## Proposal + +After building software that users depend on every day it becomes clear that uptime and response times are very important measures to always keep track of. We need to be able to respond quickly when something goes wrong, and want to know when an endpoint doesn't work; preferably before the user even notices. There are some paid, closed-source tools that achieve this, but there's very few self-hosted, open-source alternatives. + +[Cloudprober](https://cloudprober.org) is a good option; it is an open-source monitoring tool that makes it easy to monitor availability and performance of applications. In this demo we will show how to setup Cloudprober to monitor an API and then display the data in [Prometheus](https://prometheus.io).