{"action":"created","issue":{"url":"https://api.github.com/repos/DataDog/datadog-agent/issues/1552","repository_url":"https://api.github.com/repos/DataDog/datadog-agent","labels_url":"https://api.github.com/repos/DataDog/datadog-agent/issues/1552/labels{/name}","comments_url":"https://api.github.com/repos/DataDog/datadog-agent/issues/1552/comments","events_url":"https://api.github.com/repos/DataDog/datadog-agent/issues/1552/events","html_url":"https://github.com/DataDog/datadog-agent/issues/1552","id":311016417,"number":1552,"title":"The units of kubernetes.cpu.usage.total has changed from agent5","user":{"login":"nimeshksingh","id":7454380,"avatar_url":"https://avatars3.githubusercontent.com/u/7454380?v=4","gravatar_id":"","url":"https://api.github.com/users/nimeshksingh","html_url":"https://github.com/nimeshksingh","followers_url":"https://api.github.com/users/nimeshksingh/followers","following_url":"https://api.github.com/users/nimeshksingh/following{/other_user}","gists_url":"https://api.github.com/users/nimeshksingh/gists{/gist_id}","starred_url":"https://api.github.com/users/nimeshksingh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nimeshksingh/subscriptions","organizations_url":"https://api.github.com/users/nimeshksingh/orgs","repos_url":"https://api.github.com/users/nimeshksingh/repos","events_url":"https://api.github.com/users/nimeshksingh/events{/privacy}","received_events_url":"https://api.github.com/users/nimeshksingh/received_events","type":"User","site_admin":false},"labels":[{"id":695417157,"url":"https://api.github.com/repos/DataDog/datadog-agent/labels/team/kenafeh","name":"team/kenafeh","color":"d4c5f9","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":6,"created_at":"2018-04-03T22:10:30Z","updated_at":"2018-04-10T02:02:13Z","closed_at":null,"author_association":"NONE","body":"**Output of the info page (if this is a bug)**\r\n```\r\nroot@datadog-uds-datadog-6l9p2:/# agent status\r\nGetting the status from the agent.\r\n\r\n==============\r\nAgent (v6.1.0)\r\n==============\r\n\r\n  Status date: 2018-04-03 22:04:44.453018 UTC\r\n  Pid: 356\r\n  Python Version: 2.7.14\r\n  Logs: \r\n  Check Runners: 2\r\n  Log Level: WARNING\r\n\r\n  Paths\r\n  =====\r\n    Config File: /etc/datadog-agent/datadog.yaml\r\n    conf.d: /etc/datadog-agent/conf.d\r\n    checks.d: /etc/datadog-agent/checks.d\r\n\r\n  Clocks\r\n  ======\r\n    NTP offset: 0.000941067 s\r\n    System UTC time: 2018-04-03 22:04:44.453018 UTC\r\n\r\n  Host Info\r\n  =========\r\n    bootTime: 2018-03-21 17:33:22.000000 UTC\r\n    kernelVersion: 4.4.111&#43;\r\n    os: linux\r\n    platform: debian\r\n    platformFamily: debian\r\n    platformVersion: 9.4\r\n    procs: 68\r\n    uptime: 1.138638e&#43;06\r\n\r\n  Hostnames\r\n  =========\r\n    host_aliases: [gke-lightstep-staging-pool-3-e7fc6500-wrtr.helpful-cat-109717]\r\n    hostname: gke-lightstep-staging-pool-3-e7fc6500-wrtr.c.helpful-cat-109717.internal\r\n    socket-fqdn: datadog-uds-datadog-6l9p2\r\n    socket-hostname: datadog-uds-datadog-6l9p2\r\n\r\n=========\r\nCollector\r\n=========\r\n\r\n  Running Checks\r\n  ==============\r\n    cpu\r\n    ---\r\n      Total Runs: 56\r\n      Metrics: 6, Total Metrics: 330\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    disk\r\n    ----\r\n      Total Runs: 56\r\n      Metrics: 158, Total Metrics: 8848\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    docker\r\n    ------\r\n      Total Runs: 56\r\n      Metrics: 378, Total Metrics: 21379\r\n      Events: 0, Total Events: 13\r\n      Service Checks: 1, Total Service Checks: 56\r\n  \r\n    file_handle\r\n    -----------\r\n      Total Runs: 56\r\n      Metrics: 1, Total Metrics: 56\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    io\r\n    --\r\n      Total Runs: 56\r\n      Metrics: 156, Total Metrics: 8628\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    kube_dns\r\n    --------\r\n      Total Runs: 55\r\n      Metrics: 80, Total Metrics: 4400\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    kubelet\r\n    -------\r\n      Total Runs: 55\r\n      Metrics: 704, Total Metrics: 38925\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 3, Total Service Checks: 165\r\n  \r\n    kubernetes_apiserver\r\n    --------------------\r\n      Total Runs: 55\r\n      Metrics: 0, Total Metrics: 0\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    load\r\n    ----\r\n      Total Runs: 55\r\n      Metrics: 6, Total Metrics: 330\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    memory\r\n    ------\r\n      Total Runs: 55\r\n      Metrics: 14, Total Metrics: 770\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    network\r\n    -------\r\n      Total Runs: 55\r\n      Metrics: 146, Total Metrics: 8030\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    ntp\r\n    ---\r\n      Total Runs: 55\r\n      Metrics: 1, Total Metrics: 55\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 1, Total Service Checks: 55\r\n  \r\n    uptime\r\n    ------\r\n      Total Runs: 55\r\n      Metrics: 1, Total Metrics: 55\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 0, Total Service Checks: 0\r\n  \r\n    zk\r\n    --\r\n      Total Runs: 55\r\n      Metrics: 30, Total Metrics: 1650\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 1, Total Service Checks: 55\r\n  \r\n    zk\r\n    --\r\n      Total Runs: 55\r\n      Metrics: 30, Total Metrics: 1650\r\n      Events: 0, Total Events: 0\r\n      Service Checks: 1, Total Service Checks: 55\r\n  \r\n========\r\nJMXFetch\r\n========\r\n\r\n  Initialized checks\r\n  ==================\r\n    jmx\r\n      instance_name : jmx_instance\r\n      message : \r\n      metric_count : 13\r\n      service_check_count : 0\r\n      status : OK\r\n  Failed checks\r\n  =============\r\n    no checks\r\n    \r\n=========\r\nForwarder\r\n=========\r\n\r\n  CheckRunsV1: 56\r\n  IntakeV1: 16\r\n  RetryQueueSize: 0\r\n  Success: 128\r\n  TimeseriesV1: 56\r\n\r\n  API Keys status\r\n  ===============\r\n    https://6-1-0-app.agent.datadoghq.com,*************************a39e7: API Key valid\r\n\r\n==========\r\nLogs Agent\r\n==========\r\n\r\n  Logs Agent is not running\r\n\r\n=========\r\nDogStatsD\r\n=========\r\n\r\n  Checks Metric Sample: 97414\r\n  Event: 14\r\n  Events Flushed: 14\r\n  Number Of Flushes: 56\r\n  Series Flushed: 94103\r\n  Service Check: 1273\r\n  Service Checks Flushed: 1319\r\n  Dogstatsd Metric Sample: 236300\r\n```\r\n\r\n**Describe what happened:**\r\nI have a daemonset running datadog agents in a kubernetes 1.8 cluster.  After adding a new daemonset with a v6 agent and deleting the v5 agent daemonset, the kubernetes.cpu metrics have changed units.  kubernetes.cpu.limits and kubernetes.cpu.requests is now 1/1000 of what it was before.  kubernetes.cpu.usage.total is now a much smaller number.  It usually seems approximately 1/1000 of what it was before, but not quite right.\r\n\r\n**Describe what you expected:**\r\nThe cpu metrics should be unchanged.\r\n\r\n**Steps to reproduce the issue:**\r\nUpgrade from dd-agent 5 to datadog-agent 6.\r\n\r\n**Additional environment details (Operating System, Cloud provider, etc):**\r\nKubernetes 1.8, datadog-agent jmx docker image, GKE\r\n"},"comment":{"url":"https://api.github.com/repos/DataDog/datadog-agent/issues/comments/379949729","html_url":"https://github.com/DataDog/datadog-agent/issues/1552#issuecomment-379949729","issue_url":"https://api.github.com/repos/DataDog/datadog-agent/issues/1552","id":379949729,"user":{"login":"nimeshksingh","id":7454380,"avatar_url":"https://avatars3.githubusercontent.com/u/7454380?v=4","gravatar_id":"","url":"https://api.github.com/users/nimeshksingh","html_url":"https://github.com/nimeshksingh","followers_url":"https://api.github.com/users/nimeshksingh/followers","following_url":"https://api.github.com/users/nimeshksingh/following{/other_user}","gists_url":"https://api.github.com/users/nimeshksingh/gists{/gist_id}","starred_url":"https://api.github.com/users/nimeshksingh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nimeshksingh/subscriptions","organizations_url":"https://api.github.com/users/nimeshksingh/orgs","repos_url":"https://api.github.com/users/nimeshksingh/repos","events_url":"https://api.github.com/users/nimeshksingh/events{/privacy}","received_events_url":"https://api.github.com/users/nimeshksingh/received_events","type":"User","site_admin":false},"created_at":"2018-04-10T02:02:13Z","updated_at":"2018-04-10T02:02:13Z","author_association":"NONE","body":"Actually, the more I look at this, the more it seems that the kubernetes.cpu and kubernetes.mem metrics are just wrong a lot of the time with agent6.  I'm seeing things like two pods that have the same cpu usage according the kuberenetes dashboard with wildly different cpu usages in datadog.  Also, for processes with very steady memory usage, memory in datadog just jumps around in ways that don't match the kubernetes dashboard's view.\r\n\r\nShould I open a bug in integrations-core?"}}
{"actor":{"display_login":"nimeshksingh"}}