Skip to content
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

[receiver/kubeletstats] how to get kuberbetes metrics as percent-based #34952

Open
NamanGajjar26 opened this issue Sep 2, 2024 · 2 comments
Open
Labels

Comments

@NamanGajjar26
Copy link

Component(s)

receiver/kubeletstats

Describe the issue you're reporting

hello

opentelemetry in configure kubeletstats in receiver there are get pod cpu,memory (usage) in float i want to get in percent-based
how to get metrics percent-based
opentelemetry in configure like below

      `kubeletstats:      
            insecure_skip_verify: true  
            collection_interval: 30s     
            metrics:
              container.cpu.time:
                enabled: true
              container.cpu.utilization:
                enabled: true
              container.memory.available:
                enabled: true
              container.memory.usage:
                enabled: true
              k8s.node.cpu.time:
                enabled: true
              k8s.node.cpu.usage:
                enabled: true
              k8s.node.memory.available:
                enabled: true
              k8s.node.memory.usage:
                enabled: true
              k8s.pod.cpu.time:
                enabled: true
              k8s.pod.cpu.usage:
                enabled: true        
              k8s.pod.memory.available:
                enabled: true
              k8s.pod.memory.usage:
                enabled: true 
              k8s.container.memory_limit_utilization:
                enabled: true 
              k8s.container.memory_request_utilization:
                enabled: true
              k8s.container.memory.node.utilization:
                enabled: true
              k8s.container.cpu_request_utilization:
                enabled: true
              k8s.container.cpu_limit_utilization:
                enabled: true
              k8s.container.cpu.node.utilization:
                enabled: true
              k8s.pod.memory_request_utilization:
                enabled: true
              k8s.pod.memory_limit_utilization:
                enabled: true
              k8s.pod.memory.node.utilization:
                enabled: true
              k8s.pod.cpu_request_utilization:
                enabled: true
              k8s.pod.cpu_limit_utilization:
                enabled: true  `
@NamanGajjar26 NamanGajjar26 added the needs triage New item requiring triage label Sep 2, 2024
Copy link
Contributor

github-actions bot commented Sep 2, 2024

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Copy link
Contributor

github-actions bot commented Nov 4, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant