From 0b2ea9367a1ea84f59d015f301fe5c16d4635bfc Mon Sep 17 00:00:00 2001 From: Binbin Date: Tue, 7 Jan 2025 19:19:21 +0800 Subject: [PATCH] Remove extra spaces in words `reset LatenciesAfterEvent` should be `resetLatenciesAfterEvent`. `ev entEmitIntervalUnit` should be `eventEmitIntervalUnit`. Other than that, diff is all table formatting. --- docs/advanced-usage.md | 40 ++++++++++++++++++++-------------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/docs/advanced-usage.md b/docs/advanced-usage.md index 19e8c2b9d..a07d8ccd9 100644 --- a/docs/advanced-usage.md +++ b/docs/advanced-usage.md @@ -1338,32 +1338,32 @@ RedisClient client = RedisClient.create(res); The following settings are available to configure from `DefaultCommandLatencyCollectorOptions`: -| Name | Method | Default | -|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|---------------------------------| -| **Disable metrics tracking** | `disable` | `false` | -| Disables tracking of command latency metrics. | | | -| **Latency time unit** | `targetUnit` | `MICROSECONDS` | -| The target unit for command latency values. All values in the `CommandLatencyEvent` and a `CommandMetrics` instance are `long` values scaled to the `targetUnit`. | | | -| **Latency percentiles** | `targetPercentiles` | `50.0, 90 .0, 95.0, 99.0, 99.9` | -| A `double`-array of percentiles for latency metrics. The `CommandMetrics` contains a map that holds the percentile value and the latency value according to the percentile. Note that percentiles here must be specified in the range between 0 and 100. | | | -| **Reset latencies after publish** | `reset LatenciesAfterEvent` | `true` | -| Allows controlling whether the latency metrics are reset to zero one they were published. Setting `reset LatenciesAfterEvent` allows accumulating metrics over a long period for long-term analytics. | | | -| **Local socket distinction** | `localDistinction` | `false` | -| Enables per connection metrics tracking instead of per host/port. If `true`, multiple connections to the same host/connection point will be recorded separately which allows to inspection of every connection individually. If `false`, multiple connections to the same host/connection point will be recorded together. This allows a consolidated view on one particular service. | | | +| Name | Method | Default | +|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------|---------------------------------| +| **Disable metrics tracking** | `disable` | `false` | +| Disables tracking of command latency metrics. | | | +| **Latency time unit** | `targetUnit` | `MICROSECONDS` | +| The target unit for command latency values. All values in the `CommandLatencyEvent` and a `CommandMetrics` instance are `long` values scaled to the `targetUnit`. | | | +| **Latency percentiles** | `targetPercentiles` | `50.0, 90 .0, 95.0, 99.0, 99.9` | +| A `double`-array of percentiles for latency metrics. The `CommandMetrics` contains a map that holds the percentile value and the latency value according to the percentile. Note that percentiles here must be specified in the range between 0 and 100. | | | +| **Reset latencies after publish** | `resetLatenciesAfterEvent` | `true` | +| Allows controlling whether the latency metrics are reset to zero one they were published. Setting `resetLatenciesAfterEvent` allows accumulating metrics over a long period for long-term analytics. | | | +| **Local socket distinction** | `localDistinction` | `false` | +| Enables per connection metrics tracking instead of per host/port. If `true`, multiple connections to the same host/connection point will be recorded separately which allows to inspection of every connection individually. If `false`, multiple connections to the same host/connection point will be recorded together. This allows a consolidated view on one particular service. | | | #### EventPublisher Options The following settings are available to configure from `DefaultEventPublisherOptions`: -| Name | Method | Default | -|---------------------------------------------------|--------------------------|-----------| -| **Disable event publisher** | `disable` | `false` | -| Disables event publishing. | | | -| **Event publishing time unit** | `ev entEmitIntervalUnit` | `MINUTES` | -| The `TimeUnit` for the event publishing interval. | | | -| **Event publishing interval** | `eventEmitInterval` | `10` | -| The interval for the event publishing. | | | +| Name | Method | Default | +|---------------------------------------------------|-------------------------|-----------| +| **Disable event publisher** | `disable` | `false` | +| Disables event publishing. | | | +| **Event publishing time unit** | `eventEmitIntervalUnit` | `MINUTES` | +| The `TimeUnit` for the event publishing interval. | | | +| **Event publishing interval** | `eventEmitInterval` | `10` | +| The interval for the event publishing. | | | ### Micrometer