New Relic · Arazzo Workflow

New Relic Ingest Trace And Event

Version 1.0.0

Send a distributed trace then emit a correlated custom event.

1 workflow 2 source APIs 1 provider
View Spec View on GitHub AnalysisAnalyticsAPMDevOpsInfrastructureMonitoringObservabilityPerformancePlatformArazzoWorkflows

Provider

new-relic

Workflows

ingest-trace-and-event
Send a trace then emit a correlated custom event.
Sends a New Relic format span to the Trace API, then sends a custom event to the Event API carrying the same trace id for correlation.
2 steps inputs: accountId, serviceName, spanId, spanName, traceId outputs: eventUuid, traceRequestId
1
sendTrace
Send a New Relic format span to the Trace API; the API accepts the payload and queues it for processing.
2
emitCorrelatedEvent
Send a custom event carrying the same trace id so the business event is linkable to the distributed trace during analysis.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: New Relic Ingest Trace And Event
  summary: Send a distributed trace then emit a correlated custom event.
  description: >-
    A distributed-tracing ingestion pattern. The workflow sends a New Relic
    format trace payload to the Trace API and then emits a correlated custom
    event to the Event API carrying the same trace id, so the trace and the
    business event can be linked during analysis. 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: new-relic-traces-api-openapi.yml
      confidence: 0.9
    model: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0
sourceDescriptions:
- name: eventsApi
  url: ../openapi/new-relic-events-api-openapi.yml
  type: openapi
- name: tracesApi
  url: ../openapi/new-relic-traces-api-openapi.yml
  type: openapi
workflows:
- workflowId: ingest-trace-and-event
  summary: Send a trace then emit a correlated custom event.
  description: >-
    Sends a New Relic format span to the Trace API, then sends a custom event to
    the Event API carrying the same trace id for correlation.
  inputs:
    type: object
    required:
    - serviceName
    - spanId
    - traceId
    - spanName
    - accountId
    properties:
      serviceName:
        type: string
        description: The service.name attribute for the span and event.
      spanId:
        type: string
        description: The id of the span being sent.
      traceId:
        type: string
        description: The trace id shared by the span and the correlated event.
      spanName:
        type: string
        description: The human-readable name of the span.
      accountId:
        type: integer
        description: The New Relic account id to ingest the custom event into.
  steps:
  - stepId: sendTrace
    description: >-
      Send a New Relic format span to the Trace API; the API accepts the payload
      and queues it for processing.
    operationId: sendTraces
    parameters:
    - name: Data-Format
      in: header
      value: newrelic
    - name: Data-Format-Version
      in: header
      value: '1'
    - name: Content-Type
      in: header
      value: application/json
    requestBody:
      contentType: application/json
      payload:
      - common:
          attributes:
            service.name: $inputs.serviceName
        spans:
        - id: $inputs.spanId
          trace.id: $inputs.traceId
          attributes:
            name: $inputs.spanName
    successCriteria:
    - condition: $statusCode == 202
    outputs:
      traceRequestId: $response.body#/requestId
  - stepId: emitCorrelatedEvent
    description: >-
      Send a custom event carrying the same trace id so the business event is
      linkable to the distributed trace during analysis.
    operationId: sendEvents
    parameters:
    - name: accountId
      in: path
      value: $inputs.accountId
    - name: Content-Type
      in: header
      value: application/json
    requestBody:
      contentType: application/json
      payload:
      - eventType: TraceCorrelation
        traceId: $inputs.traceId
        service: $inputs.serviceName
    successCriteria:
    - condition: $statusCode == 200
    outputs:
      eventUuid: $response.body#/uuid
  outputs:
    traceRequestId: $steps.sendTrace.outputs.traceRequestId
    eventUuid: $steps.emitCorrelatedEvent.outputs.eventUuid

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-ingest-trace-and-event-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.