Dynatrace · Schema

ProblemNotificationPayload

The webhook notification payload delivered by Dynatrace when a problem lifecycle event occurs. Contains both summary fields for quick processing and the full ProblemDetailsJSON for detailed analysis.

AI OperationsAnalyticsAPMApplication Performance MonitoringApplication SecurityAutomationCloud MonitoringDigital Experience ManagementIntelligenceObservability

Properties

Name Type Description
ProblemID string The human-readable problem identifier displayed in the Dynatrace UI, e.g., P-123456.
ProblemTitle string The title of the problem generated by the Davis AI engine, describing the nature of the detected anomaly.
ProblemURL string The full URL to the problem detail page in the Dynatrace UI, allowing recipients to navigate directly to the problem.
ProblemSeverity string The severity level classification of the problem.
ProblemStatus string The current lifecycle status of the problem at the time of notification.
ImpactedEntities array The list of monitored entities that are experiencing service degradation as a result of the problem.
ImpactedEntityNames string A comma-separated string of display names for all impacted entities, for use in simple notification templates.
Tags string A comma-separated string of tags applied to the impacted entities, for use in routing or filtering notification handlers.
State string The state of the problem notification. OPEN for new or ongoing problems, RESOLVED for resolved problems, MERGED for merged problems.
ProblemDetailsJSON object
View JSON Schema on GitHub

JSON Schema

problems-problem-notification-payload-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/dynatrace/refs/heads/main/json-schema/problems-problem-notification-payload-schema.json",
  "title": "ProblemNotificationPayload",
  "description": "The webhook notification payload delivered by Dynatrace when a problem lifecycle event occurs. Contains both summary fields for quick processing and the full ProblemDetailsJSON for detailed analysis.",
  "type": "object",
  "properties": {
    "ProblemID": {
      "type": "string",
      "description": "The human-readable problem identifier displayed in the Dynatrace UI, e.g., P-123456.",
      "example": "P-123456"
    },
    "ProblemTitle": {
      "type": "string",
      "description": "The title of the problem generated by the Davis AI engine, describing the nature of the detected anomaly.",
      "example": "High failure rate on payment-service"
    },
    "ProblemURL": {
      "type": "string",
      "format": "uri",
      "description": "The full URL to the problem detail page in the Dynatrace UI, allowing recipients to navigate directly to the problem.",
      "example": "https://mySampleEnv.live.dynatrace.com/#problems/problemdetail;pid=-1234567890123456789_V2"
    },
    "ProblemSeverity": {
      "type": "string",
      "description": "The severity level classification of the problem.",
      "enum": [
        "AVAILABILITY",
        "ERROR",
        "PERFORMANCE",
        "RESOURCE_CONTENTION",
        "CUSTOM_ALERT"
      ],
      "example": "PERFORMANCE"
    },
    "ProblemStatus": {
      "type": "string",
      "description": "The current lifecycle status of the problem at the time of notification.",
      "enum": [
        "OPEN",
        "RESOLVED"
      ],
      "example": "OPEN"
    },
    "ImpactedEntities": {
      "type": "array",
      "description": "The list of monitored entities that are experiencing service degradation as a result of the problem.",
      "items": {
        "$ref": "#/components/schemas/ImpactedEntity"
      },
      "example": [
        {
          "Entity": "SERVICE-ABCDEF1234567890",
          "Name": "payment-service"
        }
      ]
    },
    "ImpactedEntityNames": {
      "type": "string",
      "description": "A comma-separated string of display names for all impacted entities, for use in simple notification templates.",
      "example": "payment-service, checkout-service"
    },
    "Tags": {
      "type": "string",
      "description": "A comma-separated string of tags applied to the impacted entities, for use in routing or filtering notification handlers.",
      "example": "env:production, team:backend"
    },
    "State": {
      "type": "string",
      "description": "The state of the problem notification. OPEN for new or ongoing problems, RESOLVED for resolved problems, MERGED for merged problems.",
      "enum": [
        "OPEN",
        "RESOLVED",
        "MERGED"
      ],
      "example": "OPEN"
    },
    "ProblemDetailsJSON": {
      "$ref": "#/components/schemas/ProblemDetails"
    }
  }
}

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/problems-problem-notification-payload"
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.