Operations
Overview
The Operations section explains how to monitor, manage, maintain, and troubleshoot ingestion activities within the Knowledge Ingestion Service.
Operational workflows focus on:
- Ingestion monitoring
- Runtime visibility
- Reprocessing
- Ingestion maintenance
- URL and file management
- Ingestion cleanup
Ingestion Run Lifecycle
Each ingestion execution creates an Ingestion Run associated with the owning Agent.
An ingestion run represents a single execution cycle of the ingestion pipeline.
Depending on the ingestion workflow and runtime behavior, ingestion runs may transition through multiple operational states.
Typical operational states may include:
| State | Description |
|---|---|
| Created | Ingestion run has been initialized |
| Running | Content extraction and processing is in progress |
| Completed | Ingestion completed successfully |
| Failed | Ingestion encountered processing failures |
| Cancelled | Ingestion was stopped before completion |
Monitoring Ingestion Runs
The Ingestions dashboard provides visibility into ingestion activity and processing status.
Users can monitor:
- Run status
- Processed URLs
- Uploaded files
- Runtime statistics
- Started time
- Completed time
Monitoring helps organizations track ingestion health and identify failed or incomplete processing operations.
Viewing Processed Content
Users can inspect content processed during ingestion runs.
Depending on the ingestion source type, the monitoring experience may display:
- Processed URLs
- Uploaded files
- Processing status
- Content selection
This helps identify failed, skipped, or partially processed content.
Rerunning an Ingestion
Users can rerun ingestion operations when content needs to be refreshed or reprocessed.
Typical scenarios include:
- Website content updates
- Updated uploaded files
- Failed processing retries
- Semantic re-indexing
To rerun an ingestion:
- Open the Ingestions dashboard
- Expand the required ingestion source
- Locate the required ingestion run
- Click the rerun action
A new ingestion run is created for the selected source.
Deleting Processed Content
Users can remove processed content from ingestion runs.
Depending on the source type, this may include:
- URLs
- Uploaded files
- Processed entries
This allows organizations to remove unwanted or outdated content from the Agent knowledge space.
Deleting Ingestion Runs
Users can delete ingestion runs that are no longer required.
Deleting ingestion runs helps maintain operational cleanliness and remove outdated processing history.
To delete an ingestion run:
- Open the Ingestions dashboard
- Expand the ingestion source
- Locate the required ingestion run
- Click the delete action
Ingestion Metrics
The Ingestions dashboard displays environment-level ingestion metrics.
Tracked metrics include:
| Metric | Description |
|---|---|
| Embeddings Created | Total embeddings generated |
| Bytes Ingested | Total bytes processed |
| Characters Ingested | Total characters indexed |
| Characters Limit | Licensed ingestion quota |
These metrics help organizations monitor ingestion usage and licensing consumption.
Operational Notes
- Knowledge ingestion is Agent-specific.
- Ingestion metrics are cumulative across the environment.
- Ingestion quota is governed by the
DATA_INGESTION_LIMITsubscription entitlement. - Infrastructure configuration is maintained globally from the root tenant.