Deprecated API
Contents
-
Deprecated PackagesPackageDescriptionsince 1.13.0 use the jersey-micrometer module in the Jersey project instead
-
Deprecated InterfacesInterfaceDescriptionas of 1.12.0 in favor of HttpComponents 5.x and
ApacheHttpClientObservationConvention.since 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 in favor of the micrometer-jetty12 modulesince 1.13.0 in favor of the micrometer-jetty12 modulePlease useInternalLoggerinstead.
-
Deprecated ClassesClassDescriptionas of 1.12.0 in favor of HttpComponents 5.x and
ApacheHttpClientContext.as of 1.12.0 in favor of HttpComponents 5.x andApacheHttpClientObservationConvention.as of 1.12.5 in favor of anHttpClientContextvalue withApacheHttpClientObservationConvention.URI_TEMPLATE_ATTRIBUTEas key name.as of 1.12.0 in favor of anHttpClientContextvalue withApacheHttpClientObservationConvention.URI_TEMPLATE_ATTRIBUTEas key name.since 1.12.0 in favor ofObservationExecChainHandler.since 1.12.0 in favor ofObservationExecChainHandler.as of 1.12.0 in favor of HttpComponents 5.x andObservationExecChainHandler.as of 1.12.0 in favor of HttpComponents 5.x andObservationExecChainHandler.as of 1.12.5 in favor of HttpComponents 5.x andPoolingHttpClientConnectionManagerMetricsBinder.since 1.13.0, Hystrix is no longer in active development, and is currently in maintenance mode.since 1.13.0, Hystrix is no longer in active development, and is currently in maintenance mode.since 1.13.0, Hystrix is no longer in active development, and is currently in maintenance mode.since 1.13.0, Hystrix is no longer in active development, and is currently in maintenance mode.since 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 in favor of the micrometer-jetty12 modulesince 1.13.0 in favor of the micrometer-jetty12 modulesince 1.13.0 in favor of the micrometer-jetty12 modulesince 1.13.0 in favor of the micrometer-jetty12 modulesince 1.13.0 in favor of the micrometer-jetty12 moduleSince 1.4.0. UseTimedHandlerinstead.since 1.13.0 in favor ofTimedHandlerin the micrometer-jetty12 moduleThis implementation is deprecated in favor of the MeterBinder maintained as part of the Hibernate project as of version 5.4.26. See https://mvnrepository.com/artifact/org.hibernate/hibernate-micrometer/This implementation is deprecated in favor of the MeterBinder maintained as part of the Hibernate project as of version 5.4.26. See https://mvnrepository.com/artifact/org.hibernate/hibernate-micrometer/useDiskSpaceMetricsinstead.useKafkaClientMetricsinstead since 1.4.0Please useStringUtilsinstead.Please useAbstractInternalLoggerinstead.Please useInternalLoggerFactoryinstead.Please useio.micrometer.common.util.internal.logging.JdkLoggerinstead.Please useSlf4JLoggerFactoryinstead.Please useWarnThenDebugLoggerinstead.
-
Deprecated Enum ClassesEnum ClassDescriptionas of 1.12.0 in favor of HttpComponents 5.x and
ApacheHttpClientObservationDocumentation.since 1.13.0 use the jersey-micrometer module in the Jersey project insteadsince 1.13.0 in favor of the micrometer-jetty12 modulePlease useInternalLogLevelinstead.
-
Deprecated Exception Classes
-
Deprecated Fields
-
Deprecated MethodsMethodDescriptionUse {
AbstractTimerBuilder.serviceLevelObjectives(Duration...)} instead. "Service Level Agreement" is more formally the agreement between an engineering organization and the business. Service Level Objectives are set more conservatively than the SLA to provide some wiggle room while still satisfying the business requirement. SLOs are the threshold we intend to measure against, then.since 1.12.0 in favor ofHttpJakartaServletRequestTags.method(jakarta.servlet.http.HttpServletRequest)since 1.12.0 in favor ofHttpJakartaServletRequestTags.outcome(jakarta.servlet.http.HttpServletResponse)since 1.12.0 in favor ofHttpJakartaServletRequestTags.status(jakarta.servlet.http.HttpServletResponse)as of 1.12.0 in favor ofApacheHttpClientContext.getHttpClientContext().as of 1.12.0 in favor of anHttpClientContextattribute.as of 1.12.0 with no replacement.since 1.11.0 in favor ofJettyClientMetrics.builder(MeterRegistry, BiFunction);JettyClientMetrics.Builder.tagsProvider(JettyClientTagsProvider)can be used to provide a custom tags providersince 1.11.0 in favor ofJettyClientMetrics.builder(MeterRegistry, BiFunction)to configure the uri pattern functionsince 1.1.2 in favor ofHibernateMetrics.monitor(MeterRegistry, SessionFactory, String, Iterable)since 1.1.2 in favor ofHibernateMetrics.monitor(MeterRegistry, SessionFactory, String, String...)Should not be needed anymore sinceLogbackMetricsrecords logback events asynchronously and should not get into an infinite loop.UseMeterFilter.maxExpected(String, double)instead since 1.4.0.UseMeterFilter.minExpected(String, double)instead since 1.4.0.UseDistributionStatisticConfig.Builder.maximumExpectedValue(Double)instead since 1.4.0.UseDistributionStatisticConfig.Builder.minimumExpectedValue(Double)instead since 1.4.0.UseDistributionStatisticConfig.Builder.serviceLevelObjectives(double...)instead. "Service Level Agreement" is more formally the agreement between an engineering organization and the business. Service Level Objectives are set more conservatively than the SLA to provide some wiggle room while still satisfying the business requirement. SLOs are the threshold we intend to measure against, then.UseDistributionStatisticConfig.Builder.serviceLevelObjectives(double...)instead. "Service Level Agreement" is more formally the agreement between an engineering organization and the business. Service Level Objectives are set more conservatively than the SLA to provide some wiggle room while still satisfying the business requirement. SLOs are the threshold we intend to measure against, then.UseDistributionStatisticConfig.getMaximumExpectedValueAsDouble(). If you use this method, your code will not be compatible with code that uses Micrometer 1.3.x.UseDistributionStatisticConfig.getMinimumExpectedValueAsDouble(). If you use this method, your code will not be compatible with code that uses Micrometer 1.3.x.UseDistributionStatisticConfig.getServiceLevelObjectiveBoundaries(). If you use this method, your code will not be compatible with code that uses Micrometer 1.4.x and later.UseDistributionSummary.Builder.maximumExpectedValue(Double)instead since 1.4.0.UseDistributionSummary.Builder.minimumExpectedValue(Double)instead since 1.4.0.Use {DistributionSummary.Builder.serviceLevelObjectives(double...)} instead. "Service Level Agreement" is more formally the agreement between an engineering organization and the business. Service Level Objectives are set more conservatively than the SLA to provide some wiggle room while still satisfying the business requirement. SLOs are the threshold we intend to measure against, then.Use {DistributionSummary.Builder.serviceLevelObjectives(double...)} instead. "Service Level Agreement" is more formally the agreement between an engineering organization and the business. Service Level Objectives are set more conservatively than the SLA to provide some wiggle room while still satisfying the business requirement. SLOs are the threshold we intend to measure against, then.UseHistogramSupport.takeSnapshot()to retrieve bucket counts.UseHistogramSupport.takeSnapshot()to retrieve percentiles.UseLongTaskTimer.Sample.duration(TimeUnit). As of 1.5.0, this always returns -1 as tasks no longer have IDs.UseLongTaskTimer.Sample.stop(). As of 1.5.0, this always returns -1 as tasks no longer have IDs.ImplementMeterRegistry.newLongTaskTimer(Meter.Id, DistributionStatisticConfig)instead.UsePushMeterRegistry.start(ThreadFactory)instead.Connect timeout and read timeout have different meanings depending on the HTTP client. Configure timeout options on yourHttpSenderof choice instead.since 1.1.13 because this configuration is not usedConnect timeout and read timeout have different meanings depending on the HTTP client. Configure timeout options on yourHttpSenderof choice instead.UseHistogramSupport.takeSnapshot()to retrieve bucket counts.UseHistogramSupport.takeSnapshot()to retrieve bucket counts.since 1.0.11 in favour ofDoubleFormat.wholeOrDecimal(double)UseDurationValidator.validate(String, String)instead since 1.5.0.
-
Deprecated ConstructorsConstructorDescriptionTimer implementations should now declare at construction time whether they support aggregable percentiles or not. By declaring it up front, Micrometer can memory optimize the histogram structure used to store distribution statistics.as of 1.12.0 in favor of
ApacheHttpClientContext(HttpRequest, HttpClientContext).since 1.11.0 in favor ofJettyClientMetrics.builder(MeterRegistry, BiFunction)since 1.1.2 in favor ofHibernateMetrics(SessionFactory, String, Iterable)UseCountAtBucket(double, double)instead since 1.4.0.useNoPauseDetector.INSTANCEinstead.since 1.16.0, useHighCardinalityTagsDetector.Builder.highCardinalityMeterInfoConsumer(Consumer)instead.