---
title: stack es cat thread-pool cli command
description: Get thread pool statistics. Behaviour flags: --dry-run — validate all inputs and exit without performing any action 
url: https://docs-v3-preview.elastic.dev/elastic/cli/pull/573/cli/stack/es/cat/thread-pool
---

# stack es cat thread-pool cli command
<cli-modifiers>
</cli-modifiers>

```bash
elastic stack es cat thread-pool [options]
```

Get thread pool statistics.
**Behaviour flags:**
`--dry-run` — validate all inputs and exit without performing any action

## Options

<definitions>
  <definition term="--h string">
    List of columns to appear in the response. Supports simple wildcards.
    **Repeatable:** pass `--h` multiple times to supply more than one value
  </definition>
  <definition term="--s string">
    A comma-separated list of column names or aliases that determines the sort order.
    Sorting defaults to ascending and can be changed by setting `:asc`
    or `:desc` as a suffix to the column name.
    **Repeatable:** pass `--s` multiple times to supply more than one value
  </definition>
  <definition term="--local">
    If `true`, the request computes the list of selected nodes from the
    local cluster state. If `false` the list of selected nodes are computed
    from the cluster state of the master node. In both cases the coordinating
    node will send requests for further information to each selected node.
  </definition>
  <definition term="--master-timeout string">
    The period to wait for a connection to the master node.
  </definition>
  <definition term="--thread-pool-patterns string">
    A comma-separated list of thread pool names used to limit the request.
    Accepts wildcard expressions.
    **Repeatable:** pass `--thread-pool-patterns` multiple times to supply more than one value
  </definition>
  <definition term="--format string">
    Specifies the format to return the columnar data in, can be set to
    `text`, `json`, `cbor`, `yaml`, or `smile`.
  </definition>
  <definition term="--v">
    When set to `true` will enable verbose output.
  </definition>
  <definition term="--bytes enum">
    Sets the units for columns that contain a byte-size value.
    Note that byte-size value units work in terms of powers of 1024. For instance `1kb` means 1024 bytes, not 1000 bytes.
    If omitted, byte-size values are rendered with a suffix such as `kb`, `mb`, or `gb`, chosen such that the numeric value of the column is as small as possible whilst still being at least `1.0`.
    If given, byte-size values are rendered as an integer with no suffix, representing the value of the column in the chosen unit.
    Values that are not an exact multiple of the chosen unit are rounded down.
    **Values:** b, kb, mb, gb, tb, pb
  </definition>
  <definition term="--time enum">
    Sets the units for columns that contain a time duration.
    If omitted, time duration values are rendered with a suffix such as `ms`, `s`, `m` or `h`, chosen such that the numeric value of the column is as small as possible whilst still being at least `1.0`.
    If given, time duration values are rendered as an integer with no suffix.
    Values that are not an exact multiple of the chosen unit are rounded down.
    **Values:** nanos, micros, ms, s, m, h, d
  </definition>
  <definition term="--error-trace">
    When set to `true` Elasticsearch will include the full stack trace of errors
    when they occur.
  </definition>
  <definition term="--filter-path string">
    Comma-separated list of filters in dot notation which reduce the response
    returned by Elasticsearch.
    **Repeatable:** pass `--filter-path` multiple times to supply more than one value
  </definition>
  <definition term="--human">
    When set to `true` will return statistics in a format suitable for humans.
    For example `"exists_time": "1h"` for humans and
    `"exists_time_in_millis": 3600000` for computers. When disabled the human
    readable values will be omitted. This makes sense for responses being consumed
    only by machines.
  </definition>
  <definition term="--pretty">
    If set to `true` the returned JSON will be "pretty-formatted". Only use
    this option for debugging only.
  </definition>
  <definition term="--input-file string">
    path to a JSON file to use as command input
  </definition>
  <definition term="--dry-run">
    validate all inputs and exit without performing any action (preview changes without applying them)
  </definition>
</definitions>


## Global Options

<definitions>
  <definition term="--json">
    output as JSON
  </definition>
</definitions>