Send OneView events to Data Fabric

You can choose to send both live and archived connect or process data to Data Fabric. See ION data archiving. This data can be sent to Data Fabric:

  • All events from OneView, including those in the EventGroup.DOCUMENT_TRACKING, as well as process-related events from EventGroup.WORKFLOW and EventGroup.PULSE, can be sent to Data Fabric.
  • If you enable sending data to Data Fabric, payloads are not included. If required, you can create a Data Lake flow to add payloads to Data Fabric.
  • Once you enable the option to send archived data to Data Fabric, the events can no longer be restored using OneView restore functionality. These events are accessible only in Data Fabric.
Note: 
  • No process-related events have been archived so far because they have been present in the Elasticsearch cluster since the beginning. If you enable sending process data to Data Fabric, all the events in the cluster are sent to Data Fabric.
  • For non-production users, if the user has not opted in, data is purged when the retention period is completed. For users who have opted in, data is purged only after it is sent to Data Fabric.
  • With the ION 2025.10 release, the default setting for production tenants enables the option to send live connect and process data to Data Fabric. Archiving is discontinued for all tenants, even if they have not opted to send their data to Data Fabric. In this case, data is purged after the retention period is completed.
  • If a production tenant previously opted in and then opted out, no changes are made. The default setting is enabled only for users who have not previously opted in.
  • If you choose to send archived data to Data Fabric, only events are sent. Payloads are not included.

Ingesting data into Data Fabric

The Batch Ingestion API is used to send live and archived OneView data to Data Fabric. This feature is available only for AWS Commercial because the Batch Ingestion API is only available in that environment.

Schema maintenance

Keep these points in mind:

  • Data Catalog schemas are created once and must be maintained by users.
  • If schemas are deleted unknowingly, the Batch Ingestion API and archiving process continue sending data to Data Fabric, but users cannot search that data in Compass until the schema is recreated. Data is not lost, but search functionality is impaired until schemas are restored.

Dedicated object schemas

The ION_OneViewEvent and ION_OneViewEventProperties object schemas must be dedicated to ION data archiving. If a user has their own schema with these names, the archiving data does not map correctly, which results in incorrect search results in the Compass interface.