-
Deprecated ClassesClassDescriptionThis 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/use
DiskSpaceMetricsinstead.useKafkaClientMetricsinstead since 1.4.0
-
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.1.2 in favor ofHibernateMetrics.monitor(MeterRegistry, SessionFactory, String, Iterable)since 1.1.2 in favor ofHibernateMetrics.monitor(MeterRegistry, SessionFactory, String, String...)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.since 1.1.2 in favor of
HibernateMetrics(SessionFactory, String, Iterable)UseCountAtBucket(double, double)instead since 1.4.0.
TimedHandlerinstead.