-
Notifications
You must be signed in to change notification settings - Fork 32
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" #165
Comments
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? |
Nope. I've seen this before but I'm not sure what the cause was. Is it
still happening?
…On Jan 11, 2017 4:40 PM, "Vaughn Dice" ***@***.***> wrote:
Hmmm, I'm not able to reproduce this issue w/ same telegraf image (also
GKE, k8s server 1.4.7)
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.
@jchauncey <https://github.com/jchauncey> any suggestions on how to debug?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#165 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAaRGG44WRs6bIBsrBRaYhCJH2f-7BPGks5rRUxLgaJpZM4LLgQt>
.
|
@jchauncey yes, it's still happen.
|
@zinuzoid I encounter a similar issue. Telegraf is using |
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. |
This issue was moved to teamhephy/monitor#9 |
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.
The text was updated successfully, but these errors were encountered: