juliusv/prometheus_workshop

Example client/server app used for a Prometheus workshop

prometheus_workshop's Issues

Improve server example

Now I remember what the problem with the server was:

While the client is nicely reducing and increasing QPS in periodic fashion, the server is varying response latencies in a normally distributed fashion, but always in the same way, i.e. if you graph latencies with the histogram, they will always looks the same (modulo noise). I think we should vary the response time systematically over time. Like simulating an outage every 3min and increase latencies or something.

This is for Go example. Need to vet Python.

Update outdated parts

This is not about adding anything, just update everything to latest version and include the related changes.

Get familiar with Python example

Since Brian won't be with us this time, one of us should familiarize himself with the Python client and possible instrumentation.

@juliusv Would you be up for it?

Add Python example

Copy over from Brian's account, similar to the Go example, to have everything in one place.

Add concrete examples to the Pushing Metrics chapter.

That chapter essentially only points to the documentation right now. It would be nice to have a concrete example, similar to that in the doc, essentially pushing a metric with curl and then show how to look at the PGW's /metrics endpoint, how to configure Prometheus to scrape it, and how Prometheus will scrape the same value again and again until it is pushed again.

Add concrete examples to the Alerting chapter.

That chapter essentially only points to the documentation right now. It would be nice to have at least one (simple) alerting expression and some screenshots how it can be checked on the server and on the alert manager.

Rename workshop.md to README.md

If renamed, GitHub will autopreview the instructions from the workshop.md file in the repo.