@@ -23,7 +23,7 @@ Now quickly confirm that /mnt/promdash/file.sqlite3 exists, and has a non-zero s
...
@@ -23,7 +23,7 @@ Now quickly confirm that /mnt/promdash/file.sqlite3 exists, and has a non-zero s
```
```
Looks open enough :).
Looks open enough :).
1. Now, you can start this pod, like so `kubectl create -f cluster/add-ons/prometheus/prometheusB3.yaml`. This pod will start both prometheus, the server, as well as promdash, the visualization tool. You can then configure promdash, and next time you restart the pod - you're configuration will be remain (since the promdash directory was mounted as a local docker volume).
1. Now, you can start this pod, like so `kubectl create -f contrib/prometheus/prometheus-all.json`. This ReplicationController will maintain both prometheus, the server, as well as promdash, the visualization tool. You can then configure promdash, and next time you restart the pod - you're configuration will be remain (since the promdash directory was mounted as a local docker volume).
1. Finally, you can simply access localhost:3000, which will have promdash running. Then, add the prometheus server (locahost:9090)to as a promdash server, and create a dashboard according to the promdash directions.
1. Finally, you can simply access localhost:3000, which will have promdash running. Then, add the prometheus server (locahost:9090)to as a promdash server, and create a dashboard according to the promdash directions.
...
@@ -31,13 +31,13 @@ Looks open enough :).
...
@@ -31,13 +31,13 @@ Looks open enough :).
You can launch prometheus easily, by simply running.
You can launch prometheus easily, by simply running.
This will bind to port 9090 locally. You can see the prometheus database at that URL.
This will bind to port 9090 locally. You can see the prometheus database at that URL.
# How it works
# How it works
This is a v1beta1 based, containerized prometheus pod, which scrapes endpoints which are readable on the KUBERNETES_RO service (the internal kubernetes service running in the default namespace, which is visible to all pods).
This is a v1beta3 based, containerized prometheus ReplicationController, which scrapes endpoints which are readable on the KUBERNETES_RO service (the internal kubernetes service running in the default namespace, which is visible to all pods).
1. The KUBERNETES_RO service is already running : providing read access to the API metrics.
1. The KUBERNETES_RO service is already running : providing read access to the API metrics.
...
@@ -68,7 +68,5 @@ at port 9090.
...
@@ -68,7 +68,5 @@ at port 9090.
- We should publish this image into the kube/ namespace.
- We should publish this image into the kube/ namespace.
- Possibly use postgre or mysql as a promdash database.
- Possibly use postgre or mysql as a promdash database.