blob: ae4cf0893904beedf9dd1b85423dfe775396c66e [file] [log] [blame]
Doyoung Lee8f30e152019-05-21 16:23:07 -07001Thank you for installing {{ .Chart.Name }}.
2
3This chart is for CDN monitoring in M-CORD demo scenarios.
4To show CDN traffic of CDN server, this chart deploys cAdvisor, Grafana, and Prometheus.
5
6You can determine which components will be installed by values.yaml.
7
8{{- if .Values.cadvisor.enabled }}
9
10
11- cAdvisor
12
13You can now access cAdvisor at: <node-ip>:{{ .Values.cadvisor.nodePort }}
14Prometheus will collect data through this cAdvisor at: <node-ip>:{{ .Values.cadvisor.nodePort }}/metrics
15
16
17{{- end }}
18
19
20{{- if .Values.grafana.enabled }}
21
22
23- Grafana
24
25You can now access Grafana at: <{{ .Values.grafana.node_selector }}-ip>:{{ .Values.grafana.nodePort }}
26using:
27
28username: {{ .Values.grafana.adminUser}}
29password: {{ .Values.grafana.adminPassword}}
30
31We use configs/cdn_metrics.json in default to create dashboards.
32If you want to monitor other CDN servers which have different container names, you should modify the json file or create your own json files.
33
34
35{{- end}}
36
37
38{{- if .Values.prometheus.enabled }}
39
40
41- Prometheus
42
43You can now access Prometheus at: <{{ .Values.prometheus.node_selector }}-ip>:{{ .Values.prometheus.nodePort }}
44If you want to show CDN traffics by Grafana, Grafana should select this Prometheus as data source.
45
46
47{{- end }}