New Relic · Arazzo Workflow

New Relic Open Violations Triage

Version 1.0.0

List open violations and branch into incident or event detail.

1 workflow 1 source API 1 provider
View Spec View on GitHub AnalysisAnalyticsAPMDevOpsInfrastructureMonitoringObservabilityPerformancePlatformArazzoWorkflows

Provider

new-relic

Workflows

open-violations-triage
List open violations then branch on whether any are open.
Reads open violations and either pulls open incidents when violations exist or lists recent events when the system is quiet.
3 steps inputs: endDate, startDate outputs: events, incidents, violation
1
listOpenViolations
List the currently open alerts violations within the supplied window for triage.
2
listOpenIncidents
List the open alerts incidents so violations can be correlated to the incidents they rolled up into.
3
listRecentEvents
List recent alerts events to provide context when no violations are currently open.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: New Relic Open Violations Triage
  summary: List open violations and branch into incident or event detail.
  description: >-
    An incident-response triage pattern. The workflow lists currently open
    alerts violations, and branches: when at least one open violation exists it
    pulls open incidents for correlation, and when none are open it lists recent
    alerts events for context. 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
sourceDescriptions:
- name: alertsApi
  url: ../openapi/new-relic-alerts-api-openapi.yml
  type: openapi
workflows:
- workflowId: open-violations-triage
  summary: List open violations then branch on whether any are open.
  description: >-
    Reads open violations and either pulls open incidents when violations exist
    or lists recent events when the system is quiet.
  inputs:
    type: object
    required:
    - startDate
    - endDate
    properties:
      startDate:
        type: string
        description: The start of the violation window (ISO 8601).
      endDate:
        type: string
        description: The end of the violation window (ISO 8601).
  steps:
  - stepId: listOpenViolations
    description: >-
      List the currently open alerts violations within the supplied window for
      triage.
    operationId: getAlertsViolations
    parameters:
    - name: start_date
      in: query
      value: $inputs.startDate
    - name: end_date
      in: query
      value: $inputs.endDate
    - name: only_open
      in: query
      value: true
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      violation: $response.body#/violation
    onSuccess:
    - name: hasViolations
      type: goto
      stepId: listOpenIncidents
      criteria:
      - context: $response.body
        condition: $.violation.id != null
        type: jsonpath
    - name: noViolations
      type: goto
      stepId: listRecentEvents
      criteria:
      - context: $response.body
        condition: $.violation.id == null
        type: jsonpath
  - stepId: listOpenIncidents
    description: >-
      List the open alerts incidents so violations can be correlated to the
      incidents they rolled up into.
    operationId: getAlertsIncidents
    parameters:
    - name: only_open
      in: query
      value: true
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      incidents: $response.body#/incident
    onSuccess:
    - name: done
      type: end
  - stepId: listRecentEvents
    description: >-
      List recent alerts events to provide context when no violations are
      currently open.
    operationId: getAlertsEvents
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      events: $response.body#/recent_event
  outputs:
    violation: $steps.listOpenViolations.outputs.violation
    incidents: $steps.listOpenIncidents.outputs.incidents
    events: $steps.listRecentEvents.outputs.events

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/new-relic-open-violations-triage-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.