Dynatrace · Arazzo Workflow

Dynatrace Service Health Snapshot

Version 1.0.0

Resolve a service, read a key metric, and list its open problems and recent events.

1 workflow 4 source APIs 1 provider
View Spec View on GitHub AI OperationsAnalyticsAPMApplication Performance MonitoringApplication SecurityAutomationCloud MonitoringDigital Experience ManagementIntelligenceObservabilityArazzoWorkflows

Provider

dynatrace

Workflows

service-health-snapshot
Resolve a service and gather its metric, problems, and events.
Resolves a service by name, queries a key metric scoped to it, lists open problems affecting it, and lists recent events on its timeline.
4 steps inputs: from, metricSelector, serviceName outputs: entityId, eventCount, metricSeriesCount, problemCount
1
resolveService
Resolve the service display name to its Dynatrace entity ID for scoping the metric, problem, and event queries.
2
queryMetric
Query the key performance metric scoped to the resolved service over the requested time range.
3
listOpenProblems
List open problems whose affected or impacted entities include the resolved service.
4
listRecentEvents
List recent events on the resolved service's timeline to round out the health snapshot.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Dynatrace Service Health Snapshot
  summary: Resolve a service, read a key metric, and list its open problems and recent events.
  description: >-
    Assembles a one-shot health snapshot for a named service across three
    monitoring domains. The workflow resolves the service by name, queries a key
    performance metric scoped to it, lists open problems affecting it, and lists
    recent events on its timeline. Every step spells out its request inline so
    the flow can be read and executed without opening the underlying OpenAPI
    description.
  version: 1.0.0
  x-realizes-capability-ids:
  - BC-4220.20
  x-capability-derivation:
    method: 'deterministic join: sourceDescriptions -> per-tag OpenAPI -> tag/capability edge. No classification at this step.'
    min_confidence: 0.7
    sources:
    - capability_id: BC-4220.20
      capability_name: Observability Management
      spec: dynatrace-metrics-api-openapi.yml
      confidence: 0.85
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: entitiesApi
  url: ../openapi/dynatrace-entities-api-openapi.yml
  type: openapi
- name: eventsApi
  url: ../openapi/dynatrace-events-api-openapi.yml
  type: openapi
- name: metricsApi
  url: ../openapi/dynatrace-metrics-api-openapi.yml
  type: openapi
- name: problemsApi
  url: ../openapi/dynatrace-problems-api-openapi.yml
  type: openapi
workflows:
- workflowId: service-health-snapshot
  summary: Resolve a service and gather its metric, problems, and events.
  description: >-
    Resolves a service by name, queries a key metric scoped to it, lists open
    problems affecting it, and lists recent events on its timeline.
  inputs:
    type: object
    required:
    - serviceName
    - metricSelector
    properties:
      serviceName:
        type: string
        description: The display name of the service to snapshot.
      metricSelector:
        type: string
        description: The metric selector to query (e.g. builtin:service.response.time:avg).
      from:
        type: string
        description: Start of the queried time range (e.g. now-2h).
  steps:
  - stepId: resolveService
    description: >-
      Resolve the service display name to its Dynatrace entity ID for scoping
      the metric, problem, and event queries.
    operationId: lookupEntity
    requestBody:
      contentType: application/json
      payload:
        name: $inputs.serviceName
        type: SERVICE
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      entityId: $response.body#/entityId
      displayName: $response.body#/displayName
  - stepId: queryMetric
    description: >-
      Query the key performance metric scoped to the resolved service over the
      requested time range.
    operationId: queryMetricData
    parameters:
    - name: metricSelector
      in: query
      value: $inputs.metricSelector
    - name: entitySelector
      in: query
      value: "entityId($steps.resolveService.outputs.entityId)"
    - name: from
      in: query
      value: $inputs.from
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      seriesCount: $response.body#/totalCount
      firstMetricId: $response.body#/result/0/metricId
  - stepId: listOpenProblems
    description: >-
      List open problems whose affected or impacted entities include the
      resolved service.
    operationId: listProblems
    parameters:
    - name: problemSelector
      in: query
      value: status(OPEN)
    - name: entitySelector
      in: query
      value: "entityId($steps.resolveService.outputs.entityId)"
    - name: from
      in: query
      value: $inputs.from
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      problemCount: $response.body#/totalCount
      topProblemId: $response.body#/problems/0/problemId
  - stepId: listRecentEvents
    description: >-
      List recent events on the resolved service's timeline to round out the
      health snapshot.
    operationId: listEvents
    parameters:
    - name: entitySelector
      in: query
      value: "entityId($steps.resolveService.outputs.entityId)"
    - name: from
      in: query
      value: $inputs.from
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      eventCount: $response.body#/totalCount
      latestEventId: $response.body#/events/0/eventId
  outputs:
    entityId: $steps.resolveService.outputs.entityId
    metricSeriesCount: $steps.queryMetric.outputs.seriesCount
    problemCount: $steps.listOpenProblems.outputs.problemCount
    eventCount: $steps.listRecentEvents.outputs.eventCount

Work with this as data

Every workflow 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 arazzo workflows

4 MCP tools reach this
  • find_arazzoBrowse and filter every workflow 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 workflow
curl "https://apis.io/api/v1/arazzo/dynatrace-service-health-snapshot-workflow"
All arazzo workflows
curl "https://apis.io/api/v1/arazzo?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.