Self-Hosted Prometheus
If you are self-hosting your Cobrowse Enterprise kubernetes cluster, then deploying your own Prometheus and Grafana instances into your cluster may make the most sense for you.

Prometheus

If you do not have Prometheus running in your cluster already, then you may consider using the Prometheus Community Helm Chart to deploy the components necessary to get you started.
There is one chart that deploys a configurable node-exporter, alertnamanager and server component with ingress, which can get you started querying metrics as quickly a possible:
These example configurations and commands are intended to demonstrate the Helm repositories and chart resources you can use as a reference to help deploy a non-production prometheus instance that is capable of scraping cobrowse redis cluster and service metrics.
For a production-grade deployment with appropriate authentication, persistence, and ingress, we recommend you research the Prometheus configuration options and the full prometheus helm chart values.yaml file that are available to help you make the appropriate decisions for your organization.
1
# values.yml
2
server:
3
baseURL: http://<prometheus host>/prometheus/
4
prefixURL: /prometheus
5
ingress:
6
annotations:
7
kubernetes.io/ingress.class: nginx
8
enabled: true
9
hosts:
10
- <prometheus host>/prometheus
11
path: /prometheus
Copied!
1
> helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
2
> helm repo update
3
> helm install prometheus prometheus-community/prometheus -f values.yml
Copied!

Grafana

If you do not have Grafana installed in your cluster already, then may consider using the Grafana official Helm Chart to deploy the components necessary to get you started.
There is one chart that deploys the Grafana server with ingress and configuration to query your prometheus instance, which can get you querying metrics as quickly as possible:
These example configurations and commands are intended to demonstrate the Helm repositories and chart resources you can use as a reference to help deploy a non-production Grafana server that is capable of querying a local Prometheus server.
For a production-grade deployment with appropriate authentication, persistence, and ingress, we recommend you research the Grafana configuration options and the full Grafana helm chart values.yaml file that are available to make the appropriate decisions for your organization.
1
# values.yml
2
persistence:
3
enabled: true
4
accessModes:
5
- ReadWriteOnce
6
size: 5Gi
7
grafana.ini:
8
server:
9
domain: <grafana host>
10
root_url: "http://<grafana host>/grafana"
11
serve_from_sub_path: true
12
ingress:
13
annotations:
14
kubernetes.io/ingress.class: nginx
15
enabled: true
16
hosts:
17
- <grafana host>
18
path: /grafana
19
datasources:
20
datasources.yaml:
21
apiVersion: 1
22
datasources:
23
- name: Prometheus
24
type: prometheus
25
url: http://<prometheus host>/prometheus
26
access: proxy
27
isDefault: true
Copied!
1
> helm repo add grafana https://grafana.github.io/helm-charts
2
> helm repo update
3
> helm install grafana grafana/grafana -f values.yml
Copied!
Copy link
Contents