Creating Ingestion Pages

when vulnerability data is imported into vrm—either via csv or through a connector—the system automatically splits the data into multiple ingestion pages these pages are designed to manage processing in batches, ensuring scalability and reliability even for large datasets each ingestion page corresponds to a portion of the original dataset and is stored as a record in vrm ingestion page page record contents each ingestion page includes status tracks progress (e g , pending, submitted, completed) page type source of data (csv or api) source logical source name, used in mapping logic timestamp when the page was created/updated json file encoded subset of findings finding count number of findings in this batch sample data preview of the findings payload common statuses pending submission to enrichment page is queued but not yet picked up submitting to enrichment page is actively being processed successfully submitted all findings in the page have been sent for enrichment notes page size is defined in the import step (default 1000) this controls how many findings go into each page all ingestion pages are viewable in the vrm ingestion page application errors or issues encountered during enrichment are reflected in page level status and logs