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
Embed metrics into structs and optional initialization #1512
Comments
I support this idea; came here to add that we have some other metrics that come in via |
Relevant Design Document: https://docs.google.com/document/d/100HSvgvaswVR96Bmz2BWIL3d9ds6wqNTVI7_vESgOtE/edit?usp=sharing |
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
I think the solution we've already started adopting is to pass |
This issue has been automatically marked as stale because it has not had any activity in the past 60 days. It will be closed in 15 days if no further activity occurs. Thank you for your contributions. |
This issue says not to use This one got closed as stale; does that mean |
I think we can close this issue. The pattern we're currently using (and looks working fine with downstream projects) is to take the |
Agreed: if we create the metrics in Nitpick: the key is we are creating metrics via |
The single binary version of cortex ends up reporting metrics for each component in cortex regardless of whether the module is enabled or not. At this point it would make sense to start embedding metrics into structs so that the initialization of those metrics is actually dependent on whether that module is deployed or not.
This can be done piecemeal one module or package at a time.
The text was updated successfully, but these errors were encountered: