mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-10-31 02:28:09 +00:00
f4f0412b6a
* Convert documentation titles to sentense case * Docker, Google, Foundry, Cloud proper case
47 lines
1.4 KiB
Plaintext
47 lines
1.4 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Log Completed Requests - Configuration
|
|
description: |-
|
|
Vault can be configured to log completed requests.
|
|
---
|
|
|
|
# Log completed requests
|
|
|
|
Vault can be configured to log completed requests using the `log_requests_level` configuration parameter.
|
|
|
|
## Activating logging completed requests
|
|
|
|
By default, logging completed requests is disabled. To activate request logging, set the `log_requests_level`
|
|
configuration option in the Vault server configuration to the desired logging level. The acceptable logging levels are
|
|
`error`, `warn`, `info`, `debug`, `trace`, and `off`, which is the default.
|
|
|
|
Completed requests will be logged at the configured level, if Vault's log level includes this level of logs. For
|
|
example, if `log_level` is set to `debug`, but `log_requests_level` is set to `trace`, completed requests will
|
|
not be logged.
|
|
|
|
If the Vault server is already running, you can still configure the parameter in the Vault server configuration,
|
|
and then send a `SIGHUP` signal to the Vault process.
|
|
|
|
```hcl
|
|
log_requests_level = "debug"
|
|
log_level = "debug"
|
|
|
|
listener "tcp" {
|
|
# ...
|
|
}
|
|
```
|
|
|
|
## Deactivating logging completed requests
|
|
|
|
To deactivate logging completed requests, simply remove the `log_requests_level` configuration parameter
|
|
from the Vault server configuration, or set it to `off`, and send a `SIGHUP` signal to the Vault process.
|
|
|
|
```hcl
|
|
log_requests_level = "off"
|
|
log_level = "debug"
|
|
|
|
listener "tcp" {
|
|
# ...
|
|
}
|
|
```
|