-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metric API proposal to cover typical Kubernetes metrics #1001
Comments
Our discussions showed that it is hard to split the metrics from input:
runtime:
enabled: true
resources:
pod:
enabled: true
container:
enabled: true
node:
enabled: true
volume:
enabled: true
daemonset:
enabled: false
deployment:
enabled: false
statefulset:
enabled: false
quota:
enabled: false
job:
enabled: false
hpa:
enabled: false
namespaces:
include:
- myNamespace The individual resources should include the following metrics: podk8s.pod.cpu.time (kubeletstats) containerk8s.container.cpu_limit (k8scluster) nodek8s.node.cpu.utilization (kubeletstats) volumek8s.volume.available (kubeletstats) daemonsetk8s.daemonset.current_scheduled_nodes (k8scluster) deploymentk8s.deployment.available (k8scluster) statefulsetk8s.statefulset.current_pods (k8scluster) quotak8s.resource_quota.hard_limit (k8scluster) jobk8s.cronjob.active_jobs (k8scluster) hpak8s.hpa.current_replicas (k8scluster) The bold marked metrics are already part of the |
The shown proposal will be implemented as MetricPipeline input in a follow up. |
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
Ideas
Reasons
Attachments
Release Notes
The text was updated successfully, but these errors were encountered: