Skip to main content
Monitoring & Collection/Scrape Collection
GETMonitoringSince 1.0SynchronousAuth Required

GetScrapeAlertRules

List all alert rules configured for a specific scrape target

Execution Availability

Try It Out

Submit a mock request using the current auth context and example-driven inputs.

Path Parameters

Request Inputs

Path Parameters

  • targetIdStringRequired

    UUID of the scrape target to retrieve alert rules for

Responses

200 OK

On success, this API returns the following response structure.

  • itemsList

    Collection of result items

    Example: (nested array)

    • uuidString

      Unique identifier of the scrape alert rule

      Example: alert-rule-001

    • targetIdString

      UUID of the scrape target this rule applies to

      Example: target-001-abc

    • consecutiveFailsInteger

      Number of consecutive failures before firing this alert

      Example: 3

    • severityString

      Severity level of the alert (critical, warning)

      Example: critical

    • autoEscalateBoolean

      Whether the alert should auto-escalate after extended downtime

      Example: true

    • createdAtString

      Created at

      Example: 2026-01-15T08:00:00Z

Endpoint

GET/api/v1/monitoring/scrape-health/targets/{targetId}/alert-rules

/api/v1/monitoring/scrape-health/targets/{targetId}/alert-rules

Operation ID

GetScrapeAlertRules

Permalink

Request Example

curl -X GET '{host}/api/v1/monitoring/scrape-health/targets/{targetId}/alert-rules' -H 'Authorization: Bearer {token}'

Response Example

200
{
  "items": [
    {}
  ]
}

Change History

This API has no change history records yet.

View all change history