github.com/aclisp/heapster@v0.19.2-0.20160613100040-51756f899a96/docs/influxdb.md (about)

     1  # Run Heapster in a Kubernetes cluster with an InfluxDB backend and a Grafana UI
     2  
     3  ### Setup a Kubernetes cluster
     4  [Bring up a Kubernetes cluster](https://github.com/kubernetes/kubernetes), if you haven't already. Ensure that `kubecfg.sh` is exported.
     5  
     6  ### Start all of the pods and services
     7  ```shell
     8  $ kubectl create -f deploy/kube-config/influxdb/
     9  ```
    10  
    11  Grafana service by default requests for a LoadBalancer. If that is not available in your cluster, consider changing that to NodePort. Use the external IP assigned to the Grafana service,
    12  to access Grafana.
    13  The default user name and password is 'admin'.
    14  Once you login to Grafana, add a datasource that is InfluxDB. The URL for InfluxDB will be `http://localhost:8086`. Database name is 'k8s'. Default user name and password is 'root'. 
    15  Grafana documentation for InfluxDB [here](http://docs.grafana.org/datasources/influxdb/).
    16  
    17  Take a look at the [storage schema](storage-schema.md) to understand how metrics are stored in InfluxDB.
    18  
    19  Grafana is set up to auto-populate nodes and pods using templates.
    20  
    21  ## Troubleshooting guide
    22  1. If the Grafana service is not accessible, chances are it might not be running. Use `kubectl.sh` to verify that the `heapster` and `influxdb & grafana` pods are alive.
    23  
    24  	kubectl get pods
    25  
    26  	kubectl get services
    27  
    28  2. To access the InfluxDB UI, you will have to make the InfluxDB service externally visible, similar to how Grafana is made publicly accessible.
    29  
    30  3. If you find InfluxDB to be using up a lot of CPU or memory, consider placing resource restrictions on the `InfluxDB & Grafana` pod. You can add `cpu: <millicores>` and `memory: <bytes>` in the [Controller Spec](../deploy/kube-config/influxdb/influxdb-grafana-controller.yaml) and relaunch the controllers: