[jira] [Updated] (SOLR-18172) Declare OTEL metrics as BETA in Solr 10
[ https://issues.apache.org/jira/browse/SOLR-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Høydahl updated SOLR-18172: --- Component/s: documentation > Declare OTEL metrics as BETA in Solr 10 > --- > > Key: SOLR-18172 > URL: https://issues.apache.org/jira/browse/SOLR-18172 > Project: Solr > Issue Type: Bug > Components: documentation, metrics >Reporter: Jan Høydahl >Assignee: Jan Høydahl >Priority: Major > Labels: pull-request-available > Fix For: 10.0 > > Time Spent: 1h > Remaining Estimate: 0h > > Ref discussion > [https://lists.apache.org/thread/0d7fp80p39tfn95kdbq0fychjd1lsbl2] > In 10.0 we shipped a brand new metrics system powered by OTEL > instrumentation. It has diferent metric names, and is not backward compatible > with the solr exporter from 9.x > We are in the process of building some Grafana boards for it, which uncover > needs for some changes. > We decided to change internal and OTLP metric names from underscore to dot > separators (https://github.com/apache/solr/pull/4223) to align with OTEL > semantic conventions. > We found two metrics that are pure duplicates with different names. > Clearly, there is a need for some changes and stabilization of this brand new > feature. > Looking back we should have declared the feature as BETA and experimental in > 10.0, but we did not. > I therefore propose that we declare it a BETA feature now, by adding a > disclaimer in Ref Guide and send an [ANNOUNCE] email to the lists. > As 10.0 is still brand new and likely not yet in production many places, and > even fewer depending on the new metrics names, we could retroactively delcare > it BETA from version 10.0. > That will allow us to tweak things in the next few minor versions. Perhaps we > want to rename a few metrics with better names. Perhaps some need to change > slightly. > It is unfortunate to do such things after a release, but it is better to do > it now when 19.0 is still fresh. The longer we wait the harder to justify > changes. > If the PMC agrees (I don't think we need a vote), I can draft an announce > mail and a PR against branch_10_0 ref guide. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
[jira] [Updated] (SOLR-18172) Declare OTEL metrics as BETA in Solr 10
[ https://issues.apache.org/jira/browse/SOLR-18172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated SOLR-18172: -- Labels: pull-request-available (was: ) > Declare OTEL metrics as BETA in Solr 10 > --- > > Key: SOLR-18172 > URL: https://issues.apache.org/jira/browse/SOLR-18172 > Project: Solr > Issue Type: Bug > Components: metrics >Reporter: Jan Høydahl >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Ref discussion > [https://lists.apache.org/thread/0d7fp80p39tfn95kdbq0fychjd1lsbl2] > In 10.0 we shipped a brand new metrics system powered by OTEL > instrumentation. It has diferent metric names, and is not backward compatible > with the solr exporter from 9.x > We are in the process of building some Grafana boards for it, which uncover > needs for some changes. > We decided to change internal and OTLP metric names from underscore to dot > separators (https://github.com/apache/solr/pull/4223) to align with OTEL > semantic conventions. > We found two metrics that are pure duplicates with different names. > Clearly, there is a need for some changes and stabilization of this brand new > feature. > Looking back we should have declared the feature as BETA and experimental in > 10.0, but we did not. > I therefore propose that we declare it a BETA feature now, by adding a > disclaimer in Ref Guide and send an [ANNOUNCE] email to the lists. > As 10.0 is still brand new and likely not yet in production many places, and > even fewer depending on the new metrics names, we could retroactively delcare > it BETA from version 10.0. > That will allow us to tweak things in the next few minor versions. Perhaps we > want to rename a few metrics with better names. Perhaps some need to change > slightly. > It is unfortunate to do such things after a release, but it is better to do > it now when 19.0 is still fresh. The longer we wait the harder to justify > changes. > If the PMC agrees (I don't think we need a vote), I can draft an announce > mail and a PR against branch_10_0 ref guide. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
