AI Ingestion (AI)

ai ingestion stores records of ingestion configurations used to build vendor connectors and alert ingestion pipelines each record (for example, ai 1, ai 2) represents one ingestion setup 1\) open ai ingestion navigate to application records → ai ingestion (in the ai ingestion workspace) each record has a tracking id (prefix ai ), vendor product , api specification uploaded , asset created/used , and name of component(s) generated 2\) what the application is for custom widget the application includes a custom widget with two modes create connector actions as components (build turbine components from an openapi spec) and run the ingestion process (build a full ingestion component with hero ai–assisted teds mapping) use the widget to add new records as you configure ingestion for each vendor or source records each record stores the outcome of a widget run (vendor, spec, asset, component names) open a record to see details of that ingestion configuration audit tab use the audit tab in the application to view ingestion activity and key fields (vendor product, api specification uploaded, name of component(s) generated) without configuring reports 3\) when to use it when you need to onboard a new alert source (siem, edr, xdr, etc ) and build connector and ingestion components when you want to review which ingestion configurations exist or which components were generated for full step by step instructions, see docid 0p9qwz3o 0j5dnkpjugmq