AsyncAPI channel · Palo Alto Networks · Cortex XSIAM Data Ingestion

log_data/ingested

Event channel for raw log data ingestion. Logs are submitted to the XSIAM HTTP collector endpoint as structured JSON batches. Each log entry must include dataset, vendor, product, log_type, and raw_log fields to route the data to the correct parsing pipeline. The XSIAM ingestion engine parses, normalizes, and indexes the log data into the appropriate dataset for analytics and correlation.

Provider: Palo Alto Networks AsyncAPI: v2.6.0 Spec: Cortex XSIAM Data Ingestion Operations: 1 Messages: 1

Channel address

log_data/ingested

Operations

onLogDataIngested
Raw log data ingested into XSIAM

Messages

LogDataIngested
Raw log data submitted to the XSIAM HTTP log collector for parsing and ingestion into the data lake
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.