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
Generic error status codes #145
Comments
We don't have the notion of error 'code', we simply have error messages. All the errors you mention have different messages. |
Do you mean you would like to have an additional notion of error 'code' returned as an HTTP header which could differentiate some specific errors? |
Yes, It could be either an HTTP header or a json payload (or even simple plain text...) Some HTTP status codes could be affected to common errors : 206 Partial Content // parsing error, some data points accepted, but not the whole dataset |
Any news? |
Ping |
Error codes formatting have recently changed, breaking parsing and putting this subject back on table. |
Since Warp10 use an HTTP API it should be great to use it at 100% |
What do you mean? |
Many errors have the same return code :
It would be nice to have a fine grained error status codes so that we can better catch the source of the issue.
The text was updated successfully, but these errors were encountered: