Deprecated API

Contents

• Classes
• Exceptions
• Fields
• Methods
• Constructors

Classes

Class	Description
io.micrometer.core.instrument.binder.jetty.JettyStatisticsMetrics	Since 1.4.0. Use TimedHandler instead.
io.micrometer.core.instrument.binder.jpa.HibernateMetrics	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/
io.micrometer.core.instrument.binder.jpa.HibernateQueryMetrics	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/
io.micrometer.core.instrument.binder.kafka.KafkaConsumerMetrics	use KafkaClientMetrics instead since 1.4.0

Exceptions

Exceptions	Description
io.micrometer.core.instrument.config.MissingRequiredConfigurationException	since 1.5.0 replaced with Validated API.

Fields

Field	Description
io.micrometer.core.instrument.binder.httpcomponents.MicrometerHttpRequestExecutor.DEFAULT_URI_PATTERN_HEADER	use DefaultUriMapper.URI_PATTERN_HEADER since 1.4.0

Methods

Method	Description
io.micrometer.core.instrument.AbstractTimerBuilder.sla(Duration...)	Use {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.
io.micrometer.core.instrument.binder.db.MetricsDSLContext.bind(QueryPart, PreparedStatement)
io.micrometer.core.instrument.binder.db.MetricsDSLContext.bindContext(PreparedStatement)
io.micrometer.core.instrument.binder.db.MetricsDSLContext.renderContext()
io.micrometer.core.instrument.binder.jpa.HibernateMetrics.monitor(MeterRegistry, EntityManagerFactory, String, Iterable<Tag>)	since 1.1.2 in favor of HibernateMetrics.monitor(MeterRegistry, SessionFactory, String, Iterable)
io.micrometer.core.instrument.binder.jpa.HibernateMetrics.monitor(MeterRegistry, EntityManagerFactory, String, String...)	since 1.1.2 in favor of HibernateMetrics.monitor(MeterRegistry, SessionFactory, String, String...)
io.micrometer.core.instrument.config.MeterFilter.maxExpected(String, long)	Use MeterFilter.maxExpected(String, double) instead since 1.4.0.
io.micrometer.core.instrument.config.MeterFilter.minExpected(String, long)	Use MeterFilter.minExpected(String, double) instead since 1.4.0.
io.micrometer.core.instrument.distribution.DistributionStatisticConfig.Builder.maximumExpectedValue(Long)	Use DistributionStatisticConfig.Builder.maximumExpectedValue(Double) instead since 1.4.0.
io.micrometer.core.instrument.distribution.DistributionStatisticConfig.Builder.minimumExpectedValue(Long)	Use DistributionStatisticConfig.Builder.minimumExpectedValue(Double) instead since 1.4.0.
io.micrometer.core.instrument.distribution.DistributionStatisticConfig.Builder.sla(double...)	Use DistributionStatisticConfig.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.
io.micrometer.core.instrument.distribution.DistributionStatisticConfig.Builder.sla(long...)	Use DistributionStatisticConfig.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.
io.micrometer.core.instrument.distribution.DistributionStatisticConfig.getMaximumExpectedValue()	Use DistributionStatisticConfig.getMaximumExpectedValueAsDouble(). If you use this method, your code will not be compatible with code that uses Micrometer 1.3.x.
io.micrometer.core.instrument.distribution.DistributionStatisticConfig.getMinimumExpectedValue()	Use DistributionStatisticConfig.getMinimumExpectedValueAsDouble(). If you use this method, your code will not be compatible with code that uses Micrometer 1.3.x.
io.micrometer.core.instrument.distribution.DistributionStatisticConfig.getSlaBoundaries()	Use DistributionStatisticConfig.getServiceLevelObjectiveBoundaries(). If you use this method, your code will not be compatible with code that uses Micrometer 1.4.x and later.
io.micrometer.core.instrument.distribution.HistogramSupport.takeSnapshot(boolean)	Use HistogramSupport.takeSnapshot().
io.micrometer.core.instrument.DistributionSummary.Builder.maximumExpectedValue(Long)	Use DistributionSummary.Builder.maximumExpectedValue(Double) instead since 1.4.0.
io.micrometer.core.instrument.DistributionSummary.Builder.minimumExpectedValue(Long)	Use DistributionSummary.Builder.minimumExpectedValue(Double) instead since 1.4.0.
io.micrometer.core.instrument.DistributionSummary.Builder.sla(double...)	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.
io.micrometer.core.instrument.DistributionSummary.Builder.sla(long...)	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.
io.micrometer.core.instrument.DistributionSummary.histogramCountAtValue(long)	Use HistogramSupport.takeSnapshot() to retrieve bucket counts.
io.micrometer.core.instrument.DistributionSummary.percentile(double)	Use HistogramSupport.takeSnapshot() to retrieve percentiles.
io.micrometer.core.instrument.LongTaskTimer.duration(long, TimeUnit)	Use LongTaskTimer.Sample.duration(TimeUnit). As of 1.5.0, this always returns -1 as tasks no longer have IDs.
io.micrometer.core.instrument.LongTaskTimer.stop(long)	Use LongTaskTimer.Sample.stop(). As of 1.5.0, this always returns -1 as tasks no longer have IDs.
io.micrometer.core.instrument.MeterRegistry.newLongTaskTimer(Meter.Id)	Implement MeterRegistry.newLongTaskTimer(Meter.Id, DistributionStatisticConfig) instead.
io.micrometer.core.instrument.push.PushMeterRegistry.start()	Use PushMeterRegistry.start(ThreadFactory) instead.
io.micrometer.core.instrument.push.PushRegistryConfig.connectTimeout()	Connect timeout and read timeout have different meanings depending on the HTTP client. Configure timeout options on your HttpSender of choice instead.
io.micrometer.core.instrument.push.PushRegistryConfig.numThreads()	since 1.1.13 because this configuration is not used
io.micrometer.core.instrument.push.PushRegistryConfig.readTimeout()	Connect timeout and read timeout have different meanings depending on the HTTP client. Configure timeout options on your HttpSender of choice instead.
io.micrometer.core.instrument.Timer.histogramCountAtValue(long)	Use HistogramSupport.takeSnapshot() to retrieve bucket counts.
io.micrometer.core.instrument.Timer.percentile(double, TimeUnit)	Use HistogramSupport.takeSnapshot() to retrieve bucket counts.
io.micrometer.core.instrument.util.DoubleFormat.decimalOrWhole(double)	since 1.0.11 in favour of DoubleFormat.wholeOrDecimal(double)
io.micrometer.core.instrument.util.TimeUtils.simpleParse(String)	Use DurationValidator.validate(String, String) instead since 1.5.0.

Constructors

Constructor	Description
io.micrometer.core.instrument.AbstractTimer(Meter.Id, Clock, DistributionStatisticConfig, PauseDetector, TimeUnit)	Timer 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.
io.micrometer.core.instrument.binder.jpa.HibernateMetrics(EntityManagerFactory, String, Iterable<Tag>)	since 1.1.2 in favor of HibernateMetrics(SessionFactory, String, Iterable)
io.micrometer.core.instrument.cumulative.CumulativeDistributionSummary(Meter.Id, Clock, DistributionStatisticConfig, double)
io.micrometer.core.instrument.distribution.CountAtBucket(long, double)	Use CountAtBucket(double, double) instead since 1.4.0.
io.micrometer.core.instrument.internal.DefaultLongTaskTimer(Meter.Id, Clock)	Use DefaultLongTaskTimer(Meter.Id, Clock, TimeUnit, DistributionStatisticConfig, boolean) instead.