-
Notifications
You must be signed in to change notification settings - Fork 453
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
An aggregate namespace who write data to it #2194
Comments
It is aggregated in m3coordinator, and sent to aggregated namespaces in the dbnode |
I have been looking at the code of m3coordinator recently, some places are not very understandable。 consumeLocalMetric
-->consum -->processValueWithAggregationLock
then finally call this to write to dbnode
|
Hey @ning1875 apologies for getting back to you late. So right now by default the aggregation is always "last" value, you can use mapping rules to choose different aggregations: This PR will then allow for adding tags per mapping rule so you can differentiate them as you need #2414. We'll update the docs on this to make more clear. |
here is my usage :promethues remote write to m3coordinator then write to m3dbnode 。And my question is that : Is it written to m3db after m3coordinator aggregation, or is it aggregated by m3db itself?
The text was updated successfully, but these errors were encountered: