Page Comparison

Grafana docker image: grafana/grafana-oss:8.3.4

Prometheus docker image: prom/prometheus:v2.32.1

Node exporter docker image: prom/node-exporter:v1.3.1

Run node exporter and prometheus

docker run -d -p 9100:9100 prom/node-exporter:v1.3.1

docker run -d -p 9090:9090 Running as standalone:

Start the policy components on HTTP mode (so no trust/key store). Collect the IPs of applications.

Edit the prometheus configuration YAML file. (update here the file)

Run Prometheus

docker run -d --name=prometheus --network=host -v /

...

path/

...

to/

...

prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus:v2.32.1

Run grafana

docker run -d

...

 -

...

-

...

name=grafana

...

 grafana/grafana-oss:8.3.4

...

API - http://172.18.0.7:6969/

Start the docker composer for the applications. Get IPs

Start node exporter, then Prometheus with the jobs to be scrapped on a prometheus.yml file configuration.

Navigate to localhost:9090 to check if targets are up and running.

...

Save and test to check if Grafana can connect to Prometheus.

Remember to stop/remove containers to run the commands again.

Running with docker-compose:

Clone the docker project.

Run ./csit/start-grafana.sh to start all the policy components (except for clamp) or run ./csit/start-grafana.sh ${component} to start per component. (i.e ./csit/start-grafana.sh pap will start pap and its dependencies only)

Prometheus and Grafana endpoints are shown at the end of script execution. Navigate to ${prometheus}/targets to check if all apps are up and connecting to the service. It takes a few minutes.

Docker compose setup has provisioning of prometheus datasource and two dashboards. As of now, only PAP and API have more detailed stats due to the use of micrometer and actuator. 

Review:

https://gerrit.onap.org/r/c/policy/docker/+/127030