AsyncAPI channel · Palo Alto Networks · Cortex XSIAM Data Ingestion

event_data/ingested

Event channel for structured event data ingestion. Pre-parsed events with normalized field mappings are submitted directly to the XSIAM data lake, bypassing the raw log parsing pipeline. Each event must include dataset, vendor, product, log_type, and timestamp metadata along with the normalized event fields. Used when the source system has already normalized data into XSIAM-compatible field mappin

Open source AsyncAPI → All Palo Alto Networks channels Palo Alto Networks provider profile
Provider: Palo Alto Networks AsyncAPI: v2.6.0 Spec: Cortex XSIAM Data Ingestion Operations: 1 Messages: 1

Channel address

event_data/ingested

Operations

onEventDataIngested
Structured event data ingested into XSIAM

Messages

EventDataIngested
Structured and normalized event data submitted directly to the XSIAM data lake for indexing without additional parsing
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.