Files
threshold/website/content/docs/commands/cache/status.mdx
T
Dan HeathandRobin Beck b442c1fa60 docs: Update meta content - CLI (#5343)
* docs: Update meta content - CLI

* docs: Edits for consistency

* docs: More edits for consistency

* Apply batch of suggestions from code review

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>

* Apply batch suggestions from code review

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>

* docs: Remove given id references

* Update read.mdx

* Update read.mdx

---------

Co-authored-by: Robin Beck <stellarsquall@users.noreply.github.com>
2024-12-17 14:13:18 -05:00

53 lines
1.2 KiB
Plaintext

---
layout: docs
page_title: cache status - Command
description: >-
The "cache status" command checks the status of the Boundary cache and reports on configuration, user, and resource information.
---
# cache status
Command: `boundary cache status`
The `boundary cache status` command lets you manually check the status of the Boundary cache.
Boundary prints out a status report that includes configuration, user, and resource information.
## Example
The following command checks the status of the Boundary cache:
```shell-session
$ boundary cache status
```
**Example output:**
<CodeBlockConfig hideClipboard>
```plaintext
Status:
Domain Socket: /home/my_user/.boundary/socket/daemon.sock
Log Location: /home/my_user/.boundary/cache.log
Uptime: 15m22s
User Count: 1
```
</CodeBlockConfig>
## Usage
<CodeBlockConfig hideClipboard>
```shell-session
$ boundary cache status [options] [args]
```
</CodeBlockConfig>
### Command options
- `output-curl-string` - Specifies that Boundary should print an equivalent cURL command string and exit, instead of executing the request.
The default value is `false`.
@include 'cmd-option-note.mdx'