> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/ingestion/get-started-with-ingestion-in-sprinto/review-ingested-data-and-entity-records.md). # Review Ingested Data and Entity Records The **Entities** section in Sprinto helps you review and manage data imported through ingestion workflows. Each ingestion workflow stores incoming records as entities. Entity types define how those records are structured and organised inside Sprinto. You can use the Entities section to: * Review ingested records * Create and manage entity types * Add custom fields * Configure entity relationships * Monitor ingestion output * Review associated checks *** ## Before You Begin Ensure that: * An ingestion workflow has already run successfully * Entity types exist for the workflow * You have access to the **Ingestion** module *** ## Open the Entities Section To review ingested data: 1. Log in to the Sprinto dashboard. 2. Go to **Ingestion**. 3. Open the **Entities** tab.
The Entities page displays all available entity types. *** ## Understand Entity Types An entity type defines how ingested records are structured. Each entity type acts as a reusable schema that determines: * Which fields exist * What type of data is stored * How records are organised Examples include: * Employee * Incident * Device * Repository * Cloud Account Each entity type can contain multiple entity records. *** ## Review the Entities Dashboard The Entities dashboard displays all configured entity types. Each row typically includes:
ColumnDescription
NameEntity type name
DescriptionOptional explanation
EntitiesNumber of records stored
ActionsOpens entity records
Use this page to review ingestion coverage across workflows. *** ## View Entity Records Each entity type contains individual ingested records. To review records: 1. Locate the required entity type. 2. Click **View Entities**.
Sprinto opens the entity details page. *** ## Review Entity Details The entity details page contains multiple tabs. Tabs include: * Details * Entities * Monitoring Each tab provides visibility into different parts of the ingestion output. *** ## Use the Details Tab The **Details** tab displays the entity structure. You can review: * Entity metadata * Field definitions * Field types * Required fields * Entity configuration
This helps you understand how incoming records are organised. *** ## Use the Entities Tab The **Entities** tab displays all records stored for the selected entity type. Each row represents one ingested record. You can review: * Entity identifiers * Field values * Created timestamps * Updated timestamps * Source metadata *** ## View an Entity Record To open an entity record: 1. Open the **Entities** tab. 2. Locate the required record. 3. Click **View** next to the entity.
Sprinto opens the entity record details page. *** ## Review Entity Record Information The entity record page displays: * Record metadata * Entity field values * Source information * Monitoring visibility * Raw ingestion data
This helps you validate whether the ingestion workflow processed data correctly. *** ## Review Monitoring Information The **Monitoring** tab displays checks associated with the entity type. You can review: * Linked checks * Monitoring status * Evaluation visibility * Related monitoring tasks
This helps validate how ingested records participate in monitoring workflows. *** ## Create an Entity Type Create an entity type when you need a new structure for ingested data. ### Add an Entity Type 1. Open the **Entities** tab. 2. Click **Manage Entity**.
3. Click **Add Entity Type**. 4. Enter the entity details. 5. Click **Add Entity** to save the entity type.
The entity type becomes available immediately. *** ## Configure Entity Fields Each entity type can include: * Standard fields * Custom fields * Reference fields *** ## Understand Standard Fields Standard fields are automatically included with every entity type. Common standard fields include:
FieldDescription
NameHuman-readable record name
IdentifierUnique entity identifier
URLSource reference link
Last Seen on SourceLatest observed timestamp
Standard fields cannot be removed. *** ## Add Custom Fields Custom fields allow additional metadata to be stored. To add a custom field: 1. Open the entity type configuration. 2. Click **Add Custom Field**. 3. Enter the field details. 4. Save the field. Supported data types include: * String * Boolean * Long * Double * Timestamp * JSON You can add multiple custom fields. *** ## Allow User Editing Enable **Allow User Editing** when users should be able to manually update entity values. When enabled, you can also define predefined selectable options. Use editable fields when: * Teams need to classify records manually * Additional operational metadata is required * Entity values may change outside the ingestion source *** ## Add Reference Fields Reference fields create relationships between entities. Use reference fields when one entity depends on another. Examples include: * Device → User * Incident → Asset * Resource → Organisation To add a reference field: 1. Open the entity configuration. 2. Click **Add Reference Field**. 3. Configure the relationship. 4. Save the field. You can add multiple reference fields. *** ## Edit an Entity Type Existing entity types can be modified. To edit an entity type: 1. Open **Manage Entity**. 2. Select the required entity type. 3. Click **Edit**.
1. Update the configuration. 2. Save changes. *** ## Understand Entity Relationships Reference fields help connect ingestion datasets together. Relationships improve: * Record visibility * Workflow context * Monitoring correlation * Data organisation Use relationships only when entities are logically connected. *** ## When to Create Custom Entity Types Create custom entity types when: * Existing schemas do not match the ingestion workflow * External systems contain unique data structures * Additional workflow visibility is required * Custom monitoring logic depends on new entity data *** ## Best Practices Use the following recommendations when working with entity records: * Use clear entity names * Keep field structures simple * Use custom fields only when needed * Avoid excessive JSON fields * Review ingested records after workflow execution * Use reference fields only for meaningful relationships * Enable user editing only when manual updates are required *** ## Related Topics * [Get Started with Ingestion in Sprinto](/ingestion/get-started-with-ingestion-in-sprinto.md) * [Build and Edit Workflows Using AI Editor](/ingestion/get-started-with-ingestion-in-sprinto/build-and-edit-workflows-using-ai-editor.md) * [Run and Debug Ingestion Workflows](/ingestion/get-started-with-ingestion-in-sprinto/run-and-debug-ingestion-workflows.md) * [Create and Manage Webhooks](/ingestion/get-started-with-ingestion-in-sprinto/create-and-manage-webhooks.md) * [Edit Workflows Using YAML Editor](/ingestion/get-started-with-ingestion-in-sprinto/edit-workflows-using-yaml-editor.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.sprinto.com/ingestion/get-started-with-ingestion-in-sprinto/review-ingested-data-and-entity-records.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.