Metric API proposal to cover typical Kubernetes metrics

[a-thaler]

Description
As outlined in #972 typical metrics should be easily collactable so that typical kubernetes workload monitoring gets possible. The metrics should be based on the kubletstatsreceiver and k8sclusterreceiver only.
A concrete API proposal is needed on how to enable the metric collection from user side. Hereby, you need to think about which metrics you are usually enabling together as they are always used in combination. Also, the selection via namespaces should be applied to namespace-typical metrics only.
The input name should trigger the right expectations.

Criterias

• Concrete API proposal for selecting the typical metrics, outlining which chunk of metrics are getting enabled by which input
• Users should be able to limit metrics to certain namespaces
• Users should be able to enable bigger chunks selectively

Ideas

  input:
    cluster:
      enabled: true
      namespaces:
        include:
        - myNamespace
    host:
      enabled: true
    runtime:
      enabled: true
      namespaces:
        include:
        - myNamespace

Reasons

Attachments

Release Notes