## Default values for Wavefront ## This is a unique name for the cluster ## All metrics will receive a `cluster` tag with this value ## Required clusterName: KUBERNETES_CLUSTER_NAME ## Wavefront URL (cluster) and API Token ## Required wavefront: url: https://YOUR_CLUSTER.wavefront.com token: YOUR_API_TOKEN ## Wavefront Collector is responsible to get all Kubernetes metrics from your cluster. ## It will capture Kubernetes resources metrics available from the kubelets, ## as well as auto-discovery capabilities. collector: enabled: true image: repository: wavefronthq/wavefront-kubernetes-collector tag: 0.9.7 pullPolicy: IfNotPresent ## If set to true, metrics will be sent to Wavefront via a Wavefront Proxy. ## When true you must either specify a value for `collector.proxyAddress` or set `proxy.enabled` to true ## If set to false, metrics will be sent to Wavefront via the Direct Ingestion API useProxy: true ## Can be used to specify a specific address for the Wavefront Proxy ## The proxy can be anywhere network reachable including outside of the cluster ## Required if `collector.useProxy` is true and `proxy.enabled` is false # proxyAddress: wavefront-proxy:2878 ## This is the Kubelet summary api endpoint and options. ## Ref: https://github.com/wavefrontHQ/wavefront-kubernetes-collector/blob/master/docs/configuration.md#kubernetes-source # kubernetesSource: kubernetes.summary_api:'' ## If using Openshift (see below to enable) use the following for kubernetesSource # kubernetesSource: kubernetes.summary_api:${MASTER_URL}?useServiceAccount=true&kubeletHttps=true&kubeletPort=10250 ## If set to true, any Kubernetes labels will be applied to metrics as tags. Defaults to false. includeLabels: true ## If set to true, all container metrics will be sent to Wavefront. ## When set to false, container level metrics are skipped (pod level and above are still sent to Wavefront). Defaults to true. # includeContainers: true ## The global prefix to be added for Kubernetes metrics. Defaults to `kubernetes.`. ## This does not apply to other sources. Use source level prefixes for sources other than the Kubernetes source. # prefix: kubernetes. ## max number of CPUs that can be used simultaneously. Less than 1 for default (number of cores) # maxProcs: 0 ## The resolution at which the collector will retain metrics. (default 1m) # interval: 1m ## Timeout for exporting data (default 20s) # sinkDelay: 20s ## log level. Uses V logs (glog) # logVerbosity: 0 ## Discovery capabilities of Wavefront Collector discovery: enabled: true ## Rules based discovery collection configuration ## Ref: https://github.com/wavefrontHQ/wavefront-kubernetes-collector/blob/master/docs/discovery.md#rules-based-discovery # config: # config.yaml: | # global: # discovery_interval: 10m # prom_configs: # - name: kube-dns-discovery # labels: # k8s-app: kube-dns # port: 10055 # path: /metrics # scheme: http # source: kube-dns # prefix: kube.dns. # tags: # env: prod # collector: wavefront-collector ## Wavefront Collector resource requests and limits ## Make sure to keep requests and limits equal to keep the pods in the Guaranteed QoS class ## Ref: http://kubernetes.io/docs/user-guide/compute-resources/ resources: requests: cpu: 200m memory: 256Mi limits: cpu: 200m memory: 256Mi ## Wavefront Proxy is a metrics forwarder that is used to relay metrics to the Wavefront SaaS service. ## It can receive metrics from the Wavefront Collector as well as other metrics collection services ## within your cluster. The proxy also supports preprocessor rules to allow you to further filter ## and enhance your metric names, and tags. Should network connectivity fall between the proxy and ## Wavefront SaaS service, the proxy will buffer metrics, which will be flushed when connectivity resumes. ## Ref: https://docs.wavefront.com/proxies.html proxy: enabled: true image: repository: wavefronthq/proxy tag: 4.35 pullPolicy: IfNotPresent ## The port number the proxy will listen on for metrics in Wavefront data format. ## This is usually 2878 port: 2878 ## The port nubmer the proxy will listen on for tracing spans in Wavefront trace data format. ## This is usually 30000 # tracePort: 30000 ## The port nubmer the proxy will listen on for tracing spans in Jaeger data format. ## This is usually 30001 # jaegerPort: 30001 ## The port nubmer the proxy will listen on for tracing spans in Zipkin data format. ## This is usually 9411 # zipkinPort: 9411 ## Sampling rate to apply to tracing spans sent to the proxy. ## This rate is applied to all data formats the proxy is listening on. ## Value should be between 0.0 and 1.0. Default is 1.0 # traceSamplingRate: 0.25 ## When this is set to a value greater than 0, ## spans that are greater than or equal to this value will be sampled. # traceSamplingDuration: 500 ## Any configuration property can be passed to the proxy via command line args in ## in the format: `-- `. Multiple properties can be specified ## separated by whitespace. ## Ref: https://docs.wavefront.com/proxies_configuring.html # args: ## Proxy is a Java application. By default Java will consume upto 4G of heap memory. ## This can be used to override the default. Uses the `-Xmx` command line option for java # heap: 1024m ## Preprocessor rules is a powerful way to apply filtering or to enhance metrics as they flow ## through the proxy. You can configure the rules here. By default a rule to drop Kubernetes ## generated labels is applied to remove unecessary and often noisy tags. ## Ref: https://docs.wavefront.com/proxies_preprocessor_rules.html preprocessor: rules.yaml: | '2878': - rule : drop-generated-label-tags action : dropTag tag : label\.(controller-revision-hash|pod-template-.*|.*kubernetes\.io.*) # - rule : add-cluster-tag # action : addTag # tag : cluster # value : {{ .Values.clusterName | quote }} ## Specifies whether RBAC resources should be created rbac: create: true ## Specifies whether a ServiceAccount should be created serviceAccount: create: true ## The name of the ServiceAccount to use. ## If not set and create is true, a name is generated using the fullname template name: ## kube-state-metrics are used to get metrics about the state of the Kubernetes scheduler ## If enabled the kube-state-metrics chart will be installed as a subchart and the collector ## will be configured to capture metrics. kubeStateMetrics: enabled: true ## Openshift integration can be enabled here ## If enabled is true, you must specify `collector.kubernetesSource` to be a valid ## summary api endpoint within your Openshift environment. openshift: enabled: false ## Wavefront proxy requires a persistent volume claim for its metrics buffers in Openshift ## If `proxy.enabled` is true, this must be set to the name of a persistent volume claim ## that the proxy can use for its buffers. # pvcName: wavefront-storage