Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Jira
serverONAP Jira
serverId425b2b0a-557c-3c0c-b515-579789cceedb
keyPOLICY-3886

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


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

Code Block
languagebash
docker run -d --name=prometheus --network=host -v /path/to/prometheus

...

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

Run grafana

Code Block
languagebash
docker run -d

...

 --name=grafana

...

 grafana/grafana-oss:8.3.4

...

Start node exporter, then Prometheus with the jobs to be scrapped on a prometheus.yml file configuration. IPs can be mapped with --add-host option when running docker container.


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

...

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

docker compose profile was creating extra dependencies, but docker compose allows to start two services

example: docker-compose up -d pap grafana

Issues:

Haven't solved how to connect prometheus to grafana using server access (default) as Browser access will be deprecated.

Need to find a way to have the node exporter, prometheus and grafana starting on docker compose with any run csit configuration. For now, the closest to it is docker profiles, but that's a quite big change on the docker compose file.

Need to update the pap yaml file config on csit as it's missing part of database configuration and spring app is not coming up.

got grafana, prometheus and node running along with pap, but run into cert issue, so we probably need to write our own images with the added certs.

Image Removed

Nordix review with how the updates can start

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/+/127030https://gerrit.nordix.org/c/onap/policy/docker/+/12229