# Chalk CLI Reference: Information
source: https://docs.chalk.ai/cli#information

View details about your deployment including [resolvers](https://docs.chalk.ai/docs/resolver-overview), features, releases, logs, and system health. These read-only commands help you understand the current state of your environment.

## `chalk resolvers`
source: https://docs.chalk.ai/cli?command=resolvers

```bash
chalk resolvers
```

Show the resolvers you have defined and the features they resolve

## `chalk resolvers get`
source: https://docs.chalk.ai/cli?command=resolvers_get

```bash
chalk resolvers get <resolver-name>
```

Use the 'chalk resolvers get' command to retrieve detailed information about a specific resolver from the deployment graph.

**Flags**

- `--deployment <clnw7zjo1001f0xs64y5pb8ga>` (string)
  The id of the deployment.
- `--proto <proto>` (bool, default `false`)
  Output the resolver as raw protobuf bytes to stdout.

**Example**

```
$ chalk resolvers get get_eval_records_bq_qa
$ chalk resolvers get --deployment-id clnw7zjo1001f0xs64y5pb8ga get_eval_records_bq_qa
$ chalk resolvers get --proto get_author_id > resolver.proto
```

## `chalk token`
source: https://docs.chalk.ai/cli?command=token

```bash
chalk token
```

Get access tokens and manage service tokens.

**Flags**

- `--expires-in <expires-in>` (string, default `0s`)
  Requested token lifetime (e.g. `30m`, `24h`, `720h`). The server may cap this at the maximum allowed for the credential type.

## `chalk token list`
source: https://docs.chalk.ai/cli?command=token_list

```bash
chalk token list
```

List all service tokens. Use --token-scope to list environment-scoped or team-scoped tokens.

**Flags**

- `--token-scope <token-scope>` (string, default `environment`)
  The scope of tokens to list. Valid values are 'environment' (default) or 'team'.

**Example**

```
$ chalk token list
 Name                Client ID                            Environment  Permissions       Created
──────────────────────────────────────────────────────────────────────────────────────────────
 Production API      12a3b4c5-6789-0123-4567-890abcdef123  prod        query.online      2024-01-15
                                                                       query.offline
                                                                       deploy.read
 Development Token   98f7e6d5-4321-0987-6543-210fedcba987  dev         deploy.read       2024-02-20
 CI/CD Token         abcdef12-3456-7890-1234-567890abcdef  staging     deploy.create     2024-03-10
                                                                       deploy.read
                                                                       query.online

$ chalk token list --token-scope team
 Name                Client ID                            Permissions       Created
────────────────────────────────────────────────────────────────────────────────────
 Team API Token      xyz789abc-4567-8901-2345-678901234567  query.online    2024-03-15
                                                            query.offline
```

## `chalk token get`
source: https://docs.chalk.ai/cli?command=token_get

```bash
chalk token get
```

Get an access token.

**Flags**

- `--expires-in <expires-in>` (string, default `0s`)
  Requested token lifetime (e.g. `30m`, `24h`, `720h`). The server may cap this at the maximum allowed for the credential type.

**Example**

```
$ chalk token get
eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOmYRzLmxpc3QiLCJ0b2tlbnN3cml0ZSIsInRlYW0uYWRkbmUiLCJjcm9uLmNyZWF0ZSIsImRlcGxveS5jcmVhdGUiLCJtaWdyYXRlLmV4ZWN1dGUiLCJzZWNyZXRzLndyaXRlIiwidGVhbS5hZGQiLCJ0ZWFtLmFkbWluIiwidGVhbS5kZWxldGUiLCJ0b2tlbnMud3JpdGUiXX0sImltcGVyc29uYXRlZCI6ZmFsc2V9.ZcEUIsroLoE3sgXovnZUBYZeEZC93VVsFXSP92qw0cdAMDxKavZnZv3L8k2eRVHK-KbNOEnwntk15RmopDzYzIKt8ne3u9mqgJg4YHseooskZkrHIy9F8zj94dFr3oJ9_2JDULsfKUxQmYHV9-u2mxu-AKNqtA

$ chalk token get --expires-in 720h
```

## `chalk token create`
source: https://docs.chalk.ai/cli?command=token_create

```bash
chalk token create
```

Create a new service token. Run `chalk permissions` to list the permissions a token can be given. For the permissions that scripts, CI, and compute code need, see [https://docs.chalk.ai/docs/setup-guide#permissions-for-a-service-token](https://docs.chalk.ai/docs/setup-guide#permissions-for-a-service-token).

**Flags**

- `--name <name>` (string)
  The name of the token, as it will appear in the dashboard.
- `--permission <permission>` (string[], default `[]`)
  The permissions that this token should have. When --token-scope is 'environment' or omitted, these are environment-scoped permissions. When --token-scope is 'team', these are team-scoped permissions.
- `--team-permission <team-permission>` (string[], default `[]`)
  Deprecated: Use --permission with --token-scope team instead. The team-based permissions that this token should have. Team permissions cascade to all environments under the team.
- `--token-scope <token-scope>` (string, default `environment`)
  The scope of the token. Valid values are 'environment' (default) or 'team'. Team-scoped tokens have permissions that cascade to all environments under the team.
- `--output <output>` (string)
  The file path where the token JSON response should be written. If not specified, defaults to '<client_id>.json'.

**Example**

```
$ chalk token create --name "My API Token" --permission query.online --permission query.offline
Created environment-scoped service token and wrote to abc123xyz.json

$ chalk token create --name "Team API Token" --token-scope team --permission query.online --permission query.offline
Created team-scoped service token and wrote to def456uvw.json

$ chalk token create --name "Custom Path Token" --permission query.online --output /path/to/token.json
Created environment-scoped service token and wrote to /path/to/token.json
```

## `chalk token update`
source: https://docs.chalk.ai/cli?command=token_update

```bash
chalk token update
```

Update the name or permissions of an existing service token. At least one of --name or --permission is required. Flags left unset keep their current value; --permission replaces the existing permission set entirely, so pass `--permission=` (an explicit empty value) to clear all permissions.

**Flags**

- `--id <id>` (string)
  The client ID of the service token, as shown by `chalk token list`.
- `--name <name>` (string)
  New name for the token. Omit to keep the current name.
- `--permission <permission>` (string[], default `[]`)
  The permissions that this token should have. When --token-scope is 'environment' or omitted, these are environment-scoped permissions. When --token-scope is 'team', these are team-scoped permissions.
- `--token-scope <token-scope>` (string, default `environment`)
  The scope of the token. Valid values are 'environment' (default) or 'team'. Team-scoped tokens have permissions that cascade to all environments under the team.

**Example**

```
$ chalk token update --id abc123xyz --name "Renamed Token"
Updated service token "Renamed Token" (abc123xyz)

$ chalk token update --id abc123xyz --permission query.online --permission query.offline
Updated service token "My API Token" (abc123xyz)
```

## `chalk token delete`
source: https://docs.chalk.ai/cli?command=token_delete

```bash
chalk token delete
```

Delete a service token, revoking its access immediately. This cannot be undone.

**Flags**

- `--id <id>` (string)
  The client ID of the service token, as shown by `chalk token list`.
- `--token-scope <token-scope>` (string, default `environment`)
  The scope of the token. Valid values are 'environment' (default) or 'team'. Team-scoped tokens have permissions that cascade to all environments under the team.
- `-f, --force <force>` (bool, default `false`)
  Skip the confirmation prompt before deleting the token.

**Example**

```
$ chalk token delete --id abc123xyz
Are you sure you want to delete service token "My Token" (abc123xyz)? This cannot be undone.  [y/n]

Deleted service token abc123xyz

$ chalk token delete --id abc123xyz --force
Deleted service token abc123xyz
```

## `chalk permissions`
source: https://docs.chalk.ai/cli?command=permissions

```bash
chalk permissions
```

List all available permissions that can be assigned to service tokens. For the permissions that scripts, CI, and compute code need, see [https://docs.chalk.ai/docs/setup-guide#permissions-for-a-service-token](https://docs.chalk.ai/docs/setup-guide#permissions-for-a-service-token).

## `chalk user`
source: https://docs.chalk.ai/cli?command=user

```bash
chalk user
```

User the `user` command to print the currently logged-in user.

Useful for checking that your CLI can communicate with Chalk.

The subcommands manage the roles held by the users on your team: [`list`](https://docs.chalk.ai/cli?command=user_list) shows those users and their current roles, [`roles`](https://docs.chalk.ai/cli?command=user_roles) lists the roles that can be assigned, and [`set-role`](https://docs.chalk.ai/cli?command=user_set-role) assigns one.

**Example**

```
$ chalk user
User Agent
Name:    Jane Doe
Email:   jane@example.com
Id:      cl0wpcey0770609l56lazvc52
Team:    Acme
Team Id: 131cpe52r000009l0662k3m11
Team Permissions:
  - project.create
  - team.list
Environment Permissions:
fraud/production (900nw89h0wz0613l57la8v958)
  - deploy.read
  - query.online
```

## `chalk version`
source: https://docs.chalk.ai/cli?command=version

```bash
chalk version [--tag-only]
```

Print the build, platform, and version information for the Chalk CLI tool.

**Flags**

- `--tag-only <tag-only>` (bool, default `false`)
  Output only the tag, and no other information.
- `--check <check>` (bool, default `false`)
  Check the current version against the latest version available.

**Example**

```
$ chalk version
chalk version
Version:    v0.9.5
Platform:
Hash:       a9297a32e5d2e6507f27d2ea98b831fbcb775e21
Build Time: 2023-01-23T21:19:53+00:00

$ chalk version --tag-only
v0.9.5
```

## `chalk changelog`
source: https://docs.chalk.ai/cli?command=changelog

```bash
chalk changelog
```

Print out Chalk's public changelog in an interactive viewer

**Example**

```
$ chalk changelog
# Changelog

Improvements to Chalk are published here!
See our [public roadmap](https://github.com/orgs/chalk-ai/projects/1) for upcoming changes.
---

## January 26, 2023
### SQL File Resolvers

SQL-integrated resolvers can be completely written in SQL files: no Python required!
...
```

## `chalk releases list`
source: https://docs.chalk.ai/cli?command=releases_list

```bash
chalk releases list
```

List Chalk releases from GitHub with their versions and release notes

**Flags**

- `--component <component>` (string, default `all`)
  Component to filter releases for (e.g., `'all'`).

**Example**

```
$ chalk releases list
```

## `chalk branch source`
source: https://docs.chalk.ai/cli?command=branch_source

```bash
chalk branch source [flags]
```

Use the `chalk branch source` command to download the source code for a branch.

**Flags**

- `--branch <branch>` (string)
  The branch to download the source code from.
- `-d, --deployment <deployment>` (string)
  Download the source code of the deployment with this ID. If not specified, you will be asked to pick one.
- `--out <out>` (string)
  Output folder where code should be output. If not specified, will use the deployment ID as the containing folder.
- `--latest <latest>` (bool, default `false`)
  Use the latest branch deployment instead of prompting for a deployment ID.

**Example**

```
$ chalk branch source
✓ Fetched branches

  Which branch would you like to download?: elliot-test

  Which deployment id would you like to download?: clkhcspz1000201or1uw21rrz
✓ Fetched download link
✓ Downloaded source
✓ Extracted source to clkhcspz1000201or1uw21rrz
```

## `chalk branch list`
source: https://docs.chalk.ai/cli?command=branch_list

```bash
chalk branch list [flags]
```

Use the `chalk branch list` command to view information about branches that have been deployed in this environment.

Branches can be created with `chalk apply --branch`.

**Example**

```
$ chalk branch list
✓ Fetched branches
 Name               Deploys  Last
─────────────────────────────────────
 elliot-test        3        2h ago
 testing            33       3w ago
 gabs               54       3w ago
 test-mc            6        1mo ago
 test_credit_score  1        1mo ago
```

## `chalk named-query list`
source: https://docs.chalk.ai/cli?command=named_query_list

```bash
chalk named-query list [flags]
```

List all named queries in the active environment.

**Example**

```
$ chalk named-query list
Index  Name              Version  Tags      Output                 Description                                        Staleness              Planner Options
─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
 1      get_book_volume  1.0.1    media     book.volume book.name  get book volume and book name through named query  {"book.volume":"10s"}  {"planner_version":"2"}
```

## `chalk healthcheck`
source: https://docs.chalk.ai/cli?command=healthcheck

```bash
chalk healthcheck [name]
```

Use the `healthcheck` command to view information on the health of Chalk's api server and its services.

Pass a name (or `--name`) to run a single check. Matching is case-insensitive and accepts a unique substring of the check name, including the `HEALTH_CHECK_NAME_` prefix or the human-readable form (`HTTP_ENGINE`, `http engine`, `logging`). If more than one check matches, the command errors and lists the candidates.

The healthcheck will change according to the active environment (determined by [`chalk environment`](https://docs.chalk.ai/cli?command=environment) and active project (determined by [`chalk project`](https://docs.chalk.ai/cli?command=project).

**Arguments**

- `name` (string)
  Run only the healthcheck whose name matches this string. Case-insensitive substring match; must resolve to a single check.

**Flags**

- `-n, --name <name>` (string)
  Run only the healthcheck whose name matches this string. Case-insensitive substring match; must resolve to a single check.

  ```bash
  HTTP_ENGINE
  ```

  ```bash
  logging
  ```

  ```bash
  Metadata DB
  ```

**Example**

```
$ chalk healthcheck
Name                           Status
───────────────────────────────────────────────────────
 Metadata DB                    HEALTH_CHECK_STATUS_OK
 gRPC Client Query              HEALTH_CHECK_STATUS_OK
 Logging Client                 HEALTH_CHECK_STATUS_OK
 Metrics DB                     HEALTH_CHECK_STATUS_OK
 Push Registry                  HEALTH_CHECK_STATUS_OK
 Source Bucket                  HEALTH_CHECK_STATUS_OK

$ chalk healthcheck logging
$ chalk healthcheck --name HTTP_ENGINE
```

## `chalk logs`
source: https://docs.chalk.ai/cli?command=logs

```bash
chalk logs
```

Search through Chalk logs using powerful filtering capabilities.

Searchable Fields:

- `resolver`: Search by exact resolver name
- `query_name`: Filter by specific query names
- `operation_id`: Search using internal query IDs
- `correlation_id`: Find logs by user-provided query IDs
- `trace_id`: Filter by trace IDs
- `pod_name`: Search logs from specific pods
- `component`: Filter by Chalk components (engine, branch, offline-query)
- `message`: Search through log message content
- `resource_group`: Filter by Chalk resource groups
- `deployment`: Search by Chalk deployment ID
- `app`: Filter by Kubernetes deployment or statefulset
- `all_filter`: Search across multiple fields simultaneously
- `resolver_filter`: Find logs by similar resolver names

If the query by which you're filtering has a space or special character, like a `.`, enclose it in double quotes.

**Flags**

- `--query <query>` (string)
  Query to search logs.
- `--aggregate <aggregate>` (bool, default `false`)
  Use aggregated search to get time series data.
- `--start-time <start-time>` (string, default `1h ago`)
  Start time for filtering logs (e.g., `'1h ago'`, `'2024-01-01T00:00:00Z'`).
- `--end-time <end-time>` (string, default `now`)
  End time for filtering logs (e.g., `'now'`, `'2024-01-01T01:00:00Z'`).
- `--window-period <window-period>` (string, default `5m`)
  Window period for aggregation buckets (e.g., `'5m'`, `'1h'`).
- `-f, --follow <follow>` (bool, default `false`)
  Continuously stream new logs.
- `--tui <tui>` (bool, default `false`)
  Open an interactive TUI for viewing logs.

**Example**

```
$ chalk logs --query "resolver:user_features"
$ chalk logs --query "component:engine message:error"
$ chalk logs --query "correlation_id:abc-123"
$ chalk logs --query "all_filter:user deployment:prod"
$ chalk logs --aggregate --query "component:engine" --start-time "2h ago" --window-period "10m"
$ chalk logs --follow --query "component:engine"
$ chalk logs -f --query "resolver:user_features"
```

## `chalk logs requests`
source: https://docs.chalk.ai/cli?command=logs_requests

```bash
chalk logs requests
```

Search through envoy access logs (HTTP/gRPC request logs) for your Chalk environment.

**Flags**

- `--query <query>` (string)
  Query to search logs.
- `--start-time <start-time>` (string, default `1h ago`)
  Start time for filtering logs (e.g., `'1h ago'`, `'2024-01-01T00:00:00Z'`).
- `--end-time <end-time>` (string, default `now`)
  End time for filtering logs (e.g., `'now'`, `'2024-01-01T01:00:00Z'`).
- `--tui <tui>` (bool, default `false`)
  Open an interactive TUI for viewing logs.

**Example**

```
$ chalk logs requests --query "path:/v1/query"
$ chalk logs requests --start-time "2h ago" --query "response_code:500"
$ chalk logs requests --tui
```

## `chalk features`
source: https://docs.chalk.ai/cli?command=features

```bash
chalk features
```

Output metadata for features from the active deployment to a file. If no output flag is specified, the metadata will be written to 'chalk_features_{environment_id}_{deployment_id}.json' in the current directory.

**Flags**

- `-o, --out <out>` (string)
  Filepath to output features.

**Example**

```
$ chalk features --out fraud_features.json
```

## `chalk features list`
source: https://docs.chalk.ai/cli?command=features_list

```bash
chalk features list
```

List all features from the active deployment, displayed by their fully qualified name.

**Example**

```
$ chalk features list
$ chalk features list --environment prod
```

## `chalk features search`
source: https://docs.chalk.ai/cli?command=features_search

```bash
chalk features search <pattern>
```

Search for features by their fully qualified name using fuzzy matching. If the pattern contains '*' or '?', it is treated as a glob pattern. Otherwise, fuzzy matching is used.

**Example**

```
$ chalk features search email
$ chalk features search 'user.*age'
$ chalk features search txn
```

## `chalk features resolve`
source: https://docs.chalk.ai/cli?command=features_resolve

```bash
chalk features resolve
```

Resolve metadata for specific features by their fully qualified names (FQNs). This command fetches metadata only for the features specified by the --fqns flag.

**Flags**

- `--fqns <fqns>` (string[], default `[]`)
  Fully qualified names of features to resolve.
- `-o, --out <out>` (string)
  Filepath to output features.

**Example**

```
$ chalk features resolve --fqns user.age,user.email --out selected_features.json
```

## `chalk pods`
source: https://docs.chalk.ai/cli?command=pods

```bash
chalk pods
```

Use the `chalk pods` command to display status of Kubernetes pods that support your Chalk deployment.

**Example**

```
$ chalk pods
```

## `chalk online-store describe`
source: https://docs.chalk.ai/cli?command=online_store_describe

```bash
chalk online-store describe
```

Use this to show the current configuration of the online store attached to this environment. This includes details about the DynamoDB or Elasticache backend, such as billing mode, capacity, item count, and region.

**Example**

```
$ chalk online-store describe

dynamodb:
    table_name: chalk-online-store
    billing_mode: DYNAMO_DB_BILLING_MODE_PAY_PER_REQUEST
    item_count: "1000"
    table_size_bytes: "524288"
    region: us-east-1
```

## `chalk charts list`
source: https://docs.chalk.ai/cli?command=charts_list

```bash
chalk charts list
```

List all charts for your Chalk project and print their details in JSON format.

**Example**

```
$ chalk charts list
{
  "charts": [
    {
      "id": "chart-1",
      "name": "My First Chart",
      "description": "A sample chart"
    }
  ]
}
```

## `chalk charts evaluate`
source: https://docs.chalk.ai/cli?command=charts_evaluate

```bash
chalk charts evaluate <config-json>
```

Evaluate a metric chart configuration by calling the GetChartSnapshot API. Accepts either a full GetChartSnapshotRequest JSON payload or the legacy wrapper with metricConfig, startTime, and endTime fields, and returns the chart's time series data.

**Example**

```
$ chalk charts evaluate '{"metricConfig":{"name":"Request Count","windowPeriod":"30m","series":[{"metric":"METRIC_KIND_RESOLVER_REQUEST_COUNT","filters":[],"name":"Request Count","windowFunction":"WINDOW_FUNCTION_KIND_COUNT","groupBy":[]}]},"startTime":"2026-02-23T12:00:00Z","endTime":"2026-02-23T18:00:00Z"}'
$ chalk charts evaluate '{"metricConfig":{"name":"Request Count","windowPeriod":"30m","series":[{"metric":"METRIC_KIND_RESOLVER_REQUEST_COUNT","filters":[],"name":"Request Count","windowFunction":"WINDOW_FUNCTION_KIND_COUNT","groupBy":[]}]},"startTime":"2026-02-23T12:00:00Z","endTime":"2026-02-23T18:00:00Z","useStartAsOrigin":true,"excludeIncompleteLastBucket":false}'
```

## `chalk charts options`
source: https://docs.chalk.ai/cli?command=charts_options

```bash
chalk charts options
```

Fetch the available metrics, filters, group-by dimensions, window functions, and formulas that can be used to submit metrics queries.

**Example**

```
$ chalk charts options
{
  "metrics": [...],
  "formulas": [...]
}
```

## `chalk metrics list`
source: https://docs.chalk.ai/cli?command=metrics_list

```bash
chalk metrics list [flags]
```

Use the `metrics list` command to enumerate the metric series available in the active environment.

By default this lists the Chalk metric registry: the curated backend metrics that back dashboards, monitors, and `chalk metric query`. Each row shows the metric name, the window functions it supports, and the filters and group-by dimensions it accepts, all in the spelling `chalk metric query` expects.

Pass `--type=raw-victoria` to list the raw VictoriaMetrics series stored for the environment instead. These are an internal implementation detail rather than a stable surface, so the RPCs behind them require admin permissions. Raw series can be charted with the MetricsQL escape hatch in the metrics explorer.

**Flags**

- `--type <type>` (string, default `backend`)
  Which metric catalog to list: 'backend' for the Chalk metric registry (the series behind charts and 'chalk metric query'), or 'raw-victoria' for the underlying VictoriaMetrics series.

  ```bash
  backend
  ```

  ```bash
  raw-victoria
  ```
- `--filter <substring>` (string)
  Case-insensitive substring match on the metric name.

  ```bash
  latency
  ```

  ```bash
  chalk_query
  ```
- `--limit <count>` (int, default `5000`)
  Maximum number of series to return. Only applies to --type=raw-victoria; the backend registry is always returned in full.
- `--labels <labels>` (bool, default `false`)
  Resolve the label names carried by each series. Only applies to --type=raw-victoria, and costs one VictoriaMetrics round-trip per series.

**Example**

```
$ chalk metrics list
$ chalk metrics list --filter latency
$ chalk metrics list --json
$ chalk metrics list --type=raw-victoria
$ chalk metrics list --type=raw-victoria --filter chalk_query --labels
```

## `chalk metrics export`
source: https://docs.chalk.ai/cli?command=metrics_export

```bash
chalk metrics export [flags]
```

Use the `metrics export` command to push an message to one of your configured Kafka topics.

**Example**

```
$ chalk metrics export
```

## `chalk metrics query`
source: https://docs.chalk.ai/cli?command=metrics_query

```bash
chalk metrics query <metric-query>
```

Query metrics using a Datadog-inspired query language.

Query syntax: function:metric_name{filter:value,...} by {group,...}.rollup(period)

Components: function - Window function: avg, sum, min, max, count, p99, p95, p75, p50, p25, p5 metric - Metric name, e.g. query.latency, resolver.latency, feature.request_count filters - Optional filters in braces: {resolver_name:my_resolver,status:success} group by - Optional grouping: by {resolver_name} rollup - Optional rollup period: .rollup(5m)

**Flags**

- `--since <since>` (string, default `1h`)
  How far back to query. Supports units: s, m, h, d.

  ```bash
  30m
  ```

  ```bash
  6h
  ```

  ```bash
  7d
  ```
- `-o, --output <output>` (string, default `table`)
  Output format: table or json.

**Example**

```
$ chalk metric query 'avg:query.latency.rollup(5m)'
$ chalk metric query 'p95:resolver.latency{resolver_name:foo}.rollup(1h)'
$ chalk metric query 'count:query.count by {query_name}.rollup(10m)' --since 6h
$ chalk metric query 'avg:query.latency by {query_name,query_status}.rollup(5m)' -o json
```

## `chalk metrics raw`
source: https://docs.chalk.ai/cli?command=metrics_raw

```bash
chalk metrics raw <metricsql>
```

Use the `metrics raw` command to evaluate a MetricsQL expression directly against the VictoriaMetrics instance backing this environment's charts, and either print the resulting series or draw them as a live terminal chart.

This is the escape hatch behind the metrics explorer's "MetricsQL" field: the expression is evaluated verbatim as a range query, and no environment scoping is injected. Scope it yourself with a label matcher, e.g. `{environment_id="..."}`.

Discover the available series with `chalk metrics list --type=raw-victoria`. Raw VictoriaMetrics series names and labels are an internal implementation detail rather than a stable surface, so this command requires admin permissions and the series it exposes may change without notice.

Unlike `chalk metric query`, results come back exactly as VictoriaMetrics stored them: samples are neither snapped to a bucket grid nor gap-filled, so different series may carry different timestamps. The chart aligns them onto a shared axis by carrying the last observed value forward across gaps.

**Flags**

- `--since <since>` (string, default `1h`)
  How far back to query. Supports units: s, m, h, d. Ignored when --start is set.

  ```bash
  30m
  ```

  ```bash
  6h
  ```

  ```bash
  7d
  ```
- `--start <rfc3339>` (string)
  Start of the range (RFC3339, e.g. 2026-08-01T00:00:00Z). Overrides --since.
- `--end <rfc3339>` (string)
  End of the range (RFC3339). Defaults to now.
- `--step <duration>` (string)
  Range-query step. Unset lets the server pick one from the range width.

  ```bash
  15s
  ```

  ```bash
  5m
  ```
- `--chart <chart>` (bool, default `false`)
  Render the result as a live terminal line chart instead of printing points. Press 'q' to exit.

**Example**

```
$ chalk metrics raw 'sum(rate(chalk_query_request[5m]))'
$ chalk metrics raw 'histogram_quantile(0.95, sum(rate(chalk_query_latency_bucket[5m])) by (le))' --since 6h
$ chalk metrics raw 'sum(rate(chalk_query_request[5m])) by (tag1)' --chart
$ chalk metrics raw 'chalk_query_progress_splits_queued' --step 1m --json
```

## `chalk metrics snapshot`
source: https://docs.chalk.ai/cli?command=metrics_snapshot

```bash
chalk metrics snapshot <request-json>
```

Call GetChartSnapshot directly with a chart request payload.

Accepts either a full GetChartSnapshotRequest JSON payload or the legacy wrapper with metricConfig, startTime, and endTime fields.

**Example**

```
$ chalk metrics snapshot '{"metricConfig":{"name":"Request Count","windowPeriod":"30m","series":[{"metric":"METRIC_KIND_RESOLVER_REQUEST_COUNT","filters":[],"name":"Request Count","windowFunction":"WINDOW_FUNCTION_KIND_COUNT","groupBy":[]}]},"startTime":"2026-02-23T12:00:00Z","endTime":"2026-02-23T18:00:00Z","useStartAsOrigin":true}'
```
