[metricbeat]Add kubernetes scheduler dashboard

CHANGELOG.next.asciidoc

@@ -261,11 +261,13 @@ https://github.com/elastic/beats/compare/v7.0.0-alpha2...master[Check the HEAD d
 - Allow redis URL format in redis hosts config. {pull}12408[12408]
 - Add tags into ec2 metricset. {issue}[12263]12263 {pull}12372[12372]
 - Add kubernetes metricset `scheduler` {pull}12521[12521]
+- Add Kubernetes scheduler dashboard to Kubernetes module {pull}12749[12749]
 - Add `beat` module. {pull}12181[12181] {pull}12615[12615]
 - Collect tags for cloudwatch metricset in aws module. {issue}[12263]12263 {pull}12480[12480]
 - Add AWS RDS metricset. {pull}11620[11620] {issue}10054[10054]
 - Add Oracle Module {pull}11890[11890]
 
+
 *Packetbeat*
 
 *Functionbeat*

metricbeat/docs/modules/kubernetes.asciidoc

@@ -10,6 +10,7 @@ This module fetches metrics from Kubernetes several components:
 - https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/[kubelet]
 - https://github.com/kubernetes/kube-state-metrics[kube-state-metrics]
 - https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/[apiserver]
+- https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/[scheduler]
 - https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/[proxy]
 
 All metricsets with the `state_` prefix require `hosts` field pointing to kube-state-metrics
@@ -23,12 +24,20 @@ The default metricsets are `container`, `node`, `pod`, `system` and `volume`.
 
 The Kubernetes module is tested with Kubernetes 1.13.x and 1.14.x
 
+Dashboards for `scheduler` and `proxy` are not compatible with kibana versions below `7.2.0`
+
 [float]
 === Dashboard
 
-Kubernetes module is shipped including default dashboards for `apiserver` and `proxy`.
+Kubernetes module is shipped including default dashboards for `apiserver`, `scheduler` and `proxy`.
+
 If you are using HA for those components, be aware that when gathering data from all instances the dashboard will usually show and average of the metrics. For those scenarios filtering by hosts or service address is possible.
 
+Kubernetes scheduler example:
+
+image::./images/metricbeat_kubernetes_scheduler.png[]
+
+
 Kubernetes proxy example:
 
 image::./images/metricbeat-kubernetes-proxy.png[]

metricbeat/module/kubernetes/_meta/docs.asciidoc

@@ -3,6 +3,7 @@ This module fetches metrics from Kubernetes several components:
 - https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/[kubelet]
 - https://github.com/kubernetes/kube-state-metrics[kube-state-metrics]
 - https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/[apiserver]
+- https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/[scheduler]
 - https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/[proxy]
 
 All metricsets with the `state_` prefix require `hosts` field pointing to kube-state-metrics
@@ -16,12 +17,20 @@ The default metricsets are `container`, `node`, `pod`, `system` and `volume`.
 
 The Kubernetes module is tested with Kubernetes 1.13.x and 1.14.x
 
+Dashboards for `scheduler` and `proxy` are not compatible with kibana versions below `7.2.0`
+
 [float]
 === Dashboard
 
-Kubernetes module is shipped including default dashboards for `apiserver` and `proxy`.
+Kubernetes module is shipped including default dashboards for `apiserver`, `scheduler` and `proxy`.
+
 If you are using HA for those components, be aware that when gathering data from all instances the dashboard will usually show and average of the metrics. For those scenarios filtering by hosts or service address is possible.
 
+Kubernetes scheduler example:
+
+image::./images/metricbeat_kubernetes_scheduler.png[]
+
+
 Kubernetes proxy example:
 
 image::./images/metricbeat-kubernetes-proxy.png[]