-
Notifications
You must be signed in to change notification settings - Fork 7
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
[telegraf] Error parsing response: parsing time "null" #9
Comments
From @vdice on January 11, 2017 21:40 Hmmm, I'm not able to reproduce this issue w/ same telegraf image (also GKE, k8s server 1.4.7)
@jchauncey any suggestions on how to debug? |
From @jchauncey on January 11, 2017 21:45 Nope. I've seen this before but I'm not sure what the cause was. Is it On Jan 11, 2017 4:40 PM, "Vaughn Dice" notifications@github.com wrote:
|
From @zinuzoid on January 12, 2017 11:1 @jchauncey yes, it's still happen.
|
From @stuszynski on February 6, 2017 15:0 @zinuzoid I encounter a similar issue. Telegraf is using |
From @stuszynski on February 7, 2017 12:38 Sorry, my bad. The
I check it manually and I'm sure it provide data on this URL from a telegraf container. We still, however, experience above issue. |
From @zinuzoid on December 13, 2016 9:23
Metric in Grafana seems doesn't work, so I check telegraf and there're some error logs from pods.
I'm running cluster in GKE k8s version 1.4.6
Images: quay.io/deis/telegraf:v2.7.0
Is there a way to dig it deeper. I did try to add AGENT_DEBUG:true, AGENT_QUITE:false but doesn't help much from log.
Copied from original issue: deis/monitor#165
The text was updated successfully, but these errors were encountered: