Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upIncorrect parsing of OpenTSDB failures #1061
Comments
This comment has been minimized.
This comment has been minimized.
|
Thanks for reporting! We currnetly don't have an OpenTSDB around for testing, but happy to accept fixes! |
brian-brazil
added
the
bug
label
Dec 16, 2015
fabxc
added
kind/bug
and removed
bug
labels
Apr 28, 2016
brian-brazil
referenced this issue
May 12, 2016
Closed
handle remote storage openTSDB error response correctly. #1621
This comment has been minimized.
This comment has been minimized.
|
This code is about to be removed, so this is obsolete. |
brian-brazil
closed this
Feb 13, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
swsnider commentedSep 8, 2015
When OpenTSDB 2.1.0 fails to record timeseries, it seems to always return the errors array, even if summary output is specifically requested. Since this is not an
int, prometheus returns a json error spuriously, from https://github.com/prometheus/prometheus/blob/master/storage/remote/opentsdb/client.go#L131