HTTP API

Cortex exposes an HTTP API for pushing and querying time series data, and operating the cluster itself.

For the sake of clarity, in this document we have grouped API endpoints by service, but keep in mind that they’re exposed both when running Cortex in microservices and singly-binary mode:

  • Microservices: each service exposes its own endpoints
  • Single-binary: the Cortex process exposes all API endpoints for the services running internally

Endpoints

APIServiceEndpoint
Index pageAll servicesGET /
ConfigurationAll servicesGET /config
Runtime ConfigurationAll servicesGET /runtime_config
Services statusAll servicesGET /services
Readiness probeAll servicesGET /ready
MetricsAll servicesGET /metrics
PprofAll servicesGET /debug/pprof
FgprofAll servicesGET /debug/fgprof
Remote writeDistributorPOST /api/v1/push
Tenants statsDistributorGET /distributor/all_user_stats
HA tracker statusDistributorGET /distributor/ha_tracker
Flush chunks / blocksIngesterGET,POST /ingester/flush
ShutdownIngesterGET,POST /ingester/shutdown
Ingesters ring statusIngesterGET /ingester/ring
Instant queryQuerier, Query-frontendGET,POST <prometheus-http-prefix>/api/v1/query
Range queryQuerier, Query-frontendGET,POST <prometheus-http-prefix>/api/v1/query_range
Get series by label matchersQuerier, Query-frontendGET,POST <prometheus-http-prefix>/api/v1/series
Get label namesQuerier, Query-frontendGET,POST <prometheus-http-prefix>/api/v1/labels
Get label valuesQuerier, Query-frontendGET <prometheus-http-prefix>/api/v1/label/{name}/values
Get metric metadataQuerier, Query-frontendGET <prometheus-http-prefix>/api/v1/metadata
Remote readQuerier, Query-frontendPOST <prometheus-http-prefix>/api/v1/read
Get tenant ingestion statsQuerierGET /api/v1/user_stats
Get tenant chunksQuerierGET /api/v1/chunks
Ruler ring statusRulerGET /ruler/ring
Ruler rulesRulerGET /ruler/rule_groups
List rulesRulerGET <prometheus-http-prefix>/api/v1/rules
List alertsRulerGET <prometheus-http-prefix>/api/v1/alerts
List rule groupsRulerGET /api/v1/rules
Get rule groups by namespaceRulerGET /api/v1/rules/{namespace}
Get rule groupRulerGET /api/v1/rules/{namespace}/{groupName}
Set rule groupRulerPOST /api/v1/rules/{namespace}
Delete rule groupRulerDELETE /api/v1/rules/{namespace}/{groupName}
Delete namespaceRulerDELETE /api/v1/rules/{namespace}
Delete tenant configurationRulerPOST /ruler/delete_tenant_config
Alertmanager statusAlertmanagerGET /multitenant_alertmanager/status
Alertmanager configsAlertmanagerGET /multitenant_alertmanager/configs
Alertmanager ring statusAlertmanagerGET /multitenant_alertmanager/ring
Alertmanager UIAlertmanagerGET /<alertmanager-http-prefix>
Alertmanager Delete Tenant ConfigurationAlertmanagerPOST /multitenant_alertmanager/delete_tenant_config
Get Alertmanager configurationAlertmanagerGET /api/v1/alerts
Set Alertmanager configurationAlertmanagerPOST /api/v1/alerts
Delete Alertmanager configurationAlertmanagerDELETE /api/v1/alerts
Delete seriesPurgerPUT,POST <prometheus-http-prefix>/api/v1/admin/tsdb/delete_series
List delete requestsPurgerGET <prometheus-http-prefix>/api/v1/admin/tsdb/delete_series
Cancel delete requestPurgerPUT,POST <prometheus-http-prefix>/api/v1/admin/tsdb/cancel_delete_request
Tenant delete requestPurgerPOST /purger/delete_tenant
Tenant delete statusPurgerGET /purger/delete_tenant_status
Store-gateway ring statusStore-gatewayGET /store-gateway/ring
Compactor ring statusCompactorGET /compactor/ring
Get rule filesConfigs API (deprecated)GET /api/prom/configs/rules
Set rule filesConfigs API (deprecated)POST /api/prom/configs/rules
Get template filesConfigs API (deprecated)GET /api/prom/configs/templates
Set template filesConfigs API (deprecated)POST /api/prom/configs/templates
Get Alertmanager config fileConfigs API (deprecated)GET /api/prom/configs/alertmanager
Set Alertmanager config fileConfigs API (deprecated)POST /api/prom/configs/alertmanager
Validate Alertmanager configConfigs API (deprecated)POST /api/prom/configs/alertmanager/validate
Deactivate configsConfigs API (deprecated)DELETE /api/prom/configs/deactivate
Restore configsConfigs API (deprecated)POST /api/prom/configs/restore

Path prefixes

In this documentation you will find the usage of some placeholders for the path prefixes, whenever the prefix is configurable. The following table shows the supported prefixes.

PrefixDefaultCLI FlagYAML Config
<legacy-http-prefix>/api/prom-http.prefixhttp_prefix
<prometheus-http-prefix>/prometheus-http.prometheus-http-prefixapi > prometheus_http_prefix
<alertmanager-http-prefix>/alertmanager-http.alertmanager-http-prefixapi > alertmanager_http_prefix

Authentication

When multi-tenancy is enabled, endpoints requiring authentication are expected to be called with the X-Scope-OrgID HTTP request header set to the tenant ID. Otherwise, when multi-tenancy is disabled, Cortex doesn’t require any request to have the X-Scope-OrgID header.

Multi-tenancy can be enabled/disabled via the CLI flag -auth.enabled or its respective YAML config option.

For more information, please refer to the dedicated Authentication and Authorisation guide.

All services

The following API endpoints are exposed by all services.

Index page

GET /

Displays an index page with links to other web pages exposed by Cortex.

Configuration

GET /config

Displays the configuration currently applied to Cortex (in YAML format), including default values and settings via CLI flags. Sensitive data is masked. Please be aware that the exported configuration doesn’t include the per-tenant overrides.

Different modes

GET /config?mode=diff

Displays the configuration currently applied to Cortex (in YAML format) as before, but containing only the values that differ from the default values.

GET /config?mode=defaults

Displays the configuration using only the default values.

Runtime Configuration

GET /runtime_config

Displays the runtime configuration currently applied to Cortex (in YAML format), including default values. Please be aware that the endpoint will be only available if Cortex is configured with the -runtime-config.file option.

Different modes

GET /runtime_config?mode=diff

Displays the runtime configuration currently applied to Cortex (in YAML format) as before, but containing only the values that differ from the default values.

Services status

GET /services

Displays a web page with the status of internal Cortex services.

Readiness probe

GET /ready

Returns 200 when Cortex is ready to serve traffic.

Metrics

GET /metrics

Returns the metrics for the running Cortex service in the Prometheus exposition format.

Pprof

GET /debug/pprof/heap
GET /debug/pprof/block
GET /debug/pprof/profile
GET /debug/pprof/trace
GET /debug/pprof/goroutine
GET /debug/pprof/mutex

Returns the runtime profiling data in the format expected by the pprof visualization tool. There are many things which can be profiled using this including heap, trace, goroutine, etc.

For more information, please check out the official documentation of pprof.

Fgprof

GET /debug/fgprof

Returns the sampling Go profiling data which allows you to analyze On-CPU as well as Off-CPU (e.g. I/O) time together.

For more information, please check out the official documentation of fgprof.

Distributor

Remote write

POST /api/v1/push

# Legacy
POST <legacy-http-prefix>/push

Entrypoint for the Prometheus remote write.

This API endpoint accepts an HTTP POST request with a body containing a request encoded with Protocol Buffers and compressed with Snappy. The definition of the protobuf message can be found in cortex.proto. The HTTP request should contain the header X-Prometheus-Remote-Write-Version set to 0.1.0.

For more information, please check out Prometheus Remote storage integrations.

Requires authentication.

Distributor ring status

GET /distributor/ring

Displays a web page with the distributor hash ring status, including the state, healthy and last heartbeat time of each distributor.

Tenants stats

GET /distributor/all_user_stats

# Legacy
GET /all_user_stats

Displays a web page with per-tenant statistics updated in realtime, including the total number of active series across all ingesters and the current ingestion rate (samples / sec).

HA tracker status

GET /distributor/ha_tracker

# Legacy
GET /ha-tracker

Displays a web page with the current status of the HA tracker, including the elected replica for each Prometheus HA cluster.

Ingester

Flush chunks / blocks

GET,POST /ingester/flush

# Legacy
GET,POST /flush

Triggers a flush of the in-memory time series data (chunks or blocks) to the long-term storage. This endpoint triggers the flush also when -ingester.flush-on-shutdown-with-wal-enabled or -blocks-storage.tsdb.flush-blocks-on-shutdown are disabled.

When using blocks storage, this endpoint accepts tenant parameter to specify tenant whose blocks are compacted and shipped. This parameter may be specified multiple times to select more tenants. If no tenant is specified, all tenants are flushed.

Flush endpoint now also accepts wait=true parameter, which makes the call synchronous – it will only return after flushing has finished. Note that returned status code does not reflect the result of flush operation. This parameter is only available when using blocks storage.

Shutdown

GET,POST /ingester/shutdown

# Legacy
GET,POST /shutdown

Flushes in-memory time series data from ingester to the long-term storage, and shuts down the ingester service. Notice that the other Cortex services are still running, and the operator (or any automation) is expected to terminate the process with a SIGINT / SIGTERM signal after the shutdown endpoint returns. In the meantime, /ready will not return 200. This endpoint will unregister the ingester from the ring even if -ingester.unregister-on-shutdown is disabled.

This API endpoint is usually used by scale down automations.

Ingesters ring status

GET /ingester/ring

# Legacy
GET /ring

Displays a web page with the ingesters hash ring status, including the state, healthy and last heartbeat time of each ingester.

Querier / Query-frontend

The following endpoints are exposed both by the querier and query-frontend.

Instant query

GET,POST <prometheus-http-prefix>/api/v1/query

# Legacy
GET,POST <legacy-http-prefix>/api/v1/query

Prometheus-compatible instant query endpoint.

For more information, please check out the Prometheus instant query documentation.

Requires authentication.

Range query

GET,POST <prometheus-http-prefix>/api/v1/query_range

# Legacy
GET,POST <legacy-http-prefix>/api/v1/query_range

Prometheus-compatible range query endpoint. When the request is sent through the query-frontend, the query will be accelerated by query-frontend (results caching and execution parallelisation).

For more information, please check out the Prometheus range query documentation.

Requires authentication.

Get series by label matchers

GET,POST <prometheus-http-prefix>/api/v1/series

# Legacy
GET,POST <legacy-http-prefix>/api/v1/series

Find series by label matchers. Differently than Prometheus and due to scalability and performances reasons, Cortex currently ignores the start and end request parameters and always fetches the series from in-memory data stored in the ingesters. There is experimental support to query the long-term store with the blocks storage engine when -querier.query-store-for-labels-enabled is set.

For more information, please check out the Prometheus series endpoint documentation.

Requires authentication.

Get label names

GET,POST <prometheus-http-prefix>/api/v1/labels

# Legacy
GET,POST <legacy-http-prefix>/api/v1/labels

Get label names of ingested series. Differently than Prometheus and due to scalability and performances reasons, Cortex currently ignores the start and end request parameters and always fetches the label names from in-memory data stored in the ingesters. There is experimental support to query the long-term store with the blocks storage engine when -querier.query-store-for-labels-enabled is set.

For more information, please check out the Prometheus get label names documentation.

Requires authentication.

Get label values

GET <prometheus-http-prefix>/api/v1/label/{name}/values

# Legacy
GET <legacy-http-prefix>/api/v1/label/{name}/values

Get label values for a given label name. Differently than Prometheus and due to scalability and performances reasons, Cortex currently ignores the start and end request parameters and always fetches the label values from in-memory data stored in the ingesters. There is experimental support to query the long-term store with the blocks storage engine when -querier.query-store-for-labels-enabled is set.

For more information, please check out the Prometheus get label values documentation.

Requires authentication.

Get metric metadata

GET <prometheus-http-prefix>/api/v1/metadata

# Legacy
GET <legacy-http-prefix>/api/v1/metadata

Prometheus-compatible metric metadata endpoint.

For more information, please check out the Prometheus metric metadata documentation.

Requires authentication.

Remote read

POST <prometheus-http-prefix>/api/v1/read

# Legacy
POST <legacy-http-prefix>/api/v1/read

Prometheus-compatible remote read endpoint.

For more information, please check out Prometheus Remote storage integrations.

Requires authentication.

Querier

Get tenant ingestion stats

GET /api/v1/user_stats

# Legacy
GET <legacy-http-prefix>/user_stats

Returns realtime ingestion rate, for the authenticated tenant, in JSON format.

Requires authentication.

Get tenant chunks

GET /api/v1/chunks

# Legacy
GET <legacy-http-prefix>/chunks

Fetch a compressed tar of all the chunks containing samples for the given time range and label matchers. This endpoint is supported only by the chunks storage, requires -querier.ingester-streaming=true and should not be exposed to users but just used for debugging purposes.

URL query parameterDescription
startStart timestamp, in RFC3339 format or unix epoch.
endEnd timestamp, in RFC3339 format or unix epoch.
matcherLabel matcher that selects the series for which chunks should be fetched.

Requires authentication.

Ruler

The ruler API endpoints require to configure a backend object storage to store the recording rules and alerts. The ruler API uses the concept of a “namespace” when creating rule groups. This is a stand in for the name of the rule file in Prometheus and rule groups must be named uniquely within a namespace.

Ruler ring status

GET /ruler/ring

# Legacy
GET /ruler_ring

Displays a web page with the ruler hash ring status, including the state, healthy and last heartbeat time of each ruler.

Ruler rules

GET /ruler/rule_groups

List all tenant rules. This endpoint is not part of ruler-API and is always available regardless of whether ruler-API is enabled or not. It should not be exposed to end users. This endpoint returns a YAML dictionary with all the rule groups for each tenant and 200 status code on success.

List rules

GET <prometheus-http-prefix>/api/v1/rules

# Legacy
GET <legacy-http-prefix>/api/v1/rules

Prometheus-compatible rules endpoint to list alerting and recording rules that are currently loaded.

For more information, please check out the Prometheus rules documentation.

This experimental endpoint is disabled by default and can be enabled via the -experimental.ruler.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

List alerts

GET <prometheus-http-prefix>/api/v1/alerts

# Legacy
GET <legacy-http-prefix>/api/v1/alerts

Prometheus-compatible rules endpoint to list of all active alerts.

For more information, please check out the Prometheus alerts documentation.

This experimental endpoint is disabled by default and can be enabled via the -experimental.ruler.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

List rule groups

GET /api/v1/rules

# Legacy
GET <legacy-http-prefix>/rules

List all rules configured for the authenticated tenant. This endpoint returns a YAML dictionary with all the rule groups for each namespace and 200 status code on success.

This experimental endpoint is disabled by default and can be enabled via the -experimental.ruler.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

Example response

---
<namespace1>:
- name: <string>
  interval: <duration;optional>
  rules:
  - record: <string>
      expr: <string>
  - alert: <string>
      expr: <string>
      for: <duration>
      annotations:
      <annotation_name>: <string>
      labels:
      <label_name>: <string>
- name: <string>
  interval: <duration;optional>
  rules:
  - record: <string>
      expr: <string>
  - alert: <string>
      expr: <string>
      for: <duration>
      annotations:
      <annotation_name>: <string>
      labels:
      <label_name>: <string>
<namespace2>:
- name: <string>
  interval: <duration;optional>
  rules:
  - record: <string>
      expr: <string>
  - alert: <string>
      expr: <string>
      for: <duration>
      annotations:
      <annotation_name>: <string>
      labels:
      <label_name>: <string>

Get rule groups by namespace

GET /api/v1/rules/{namespace}

# Legacy
GET <legacy-http-prefix>/rules/{namespace}

Returns the rule groups defined for a given namespace.

This experimental endpoint is disabled by default and can be enabled via the -experimental.ruler.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

Example response

name: <string>
interval: <duration;optional>
rules:
  - record: <string>
    expr: <string>
  - alert: <string>
    expr: <string>
    for: <duration>
    annotations:
      <annotation_name>: <string>
    labels:
      <label_name>: <string>

Get rule group

GET /api/v1/rules/{namespace}/{groupName}

# Legacy
GET <legacy-http-prefix>/rules/{namespace}/{groupName}

Returns the rule group matching the request namespace and group name.

This experimental endpoint is disabled by default and can be enabled via the -experimental.ruler.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

Set rule group

POST /api/v1/rules/{namespace}

# Legacy
POST <legacy-http-prefix>/rules/{namespace}

Creates or updates a rule group. This endpoint expects a request with Content-Type: application/yaml header and the rules YAML definition in the request body, and returns 202 on success.

This experimental endpoint is disabled by default and can be enabled via the -experimental.ruler.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

Example request

Request headers:

  • Content-Type: application/yaml

Request body:

name: <string>
interval: <duration;optional>
rules:
  - record: <string>
    expr: <string>
  - alert: <string>
    expr: <string>
    for: <duration>
    annotations:
      <annotation_name>: <string>
    labels:
      <label_name>: <string>

Delete rule group

DELETE /api/v1/rules/{namespace}/{groupName}

# Legacy
DELETE <legacy-http-prefix>/rules/{namespace}/{groupName}

Deletes a rule group by namespace and group name. This endpoints returns 202 on success.

This experimental endpoint is disabled by default and can be enabled via the -experimental.ruler.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

Delete namespace

DELETE /api/v1/rules/{namespace}

# Legacy
DELETE <legacy-http-prefix>/rules/{namespace}

Deletes all the rule groups in a namespace (including the namespace itself). This endpoint returns 202 on success.

This experimental endpoint is disabled by default and can be enabled via the -experimental.ruler.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

Delete tenant configuration

POST /ruler/delete_tenant_config

This deletes all rule groups for tenant, and returns 200 on success. Calling endpoint when no rule groups exist for user returns 200. Authentication is only to identify the tenant.

This is intended as internal API, and not to be exposed to users. This endpoint is enabled regardless of whether -experimental.ruler.enable-api is enabled or not.

Requires authentication.

Alertmanager

Alertmanager status

GET /multitenant_alertmanager/status

# Legacy (microservices mode only)
GET /status

Displays a web page with the current status of the Alertmanager, including the Alertmanager cluster members.

Alertmanager configs

GET /multitenant_alertmanager/configs

List all Alertmanager configurations. This endpoint is not part of alertmanager-API and is always available regardless of whether alertmanager-API is enabled or not. It should not be exposed to end users. This endpoint returns a YAML dictionary with all the Alertmanager configurations and 200 status code on success.

Alertmanager ring status

GET /multitenant_alertmanager/ring

Displays a web page with the Alertmanager hash ring status, including the state, healthy and last heartbeat time of each Alertmanager instance.

Alertmanager UI

GET /<alertmanager-http-prefix>

# Legacy (microservices mode only)
GET /<legacy-http-prefix>

Displays the Alertmanager UI.

Requires authentication.

Alertmanager Delete Tenant Configuration

POST /multitenant_alertmanager/delete_tenant_config

This endpoint deletes configuration for a tenant identified by X-Scope-OrgID header. It is internal, available even if Alertmanager API is not enabled by using -experimental.alertmanager.enable-api. The endpoint returns a status code of 200 if the user’s configuration has been deleted, or it didn’t exist in the first place.

Requires authentication.

Get Alertmanager configuration

GET /api/v1/alerts

Get the current Alertmanager configuration for the authenticated tenant, reading it from the configured object storage.

This endpoint doesn’t accept any URL query parameter and returns 200 on success.

This experimental endpoint is disabled by default and can be enabled via the -experimental.alertmanager.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

Set Alertmanager configuration

POST /api/v1/alerts

Stores or updates the Alertmanager configuration for the authenticated tenant. The Alertmanager configuration is stored in the configured backend object storage.

This endpoint expects the Alertmanager YAML configuration in the request body and returns 201 on success.

This experimental endpoint is disabled by default and can be enabled via the -experimental.alertmanager.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

Note: When using curl send the request body from a file, ensure that you use the --data-binary flag instead of -d, --data, or --data-ascii. The latter options do not preserve carriage returns and newlines.

Example request body

template_files:
  default_template: |
    {{ define "__alertmanager" }}AlertManager{{ end }}
    {{ define "__alertmanagerURL" }}{{ .ExternalURL }}/#/alerts?receiver={{ .Receiver | urlquery }}{{ end }}
alertmanager_config: |
  global:
    smtp_smarthost: 'localhost:25'
    smtp_from: '[email protected]'
  templates:
    - 'default_template'
  route:
    receiver: example-email
  receivers:
    - name: example-email
      email_configs:
      - to: '[email protected]'

Delete Alertmanager configuration

DELETE /api/v1/alerts

Deletes the Alertmanager configuration for the authenticated tenant.

This endpoint doesn’t accept any URL query parameter and returns 200 on success.

This experimental endpoint is disabled by default and can be enabled via the -experimental.alertmanager.enable-api CLI flag (or its respective YAML config option).

Requires authentication.

Purger

The Purger service provides APIs for requesting deletion of series in chunks storage and managing delete requests. For more information about it, please read the Delete series Guide.

Delete series

PUT,POST <prometheus-http-prefix>/api/v1/admin/tsdb/delete_series

# Legacy
PUT,POST <legacy-http-prefix>/api/v1/admin/tsdb/delete_series

Prometheus-compatible delete series endpoint.

For more information, please check out the Prometheus delete series documentation.

Requires authentication.

List delete requests

GET <prometheus-http-prefix>/api/v1/admin/tsdb/delete_series

# Legacy
GET <legacy-http-prefix>/api/v1/admin/tsdb/delete_series

List all the delete requests.

Requires authentication.

Cancel delete request

PUT,POST <prometheus-http-prefix>/api/v1/admin/tsdb/cancel_delete_request

# Legacy
PUT,POST <legacy-http-prefix>/api/v1/admin/tsdb/cancel_delete_request

Cancel a delete request while the request is still in the grace period (before the request is effectively processed by the purger and time series data is hard-deleted from the storage).

URL query parameterDescription
request_idDeletion request ID to cancel. Can be obtained by the List delete requests endpoint.

Requires authentication.

Tenant Delete Request

POST /purger/delete_tenant

Request deletion of ALL tenant data. Only works with blocks storage. Experimental.

Requires authentication.

Tenant Delete Status

GET /purger/delete_tenant_status

Returns status of tenant deletion. Output format to be defined. Experimental.

Requires authentication.

Store-gateway

Store-gateway ring status

GET /store-gateway/ring

Displays a web page with the store-gateway hash ring status, including the state, healthy and last heartbeat time of each store-gateway.

Compactor

Compactor ring status

GET /compactor/ring

Displays a web page with the compactor hash ring status, including the state, healthy and last heartbeat time of each compactor.

Configs API

This service has been deprecated in favour of Ruler and Alertmanager API.

The configs API service provides an API-driven multi-tenant approach to handling various configuration files for Prometheus. The service hosts an API where users can read and write Prometheus rule files, Alertmanager configuration files, and Alertmanager templates to a database. Each tenant will have its own set of rule files, Alertmanager config, and templates.

Request / response schema

The following schema is used both when retrieving the current configs from the API and when setting new configs via the API:

{
    "id": 99,
    "rule_format_version": "2",
    "alertmanager_config": "<standard alertmanager.yaml config>",
    "rules_files": {
        "rules.yaml": "<standard rules.yaml config>",
        "rules2.yaml": "<standard rules.yaml config>"
     },
    "template_files": {
        "templates.tmpl": "<standard template file>",
        "templates2.tmpl": "<standard template file>"
    }
}
  • id
    Should be incremented every time data is updated; Cortex will use the config with the highest number.
  • rule_format_version
    Allows compatibility for tenants with config in Prometheus V1 format. Pass “1” or “2” according to which Prometheus version you want to match.
  • alertmanager_config
    The contents of the alertmanager config file should be as described here, encoded as a single string to fit within the overall JSON payload.
  • config.rules_files
    The contents of a rules file should be as described here, encoded as a single string to fit within the overall JSON payload.
  • config.template_files
    The contents of a template file should be as described here, encoded as a single string to fit within the overall JSON payload. These entries should match the templates entries in alertmanager_config. Example:
    template_files:
      myorg.tmpl: |
        {{ define "__alertmanager" }}AlertManager{{ end }}
        {{ define "__alertmanagerURL" }}{{ .ExternalURL }}/#/alerts?receiver={{ .Receiver | urlquery }}{{ end }}
    alertmanager_config: |
      templates:
        - 'myorg.tmpl'
    

Get rule files

GET /api/prom/configs/rules

Get the current rule files for the authenticated tenant.

Requires authentication.

Set rule files

POST /api/prom/configs/rules

Replace the current rule files for the authenticated tenant.

Requires authentication.

Get template files

GET /api/prom/configs/templates

Get the current template files for the authenticated tenant.

Requires authentication.

Set template files

POST /api/prom/configs/templates

Replace the current template files for the authenticated tenant.

Requires authentication.

Get Alertmanager config file

GET /api/prom/configs/alertmanager

Get the current Alertmanager config for the authenticated tenant.

Requires authentication.

Set Alertmanager config file

POST /api/prom/configs/alertmanager

Replace the current Alertmanager config for the authenticated tenant.

Requires authentication.

Validate Alertmanager config file

POST /api/prom/configs/alertmanager/validate

Validate the Alertmanager config in the request body. The request body is expected to contain only the Alertmanager YAML config.

Deactivate configs

DELETE /api/prom/configs/deactivate

Disable configs for the authenticated tenant. Please be aware that setting a new config will effectively “re-enable” the Rules and Alertmanager configuration for the tenant.

Requires authentication.

Restore configs

POST /api/prom/configs/restore

Re-enable configs for the authenticated tenant, after being previously deactivated.

Requires authentication.