Spring/spring-boot
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Polish

Browse Source
This commit is contained in:
Andy Wilkinson
2020-04-23 11:49:07 +01:00
parent fe90b2a251
commit d05c973e71
4 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/metrics/MetricsProperties.java
View File

@@ -43,7 +43,7 @@ public class MetricsProperties {
private boolean useGlobalRegistry = true;
/**
* Whether meter IDs starting-with the specified name should be enabled. The longest
* Whether meter IDs starting with the specified name should be enabled. The longest
* match wins, the key `all` can also be used to configure all meters.
*/
private final Map<String, Boolean> enable = new LinkedHashMap<>();
@@ -233,7 +233,7 @@ public class MetricsProperties {
private final Map<String, double[]> percentiles = new LinkedHashMap<>();
/**
* Specific Service Level Objectives boundaries for meter IDs starting-with the
* Specific service-level objective boundaries for meter IDs starting with the
* specified name. The longest match wins. Counters will be published for each
* specified boundary. Values can be specified as a long or as a Duration value
* (for timer meters, defaulting to ms if no unit specified).
@@ -241,14 +241,14 @@ public class MetricsProperties {
private final Map<String, ServiceLevelObjectiveBoundary[]> slo = new LinkedHashMap<>();
/**
* Minimum value that meter IDs starting-with the specified name are expected to
* Minimum value that meter IDs starting with the specified name are expected to
* observe. The longest match wins. Values can be specified as a long or as a
* Duration value (for timer meters, defaulting to ms if no unit specified).
*/
private final Map<String, String> minimumExpectedValue = new LinkedHashMap<>();
/**
* Maximum value that meter IDs starting-with the specified name are expected to
* Maximum value that meter IDs starting with the specified name are expected to
* observe. The longest match wins. Values can be specified as a long or as a
* Duration value (for timer meters, defaulting to ms if no unit specified).
*/

6
spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/metrics/ServiceLevelAgreementBoundary.java
View File

@@ -21,9 +21,9 @@ import java.time.Duration;
import io.micrometer.core.instrument.Meter;
/**
* A service level agreement boundary for use when configuring Micrometer. Can be
* specified as either a {@link Long} (applicable to timers and distribution summaries) or
* a {@link Duration} (applicable to only timers).
* A boundary for a service-level agreement (SLA) for use when configuring Micrometer. Can
* be specified as either a {@link Long} (applicable to timers and distribution summaries)
* or a {@link Duration} (applicable to only timers).
*
* @author Phillip Webb
* @since 2.0.0

6
spring-boot-project/spring-boot-actuator-autoconfigure/src/main/java/org/springframework/boot/actuate/autoconfigure/metrics/ServiceLevelObjectiveBoundary.java
View File

@@ -21,9 +21,9 @@ import java.time.Duration;
import io.micrometer.core.instrument.Meter;
/**
* A service level objective boundary for use when configuring Micrometer. Can be
* specified as either a {@link Double} (applicable to timers and distribution summaries)
* or a {@link Duration} (applicable to only timers).
* A boundary for a service-level objective (SLO) for use when configuring Micrometer. Can
* be specified as either a {@link Double} (applicable to timers and distribution
* summaries) or a {@link Duration} (applicable to only timers).
*
* @author Phillip Webb
* @author Stephane Nicoll

2
spring-boot-project/spring-boot-docs/src/docs/asciidoc/production-ready-features.adoc
View File

@@ -2132,7 +2132,7 @@ The following properties allow per-meter customization:
| Publish percentile values computed in your application
| configprop:management.metrics.distribution.slo[]
| Publish a cumulative histogram with buckets defined by your Service Level Objectives.
| Publish a cumulative histogram with buckets defined by your service-level objectives.
|===
For more details on concepts behind `percentiles-histogram`, `percentiles` and `sla` refer to the {micrometer-concepts-docs}#_histograms_and_percentiles["Histograms and percentiles" section] of the micrometer documentation.