Connector Lifecycle
Questi contenuti non sono ancora disponibili nella tua lingua.
Connector Lifecycle
Section titled “Connector Lifecycle”Overview
Section titled “Overview”Connectors bring external data into Rokks through a repeatable lifecycle: configure, discover, map, test, select the supported execution path, validate, monitor, and maintain.
How it works
Section titled “How it works”Each connector type has provider-specific details, but the lifecycle stays consistent. A connection stores access and provider context. A stream or selected object defines what data to import. A transform plan and catalog metadata make the result usable.
Step-by-step
Section titled “Step-by-step”- Create the connection.
- Test reachability or discovery.
- Choose objects, endpoints, or streams.
- Review the field mapping.
- Select the execution path supported by that connector.
- Run the connector and validate row counts and dashboard usability.
- Monitor recurring runs and alert on stale syncs if needed.
For Web API streams, the current supported execution path is a Dispatcher schedule. Manual Sync and Full Sync actions are unavailable in the UI and Sidekick, so validate the first scheduled job before relying on its data. Other connector types may expose a different supported path.
Common mistakes
Section titled “Common mistakes”Do not assume a connection test proves the complete extraction, transform, and load path. Validate the first supported sync before using its data operationally.
Do not assume provider field names are good dashboard labels. Rewrite names into business language during mapping or schema review.