-
Notifications
You must be signed in to change notification settings - Fork 107
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
4 zeros inserted after some metrics #218
Comments
feels like a bug to me |
The only (big) change between v2.0 and v2.1 is optimiser changes, how many rules do you have in your config? |
I have cca 90 rewrite rules and 10 aggregation rules. |
I did some testing. This thing starts happening when I have 39 rewrite rules or more. If I disable one, so I only have 38 rewrite rules, it starts working. It is rewrite rule specific, because if I disable aggregation rule and still keep 39 rewrite rules, it still doesn't work. I dropped the output of carbon-c-relay into wireshark and this is what I see: 39 rules:
38 rules:
It looks like when there are more then 38 rules, carbon-c-relay for some reason drops one zero out of metric value. |
do you have means to edit the sources and compile? In that case it would be interesting if you could disable the optimisation, that is remove the calls to router_optimise() in relay.c |
Will try to do that later today and report back |
thanks a lot! |
After removing router_optimise(), it works as it should |
Ok, that's good (and bad for me) news. I know where to look now. |
I'm glad I could be of help. I wish I could do more, but C ain't my thing:) |
Because rewrites change the metric in-place (scary, but unavoidable in current scheme) group indirection cause conflicts. Perhaps this can be solved but disable the grouping for now.
You could help me by testing the last commit to see if it works for you. I'm affraid we can't really group rewrites, since they potentially rewrite to something that would be matched by something else in the same group. |
I think this will help, please reopen if it doesn't. |
I can confirm it now works. Thanks for the fix. |
Hello,
today I have noticed that I'm not receiving some aggregated and renamed metrics. I took a look at the thing I found out that for some reason, carbon-c-relay adds 4 zeros at the end of some metrics
Config example:
If I look at the output of carbon-c-relay with ngrep, I get metrics like:
The leading
0000
are breaking the metrics format and graphite doesn't want to save them.I tried different versions of carbon-c-relay and it works OK on v2.0, but breaks on v2.1 and v2.2.
Is there something wrong with my config or is it a bug?
The text was updated successfully, but these errors were encountered: