Sysdig · Arazzo Workflow

Sysdig Publish Event and Confirm

Version 1.0.0

Post a custom event to Monitor, then list events to confirm it landed.

1 workflow 1 source API 1 provider
View Spec View on GitHub Cloud SecurityContainersKubernetesRuntime SecuritySecurityVulnerability ManagementMonitoringObservabilityCSPMComplianceArazzoWorkflows

Provider

sysdig

Workflows

publish-event-and-confirm
Create a custom monitoring event and verify it appears in the stream.
Creates a custom event with a name, severity, and scope, then lists events over a window to confirm the new event id is present.
2 steps inputs: bearerToken, description, from, name, scope, severity, to outputs: eventId, eventName, total
1
createEvent
Post the custom event into the Monitor event stream.
2
confirmEvent
List recent events to confirm the new event landed.

Source API Descriptions

Arazzo Workflow Specification

Raw ↑
arazzo: 1.0.1
info:
  title: Sysdig Publish Event and Confirm
  summary: Post a custom event to Monitor, then list events to confirm it landed.
  description: >-
    A deployment-annotation flow for Sysdig Monitor. It posts a custom event
    (for example a release marker) into the event stream, captures the generated
    event id, and lists recent events within a time window to confirm the new
    event is present. 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: eventsApi
  url: ../openapi/sysdig-events-api-openapi.yml
  type: openapi
workflows:
- workflowId: publish-event-and-confirm
  summary: Create a custom monitoring event and verify it appears in the stream.
  description: >-
    Creates a custom event with a name, severity, and scope, then lists events
    over a window to confirm the new event id is present.
  inputs:
    type: object
    required:
    - bearerToken
    - name
    - from
    - to
    properties:
      bearerToken:
        type: string
        description: Sysdig API bearer token used for Authorization.
      name:
        type: string
        description: Event name (e.g. a deployment marker).
      description:
        type: string
        description: Optional event description.
      severity:
        type: string
        description: Event severity level (e.g. INFO, WARNING, CRITICAL).
        default: INFO
      scope:
        type: string
        description: Scope expression that associates the event with infrastructure.
      from:
        type: integer
        description: Start time in Unix epoch microseconds for the confirmation list.
      to:
        type: integer
        description: End time in Unix epoch microseconds for the confirmation list.
  steps:
  - stepId: createEvent
    description: Post the custom event into the Monitor event stream.
    operationId: createEvent
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.bearerToken
    requestBody:
      contentType: application/json
      payload:
        event:
          name: $inputs.name
          description: $inputs.description
          severity: $inputs.severity
          scope: $inputs.scope
    successCriteria:
    - condition: $statusCode == 201
    outputs:
      eventId: $response.body#/event/id
      eventName: $response.body#/event/name
  - stepId: confirmEvent
    description: List recent events to confirm the new event landed.
    operationId: listEvents
    parameters:
    - name: Authorization
      in: header
      value: Bearer $inputs.bearerToken
    - name: from
      in: query
      value: $inputs.from
    - name: to
      in: query
      value: $inputs.to
    successCriteria:
    - condition: $statusCode == 200
    - context: $response.body
      condition: $.events.length > 0
      type: jsonpath
    outputs:
      total: $response.body#/total
  outputs:
    eventId: $steps.createEvent.outputs.eventId
    eventName: $steps.createEvent.outputs.eventName
    total: $steps.confirmEvent.outputs.total

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/sysdig-publish-event-and-confirm-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.