> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ListMonitorStatuses

> Lists monitors that have at least one firing alert matching the request's
filters, and how they are firing, plus each requested monitor that is
passing under those filters. A read served by POST, because its label
filters cannot be expressed as query parameters.



## OpenAPI

````yaml openapi/api_v1_state_openapi3_DOCUMENTATION_ONLY.json POST /api/v1/state/monitor-statuses
openapi: 3.0.3
info:
  description: >

    The State API provides HTTP/JSON REST endpoints for accessing the runtime
    state

    of the Chronosphere system.


    Use this link to download the raw Swagger specification:

    <a href="/api/v1/state/swagger.json">/api/v1/state/swagger.json</a>
  title: State V1 API
  version: v1
servers:
  - url: https://{tenant}.chronosphere.io
    variables:
      tenant:
        default: tenant
        description: tenant ID assigned by the service provider
security:
  - ApiKeyAuth: []
tags:
  - name: StateV1
paths:
  /api/v1/state/monitor-statuses:
    post:
      tags:
        - MonitorStatuses
      description: >-
        Lists monitors that have at least one firing alert matching the
        request's

        filters, and how they are firing, plus each requested monitor that is

        passing under those filters. A read served by POST, because its label

        filters cannot be expressed as query parameters.
      operationId: ListMonitorStatuses
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/statev1ListMonitorStatusesRequest'
        required: true
        x-originalParamName: body
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/statev1ListMonitorStatusesResponse'
          description: A successful response.
        default:
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/apiError'
          description: An unexpected error response.
components:
  schemas:
    statev1ListMonitorStatusesRequest:
      properties:
        collection_slugs:
          description: Count only alerts from monitors owned by one of these collections.
          items:
            type: string
          type: array
        include_signals:
          description: Include each monitor's firing signals.
          type: boolean
        label_filters:
          description: >-
            Each LabelFilter is one AND clause; the clauses are OR'ed together.

            Applied to alerts before they roll up into monitor statuses, with
            the same

            semantics as ListAlerts.
          items:
            $ref: '#/components/schemas/datav1LabelFilter'
          type: array
        monitor_slugs:
          description: >-
            Return only these monitors. When empty, returns every monitor with a
            firing

            alert that matches the other filters. A named monitor with no firing
            alert

            matching the filters is returned as passing, even when it has firing
            alerts

            the filters exclude. Slugs are not checked against existing
            monitors, so a

            slug that names no monitor is also returned as passing.
          items:
            type: string
          type: array
        severity:
          allOf:
            - $ref: '#/components/schemas/datav1Severity'
          description: Count only alerts of this severity. Unset counts both.
        team_slugs:
          description: Count only alerts from monitors owned by one of these teams.
          items:
            type: string
          type: array
      type: object
    statev1ListMonitorStatusesResponse:
      properties:
        monitor_statuses:
          description: >-
            One entry per monitor with at least one firing alert matching the
            filters,

            plus a passing entry for each of `monitor_slugs` that has none,
            ordered by

            monitor slug. Other monitors are omitted.
          items:
            $ref: '#/components/schemas/statev1MonitorStatus'
          type: array
      type: object
    apiError:
      properties:
        message:
          description: An error message describing what went wrong.
          type: string
      type: object
    datav1LabelFilter:
      description: A set of label matchers evaluated together as a single AND clause.
      properties:
        label_matchers:
          description: |-
            The matchers that make up this clause. An alert must satisfy all of
            them. A filter with no matchers is ignored rather than matching
            everything.
          items:
            $ref: '#/components/schemas/LabelFilterLabelMatcher'
          type: array
        match_strategy:
          allOf:
            - $ref: '#/components/schemas/LabelFilterMatchStrategy'
          description: >-
            How closely an alert's labels must correspond to `label_matchers`.

            Defaults to `SUBSET_MATCH` when unset, whether or not
            `label_matchers`

            is populated. Applied per target: a filter that only names monitor

            labels places no constraint on the alert's signal labels under
            either

            strategy.
      type: object
    datav1Severity:
      description: The severity an alert fired at.
      enum:
        - WARN
        - CRITICAL
      type: string
    statev1MonitorStatus:
      description: >-
        The state of one monitor under the request's filters, rolled up from its

        firing alerts that match them. A monitor whose firing alerts the filters
        all

        exclude is reported as passing. A passing monitor has a `RESOLVED`
        firing

        status, no severity and no signals.
      properties:
        firing_status:
          allOf:
            - $ref: '#/components/schemas/datav1FiringStatus'
          description: >-
            `FIRING` when the monitor has at least one firing alert matching the

            request's filters, and `RESOLVED` when it has none. `RESOLVED` does
            not

            mean the monitor has no firing alerts outside the filters.
        monitor_slug:
          description: The slug of the monitor.
          type: string
        muted:
          description: True when every matching firing alert is muted.
          type: boolean
        severity:
          allOf:
            - $ref: '#/components/schemas/datav1Severity'
          description: >-
            The most severe matching unmuted alert, or the most severe matching
            alert

            when all are muted. Unset when the monitor is passing.
        signals:
          description: >-
            The monitor's firing signals that match the filters, ordered by
            their

            labels. Set only with `include_signals`.
          items:
            $ref: '#/components/schemas/statev1SignalStatus'
          type: array
      type: object
    LabelFilterLabelMatcher:
      description: One matcher, and which of the alert's two label sets it applies to.
      properties:
        filter_target:
          allOf:
            - $ref: '#/components/schemas/LabelMatcherFilterTarget'
          description: Which of the alert's label sets this matcher applies to. Required.
        matcher:
          allOf:
            - $ref: '#/components/schemas/commonPromQLMatcher'
          description: The label name, value and comparison to apply.
      type: object
    LabelFilterMatchStrategy:
      description: |-
        How closely an alert's labels must correspond to the matchers.

         - SUBSET_MATCH: EQUAL matchers require the labels to contain all the given labels, but
        the alert may carry more. NOT_EQUAL excludes an alert when the labels
        match any matcher.
         - EXACT_MATCH: EQUAL matchers require exactly the provided labels, no more or less.
        NOT_EQUAL excludes an alert only when every NOT_EQUAL matcher applies.
      enum:
        - SUBSET_MATCH
        - EXACT_MATCH
      type: string
    datav1FiringStatus:
      description: Whether an alert is currently firing or has resolved.
      enum:
        - RESOLVED
        - FIRING
      type: string
    statev1SignalStatus:
      description: One firing signal of a monitor.
      properties:
        severities:
          description: The signal's firing severities, most severe first.
          items:
            $ref: '#/components/schemas/statev1SeverityStatus'
          type: array
        signal_labels:
          additionalProperties:
            type: string
          description: The labels of the signal.
          type: object
      type: object
    LabelMatcherFilterTarget:
      description: |-
        The label set a matcher reads. An alert carries the labels of the
        signal that fired (`SIGNAL`) and the labels of the monitor or SLO
        that raised it (`MONITOR`); the two are matched independently.
      enum:
        - MONITOR
        - SIGNAL
      type: string
    commonPromQLMatcher:
      properties:
        name:
          description: Prometheus label name for the matcher
          type: string
        type:
          allOf:
            - $ref: '#/components/schemas/commonPromQLMatcherType'
          description: The type of match to be performed
        value:
          description: Prometheus label value for the matcher
          type: string
      type: object
    statev1SeverityStatus:
      description: The firing alert of one severity of a signal.
      properties:
        muted:
          description: Whether notifications for the alert are muted.
          type: boolean
        severity:
          allOf:
            - $ref: '#/components/schemas/datav1Severity'
          description: The severity the alert fired at.
      type: object
    commonPromQLMatcherType:
      enum:
        - MatchEqual
        - MatchRegexp
        - MatchNotEqual
        - MatchNotRegexp
      type: string
  securitySchemes:
    ApiKeyAuth:
      description: Chronosphere API token
      in: header
      name: API-Token
      type: apiKey

````

## Related topics

- [Cortex XCOR MCP server tools](https://docs-xcor.paloaltonetworks.com/integrate/mcp-server/resources.md)
- [ListMonitors](https://docs-xcor.paloaltonetworks.com/tooling/api-info/definition/operations/ListMonitors.md)
- [Setting monitor muting rules](https://docs-xcor.paloaltonetworks.com/investigate/alerts/muting-rules.md)
- [Monitor details](https://docs-xcor.paloaltonetworks.com/investigate/alerts/monitors/monitor-details.md)
- [Team and collection home pages](https://docs-xcor.paloaltonetworks.com/administer/collections/home.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.