-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
cAdvisor container names not captured using cadvisor->influxdb driver #1127
Comments
cAdvisor will expose the On Thu, Feb 25, 2016 at 10:42 AM, Marcello de Sales <
|
@vishh The screenshot above is from the |
Can you post the output of On Thu, Feb 25, 2016 at 1:52 PM, Marcello de Sales <[email protected]
|
@vishh sure! Let me collect the values and report... |
Hi @vishh Here's the output of https://gist.github.com/marcellodesales/ca8922b8fa6cf3d42f7c |
I still suspect that cadvisor is not able to talk to docker and so is On Thu, Feb 25, 2016 at 2:32 PM, Marcello de Sales <[email protected]
|
@vishh even running on the same host, what does
|
Can you post cAdvisor logs? If its having trouble connecting to docker it On Thu, Feb 25, 2016 at 2:50 PM, Marcello de Sales <[email protected]
|
@vishh let me collect those...
From here, I see the first error...
Then, I think the server went up again, and lost the database...
QuestionCould this be the source of the problems? We used to see the full container names before... And now only the IDs... |
No. Can you try running with On Thu, Feb 25, 2016 at 3:16 PM, Marcello de Sales <[email protected]
|
@vishh Let me try... |
@vishh I just restarted it...
The
|
Also, I started seeing the following: Is there a to setup the rate and maybe decrease the throughput?
|
It looks an InfluxDB rate limiter. You can set the syncing period to be On Thu, Feb 25, 2016 at 3:50 PM, Marcello de Sales <[email protected]
|
@vishh Hummm Yeah our influxdb team might have added something to it as they mentioned that our cadvisor from only 4 hosts was pushing events at the rate of Ok, let me add the flag and see if we can collect anything else... |
FYI: You can reduce the write rate from cadvisor side On Thu, Feb 25, 2016 at 4:30 PM, Marcello de Sales <[email protected]
|
@vishh how? :) Any pointers? |
On Thu, Feb 25, 2016 at 4:32 PM, Marcello de Sales <[email protected]
|
@vishh awesome |
@vishh I added the flag The current command is as follows:
Here's the log...
|
I will be adding the rate as described at #1074 (comment)... @vishh Any points from the logs above? |
Ignore the du logs it will be fixed in the next release. Can you post all On Fri, Feb 26, 2016, 12:02 PM Marcello de Sales [email protected]
|
@vishh Sounds good... I will be busy for the next 1-2hs but I will post another Gist with it... Thanks a lot Vish! |
Same problem here. Any update ? |
Same here. I've upgraded Docker 1.9 -> 1.11 and now I can't see container names in influxdb. Any update? @vishh @marcellodesales @TeChn4K |
Me too. i've upgraded to 1.11.1 I can't see container name in influxdb and i can't see network interface in cadvisor. Please help me. Thank you. |
Can you try the latest cadvisor version - |
I used cadvisor tag :lastest |
We added support for docker v1.11 in cadvisor On Sun, May 1, 2016 at 1:50 PM, Santi Lertsumran [email protected]
|
Ok this work. Tahnk you very much. |
Having the same issue in kubernetes setup. As cadvisor is embedded in kubelet binary, how can the cadvisor be upgraded in the kubernetes setup ? |
The only way to upgrade the cAdvisor version used by the Kubelet is to build a new kubelet with the latest release (included at head, but not the latest pre-release). cAdvisor can be run in "standalone" mode (see https://github.com/timstclair/kube-contrib/blob/master/devel/manifests/cadvisor-pod.yaml), but you are likely to run into other issues running Kubernetes with docker v1.11 without running Kubelet binaries compiled in the last week. |
Thanks @timstclair - very useful. |
Closing this, as it deals with a previous version, and appears to be resolved. |
Problem
The container names captured by cAdvisor are the container IDs instead of the names...
This is directly reflected in the InfluxDB values of the
container_name
as shown below:Details
The
docker-engine
lists the proper names that are intended to be submitted...The expected names are
npmoserver_newww_1
,npmoserver_policyfollower_1
….Question
cAdvisor
use to send toinfluxdb
?cAdvisor Version
Using the v0.20.5 version.
The text was updated successfully, but these errors were encountered: