I'm okay with removing the `maximum: 100` restriction in the metrics schema for the custom distribution to allow glean_parser to generate these, or to set it to an arbitrarily high number that will accommodate the use cases above (how about 1k or 1024 if you prefer powers of 2). The lint seems more annoying than it's worth as I don't see the bucket count really being abused by anyone, nor do I know the potential harm such abuse would cause? You might want to double check that the probe-scraper, GLAM, or any other downstream tooling that might have adopted the 100 bucket concept as being fixed. I don't think there would be any requirements, but maybe some assumptions have been made around the custom distributions for convenience. proposal-r+
Bug 1940967 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I'm okay with removing the `maximum: 100` restriction in the metrics schema for the custom distribution to allow glean_parser to generate these, or to set it to an arbitrarily high number that will accommodate the use cases above (how about 1k or 1024 if you prefer powers of 2). The lint seems more annoying than it's worth as I don't see the bucket count really being abused by anyone, nor do I know the potential harm such abuse would cause? You might want to double check that the probe-scraper, GLAM, or any other downstream tooling that might have adopted the 100 bucket concept as being fixed. I don't think there would be any requirements, but maybe some assumptions have been made around the custom distributions for convenience. proposal r+