-
Notifications
You must be signed in to change notification settings - Fork 148
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
[Questions] carbonapi have different tags object in response #755
Comments
This might be a bug, potentially introduced here d77e3ee#diff-fce0198985d6dad323115ac9f864bab245cb25e6b06dd228c901e92e6a590b71 The carbonapi/expr/functions/aliasByNode/function.go Lines 47 to 48 in 236726c
However, it looks like that was introduced in |
I have a build which say on the start in journalctl v0.15.6-296-g0bb2. but is there already. |
I've submitted a PR that should solve the issue. |
this bug is still around in latest 0.16.1 additional info:
this one are without tags:
with older versions 0.15.5 works ok. requested new bug here #808 |
Problem description
Have been used carbonapi for requests from grafana to clickhouse server (graphite-clickhouse inbetween).
After update to newer version noticed what response json become different
Old version request (working as inteded):
Old version response (working as inteded):
New version request is the same as older version. New version response also the same. BUT if I put to a request aliasByTags function - tags object in response are different for old and new versions.
Request:
Old version response:
New version response:
in my case tags list are matter. How can I return back old tags oject result? any config options?
carbonapi's version
v 0.15.6 and later - working with issue. tried different versions, newest included
v 0.15.5 and less - working as intended
Does this happened before
No. After
carbonapi's config
Both versions have the same config file:
backend software and config
graphite-clickhouse 0.12.0
clickhouse-server 22.8.4.7 (official build)
carbonapi performance metrics
Query that causes problems
Additional context
The text was updated successfully, but these errors were encountered: