---
title: "PUT /api/v1/config/log-scale-alerts/{slug}"
method: PUT
path: "/api/v1/config/log-scale-alerts/{slug}"
tags: ["LogScaleAlert"]
---

# PUT /api/v1/config/log-scale-alerts/{slug}

`PUT /api/v1/config/log-scale-alerts/{slug}`

## Path parameters

- `slug` string, required

## Request body

- ConfigV1UpdateLogScaleAlertBody
  - `create_if_missing` boolean — If `true`, the LogScaleAlert will be created if it does not already exist, identified by `slug`. If `false`, an error will be returned if the LogScaleAlert does not already exist.
  - `dry_run` boolean — If `true`, validates the specified configuration without creating or updating the LogScaleAlert. If the specified configuration is valid, the endpoint returns a partial response without the LogScaleAlert. If the specified configuration is invalid, the endpoint returns an error.
  - `log_scale_alert` Configv1LogScaleAlert
    - `alert_type` 'STANDARD' | 'FILTER'
    - `created_at` string, date-time — Timestamp of when the LogScaleAlert was created. Cannot be set by clients.
    - `description` string — Description of the alert.
    - `disabled` boolean — Flag indicating whether the alert is disabled.
    - `log_scale_action_slugs` string[] — Slugs of LogScale actions that will receive the alerts. When the value is empty this alert won't trigger. Optional.
    - `log_scale_query` string — LogScale query to execute.
    - `name` string, required — Name of the alert.
    - `repository` string — Name of LogScale repository the alerts belongs to. Required.
    - `run_as_user` string — Email of the user that the alert runs on behalf of. Required.
    - `slug` string — The unique identifier of the LogScaleAlert. If a `slug` isn't provided, one is generated based on the `name` field. You can't modify this field after the LogScaleAlert is created.
    - `tags` string[] — Tags attached to the alert.
    - `throttle_field` string — Field to throttle on. Optional.
    - `throttle_secs` integer — Throttle time in seconds. The alert is triggered at most once per throttle period.
    - `time_window_secs` integer — Lookback window used for an alert's evaluation. If this is set to 86400 seconds (24 hours), only the events from the last 24 hours will be considered when the alert query is run.
    - `updated_at` string, date-time — Timestamp of when the LogScaleAlert was last updated. Cannot be set by clients.

## Response `200`

A successful response containing the updated LogScaleAlert.

- Configv1UpdateLogScaleAlertResponse
  - `log_scale_alert` Configv1LogScaleAlert
    - `alert_type` 'STANDARD' | 'FILTER'
    - `created_at` string, date-time — Timestamp of when the LogScaleAlert was created. Cannot be set by clients.
    - `description` string — Description of the alert.
    - `disabled` boolean — Flag indicating whether the alert is disabled.
    - `log_scale_action_slugs` string[] — Slugs of LogScale actions that will receive the alerts. When the value is empty this alert won't trigger. Optional.
    - `log_scale_query` string — LogScale query to execute.
    - `name` string, required — Name of the alert.
    - `repository` string — Name of LogScale repository the alerts belongs to. Required.
    - `run_as_user` string — Email of the user that the alert runs on behalf of. Required.
    - `slug` string — The unique identifier of the LogScaleAlert. If a `slug` isn't provided, one is generated based on the `name` field. You can't modify this field after the LogScaleAlert is created.
    - `tags` string[] — Tags attached to the alert.
    - `throttle_field` string — Field to throttle on. Optional.
    - `throttle_secs` integer — Throttle time in seconds. The alert is triggered at most once per throttle period.
    - `time_window_secs` integer — Lookback window used for an alert's evaluation. If this is set to 86400 seconds (24 hours), only the events from the last 24 hours will be considered when the alert query is run.
    - `updated_at` string, date-time — Timestamp of when the LogScaleAlert was last updated. Cannot be set by clients.

## Other responses

- `400` — Cannot update the LogScaleAlert because the request is invalid.
- `404` — Cannot update the LogScaleAlert because the slug does not exist.
- `409` — Cannot update the LogScaleAlert because there is a conflict with an existing LogScaleAlert.
- `500` — An unexpected error response.
- `default` — An undefined error response.

---

[API](https://skmtc.dev/chronosphere/apis/data-v1-api.md) · [All operations](https://skmtc.dev/chronosphere/apis/data-v1-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/chronosphere/data-v1-api/revisions/ee91fd539ced/schema)