Chronosphere · Schema

configv1ReadDropRuleResponse

ObservabilityAIOpsMonitoringMetricsLoggingDistributed TracingTelemetryOpenTelemetryPrometheusAlertingSLOInfrastructure as CodeMCPAgent ReadyA2A

Properties

Name Type Description
drop_rule object
View JSON Schema on GitHub

JSON Schema

chronosphere-configv1-read-drop-rule-response-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/chronosphere/main/json-schema/chronosphere-configv1-read-drop-rule-response-schema.json",
  "title": "configv1ReadDropRuleResponse",
  "x-generated": "2026-10-03",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/chronosphere-droprule-api-openapi.yml#/components/schemas/configv1ReadDropRuleResponse",
  "properties": {
    "drop_rule": {
      "$ref": "#/$defs/configv1DropRule"
    }
  },
  "type": "object",
  "$defs": {
    "DropRuleValueBasedDrop": {
      "properties": {
        "enabled": {
          "description": "Enables dropping metrics based on a set value.",
          "type": "boolean"
        },
        "target_drop_value": {
          "description": "The target data point value at which to drop metrics.",
          "format": "double",
          "type": "number"
        }
      },
      "type": "object"
    },
    "configv1DropRule": {
      "properties": {
        "created_at": {
          "description": "Timestamp of when the DropRule was created. Cannot be set by clients.",
          "format": "date-time",
          "readOnly": true,
          "type": "string"
        },
        "drop_nan_value": {
          "description": "Drops data points if values are Not a Number (NaN). If set to true, Chronosphere\ndrops NaN data points, along with any published staleness markers. See the\n[drop rules\ndocumentation](https://docs.chronosphere.io/control/shaping/shape-metrics/rules/drop-rules#define-a-value-based-drop-rule)\nfor more information.",
          "type": "boolean"
        },
        "filters": {
          "description": "Defines the conditions that determine whether to drop a metric. Drop rules can\nhave multiple filter conditions on different labels, making it possible to drop\na subset of the series matching a particular metric name.",
          "items": {
            "$ref": "#/$defs/configv1LabelFilter"
          },
          "type": "array"
        },
        "mode": {
          "allOf": [
            {
              "$ref": "#/$defs/configv1DropRuleMode"
            }
          ],
          "description": "If set to `DISABLED`, then the rule isn't applied when ingesting data points\nand metrics won't be dropped on the basis of this rule."
        },
        "name": {
          "description": "The name of the DropRule. You can modify this value after the DropRule is created.",
          "type": "string"
        },
        "slug": {
          "description": "The unique identifier of the DropRule. If a `slug` isn't provided, one is generated based on the `name` field. You can't modify this field after the DropRule is created.",
          "type": "string"
        },
        "updated_at": {
          "description": "Timestamp of when the DropRule was last updated. Cannot be set by clients.",
          "format": "date-time",
          "readOnly": true,
          "type": "string"
        },
        "value_based_drop": {
          "allOf": [
            {
              "$ref": "#/$defs/DropRuleValueBasedDrop"
            }
          ],
          "description": "Drops metrics based on values of `0` or `1`. This type of drop rule can\nsignificantly reduce data points per second, but changes metrics from continuous\nseries to sparse metrics. Adding a rule of this type can change the behavior of\nexisting monitors or dashboards that use the target metric."
        }
      },
      "required": [
        "name"
      ],
      "type": "object"
    },
    "configv1DropRuleMode": {
      "enum": [
        "ENABLED",
        "DISABLED",
        "PREVIEW"
      ],
      "type": "string"
    },
    "configv1LabelFilter": {
      "properties": {
        "name": {
          "description": "The name of the label to match.",
          "type": "string"
        },
        "value_glob": {
          "description": "The glob value of the label to match.",
          "type": "string"
        }
      },
      "type": "object"
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/chronosphere-configv1-read-drop-rule-response"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.