| Jira | ||||||
|---|---|---|---|---|---|---|
|
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 | ||
|---|---|---|
| ||
docker run -d -p --name=prometheus |
...
--network=host -v / |
...
path/ |
...
to/ |
...
prometheus.yml:/etc/prometheus/prometheus.yml prom/prometheus:v2.32.1 |
Run grafana
| Code Block | ||
|---|---|---|
| ||
docker run -d |
...
- |
...
- |
...
name=grafana |
...
grafana/grafana-oss:8.3.4 |
...
Start the docker composer for the applications. Get IPs
...
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: Starting with docker-compose up -d pap grafanaIssues:
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.
Nordix review with how the updates can start
...