6. Instrumenting with client libraries on Prometheus Basics Training

6.1 Tasks: Instrumenting

Mon, 01 Jan 0001 00:00:00 +0000

Task 6.1.1: Get the source code

git clone https://github.com/acend/prometheus-training-go-instrumentation.git

Change into the freshly cloned git repository

cd prometheus-training-go-instrumentation

TODO: create Dockerfile This application creates a simple webserver which listens at http://localhost:8083 and returns the string Prometheus Training after a random interval between 0 and 1000 milliseconds. You can test the app by building it as a docker image using docker build -t prometheus-training-go-instrumentation:local . and then running the built image using docker run --rm -p 8083:8083 prometheus-training-go-instrumentation:local. You can then (in a separate terminal) issue a request using the command curl http://localhost:8083.

6.1 Tasks: Instrumenting

Mon, 01 Jan 0001 00:00:00 +0000

Task 6.1.1: Spring Boot Example Instrumentation

Using the micrometer metrics facade in Spring Boot Applications lets us collect all sort of metrics within a Spring Boot application. Those metrics can be exported for Prometheus to scrape by a few additional dependencies and configuration.

Let’s have a deeper look at how the instrumentation of a Spring Boot application works. For that we can use the prometheus-training-spring-boot-example application located at https://github.com/acend/prometheus-training-spring-boot-example . To make the application collect metrics and provide a Prometheus endpoint we now need to simply add the following two dependencies in the pom.xml file, where it says :

6.1 Tasks: Instrumenting

Mon, 01 Jan 0001 00:00:00 +0000