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 uphandle remote storage openTSDB error response correctly. #1621
Comments
This comment has been minimized.
This comment has been minimized.
|
aha, it is not need to change the
however, client.go#L115 compare the status code with 204. actually it is 200. then, a incorrect error will report at queue_manager.go#L194-L198 |
This comment has been minimized.
This comment has been minimized.
|
See also #1061 |
brian-brazil
added
the
kind/bug
label
Jul 13, 2016
brian-brazil
added
help wanted
priority/P3
component/remote storage
low hanging fruit
and removed
help wanted
labels
Jul 14, 2017
gouthamve
added
the
hacktoberfest
label
Sep 28, 2017
This comment has been minimized.
This comment has been minimized.
|
OpenTSDB support has been removed. Use a remote storage adapter. |
grobie
closed this
Nov 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 23, 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 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.

guanglinlv commentedMay 10, 2016
•
edited
Hi folks,
when then openTSDB return a error response with
400status code. it looks like the following with different request:/api/put/api/put?summaryi think the second output is what we need. otherwise the client.go#L127 will report a error. we should change the
putEndpointconst to/api/put?summary.more details on
/api/put, see http://opentsdb.net/docs/build/html/api_http/put.htmlthanks.