boundary/website/content/docs/commands/cache/status.mdx

---
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.
---

⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️
> [!IMPORTANT]  
> **Documentation Update:** Product documentation previously located in `/website` has moved to the [`hashicorp/web-unified-docs`](https://github.com/hashicorp/web-unified-docs) repository, where all product documentation is now centralized. Please make contributions directly to `web-unified-docs`, since changes to `/website` in this repository will not appear on developer.hashicorp.com.
⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️⚠️

# 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'