From 73f62ae0478c0ee444a095a41fe34ae7bb523689 Mon Sep 17 00:00:00 2001 From: akshya96 <87045294+akshya96@users.noreply.github.com> Date: Tue, 7 Feb 2023 11:26:38 -0800 Subject: [PATCH] adding emit duration for telemetry (#19027) --- website/content/docs/configuration/user-lockout.mdx | 2 +- website/content/docs/internals/telemetry.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/configuration/user-lockout.mdx b/website/content/docs/configuration/user-lockout.mdx index f76d31594c..1306c9aea4 100644 --- a/website/content/docs/configuration/user-lockout.mdx +++ b/website/content/docs/configuration/user-lockout.mdx @@ -59,7 +59,7 @@ or [auth tune api](/vault/api-docs/system/auth#tune-auth-method) for more detail ## `user_lockout` Parameters -The following options are available on all telemetry configurations. +The following options are available on all user_lockout configurations. - `lockout_threshold` `(string: "")` - Specifies the number of failed login attempts after which the user is locked out. - `lockout_duration` `(string: "")` - Specifies the duration for which an user will be locked out. diff --git a/website/content/docs/internals/telemetry.mdx b/website/content/docs/internals/telemetry.mdx index 9d0c293bc0..c764dc5bac 100644 --- a/website/content/docs/internals/telemetry.mdx +++ b/website/content/docs/internals/telemetry.mdx @@ -95,7 +95,7 @@ These metrics represent operational aspects of the running Vault instance. | `vault.core.leadership_setup_failed` | Duration of time taken by cluster leadership setup failures which have occurred in a highly available Vault cluster. This should be monitored and alerted on for overall cluster leadership status. | ms | summary | | `vault.core.leadership_lost` | The total duration that a HA cluster node maintained leadership as reported at the last time of loss. If metric is present and has a count greater than zero, that means a leadership change has occurred. Continuing changes or reports of low value could be a cause for monitoring alerts as they would typically imply ongoing flapping of leadership that may rotate between nodes. | ms | summary | | `vault.core.license.expiration_time_epoch` | Time as epoch (seconds since Jan 1 1970) at which license will expire. | seconds | gauge | -| `vault.core.locked_users` | Number of locked users in Vault. | locked users | gauge | +| `vault.core.locked_users` | Number of locked users in Vault. This measurement is performed every 15 minutes. | locked users | gauge | | `vault.core.mount_table.num_entries` | Number of mounts in a particular mount table. This metric is labeled by table type (auth or logical) and whether or not the table is replicated (local or not) | objects | gauge | | `vault.core.mount_table.size` | Size of a particular mount table. This metric is labeled by table type (auth or logical) and whether or not the table is replicated (local or not) | bytes | gauge | | `vault.core.post_unseal` | Duration of time taken by post-unseal operations handled by Vault core | ms | summary |