---
title: stack es ml get-job-stats cli command
description: Get anomaly detection job stats. Behaviour flags: --dry-run — validate all inputs and exit without performing any action 
url: https://www.elastic.co/elastic/docs-builder/docs/4118/reference/elastic-cli/cli/stack/es/ml/get-job-stats
applies_to:
  - Elastic Cloud Serverless: Preview
  - Elastic Stack: Preview
---

# stack es ml get-job-stats cli command
<cli-modifiers>
</cli-modifiers>

```bash
elastic stack es ml get-job-stats [options]
```

Get anomaly detection job stats.
**Behaviour flags:**
`--dry-run` — validate all inputs and exit without performing any action

## Options

<definitions>
  <definition term="--allow-no-match">
    Specifies what to do when the request: 1. Contains wildcard expressions and there are no jobs that match.
    2. Contains the _all string or no identifiers and there are no matches.
    3. Contains wildcard expressions and there are only partial matches. If `true`, the API returns an empty `jobs` array when
    there are no matches and the subset of results when there are partial
    matches. If `false`, the API returns a `404` status
    code when there are no matches or only partial matches.
  </definition>
  <definition term="--job-id string">
    Identifier for the anomaly detection job. It can be a job identifier, a
    group name, a comma-separated list of jobs, or a wildcard expression. If
    you do not specify one of these options, the API returns information for
    all anomaly detection jobs.
  </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>