Task load state always be zero #1672
Labels
Comments
|
I have similar issue. I've launched a whole stack using example from https://github.com/stefanprodan/dockprom. Setup: Ubuntu 16.04 via Vagrant / VirtualBox on Windows box. compose file contains such specification of cadvisor service: Note: I've added volume mapping to get OOM reporting After enabling verbose logging I am seeing this in cadvisor logs: container_tasks_state metrics is zero for everything in cadvisor: |
|
Similar with cAdvisor running in Docker on a Debian GCE instance. All the |
|
Just updated to |
|
+1 |
|
Have you tried enabling load reader |
|
Hi, There are no errors in the log. |
|
Make sure you are setting the flag |
|
I have a similar issue too. |
|
Have the same issue at the moment, also after adding the row below to my cAdvisor docker compose:
|
|
Same here, adding cadvisor:
image: google/cadvisor
command: "--enable_load_reader=true"
privileged: true
volumes:
- /:/rootfs:ro
- /var/run:/var/run:rw
- /sys:/sys:ro
- /var/lib/docker/:/var/lib/docker:ro
- /cgroup:/cgroup:ro
network_mode: "host"
restart: always |
|
Same behaviour here, would be nice if someone could enlighten us on what might be wrong? |
|
same problem here, can anyone solve it? |
|
@dashpole still encounter this issue running the latest v0.32.0. Adding |
|
I remember looking into this before... cAdvisor needs to be on the host network, but i'm not sure how to accomplish that with a docker compose. See #2051 for more details, and a kustomize patch to do this in kubernetes. |
|
Thanks for prompt response! Did a quick test and it looks like to be working. This is the compose file I use to deploy in swarm mode (thanks to moby/issues/25873 as network_mode is ignored): |
mfournier
pushed a commit
to camptocamp/rancher-template-metrics
that referenced
this issue
Mar 15, 2019
|
Prometheus and cadvisory must be in one docker network. |
|
I am using the host network with "enable_load_reader=true". Also had to set a different port for cadvisor since I'm using the default one - 8080: With this I've chnaged the prometheus.yml config file to set the new targets like this: Now I'm getting the following results when I run a "container_tasks_state{container_label_com_docker_swarm_service_name="portainer"}" query: Now all the containers are in state sleeping with a weird value for it. |
|
@sofronic is it possible your container tasks are sleeping? Try running a container with the image |
|
@dashpole I've ran stress:v1 as a swarm service and it is comming with a state "running" == 1 and "sleeping" == 4. I've noticed that some other containers are poping up as running from tme to time. But I've got 100+ of them in 87 swarm services. So only containers using 1 cpu or more will come up as runing? |
|
@sofronic if your application isn't actively doing processing, such as listening on a port, or |
|
I use kubelet api: http://10.142.113.20:10255/metrics/cadvisor. It has the same problem. |
|
I'm facing the same problem .So I enabled load reader and network_mode: "host". |
same issue. do not know the reason. But I find the if the container is killed or stopped. All the metrics will disappear also rather than increase the number of the stopped statue. |
|
+1 Any progress on this issue? I've enabled the cadvisor:
image: [...]/cadvisor:v0.49.1
ports: [ 9090:9090 ]
network_mode: host
pid: host
privileged: true
volumes:
[...]
command:
- -port=9090
- -docker_only=true
- -enable_load_reader=true
- -prometheus_endpoint=/container-exporter/metrics |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi team,
I started to use cadvisor, and
container_tasks_statemetrics which are exposed on the/metricsendpoint always show zero:My cadvisor version is:
Is that a bug here? What I can see in the log is some failed msg:
But these seems to be not related to this issue.
Thanks.
The text was updated successfully, but these errors were encountered: