Skip to content
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

handle remote storage openTSDB error response correctly. #1621

Closed
guanglinlv opened this Issue May 10, 2016 · 4 comments

Comments

Projects
None yet
4 participants
@guanglinlv
Copy link

guanglinlv commented May 10, 2016

Hi folks,

when then openTSDB return a error response with 400 status code. it looks like the following with different request:

  • /api/put
{
   "error" : {
         "code": 400,
         "details": "Please seen the TSD logs or append \"details\" to the put request",
         "message": "one or more data points had errors",
         "trace": ".........."
    }
}
  • /api/put?summary
{
    "failed": 1,
    "success": 1
}

i think the second output is what we need. otherwise the client.go#L127 will report a error. we should change the putEndpoint const to /api/put?summary.

more details on /api/put, see http://opentsdb.net/docs/build/html/api_http/put.html

thanks.

@guanglinlv

This comment has been minimized.

Copy link
Author

guanglinlv commented May 11, 2016

aha, it is not need to change the putEndpoint, i can set the prometheus -storage.remote.opentsdb-url=http://opentsdb-host:4242/?summary , then opentsdb's response is

HTTP/1.1 200 OK
.
{
    "failed": 0,
    "success": 100
}

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

incorrect

@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented May 12, 2016

See also #1061

@grobie

This comment has been minimized.

Copy link
Member

grobie commented Nov 12, 2017

OpenTSDB support has been removed. Use a remote storage adapter.

@grobie grobie closed this Nov 12, 2017

@lock

This comment has been minimized.

Copy link

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 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.
You can’t perform that action at this time.