Eagle.io (Source)
Extract instrument and processor node data from Eagle.io’s API.
Setup
Prerequisites
Before setting up this integration, make sure you have an Eagle.io API key with at least Workspace access level and Read Only permission.
Credential Setup
Use Eagle.io Credentials to create or select the credential for this integration. The same credential works for both source and target setups.
Integration Setup
Since Eagle.io nodes can be organized to the user’s preference, navigating the full file tree is slightly different from the user interface. In IMSURGE’s integration setup page:
- Workspace – Your account workspace in Eagle.io.
- Location – The node that your data source is attached to.
- Data Source – The node you want to collect data from.
Reference
For credential fields, see Eagle.io Credentials.
Limitations
- Eagle.io Node Structure – API requests are made automatically during setup, but folders are hidden from view. Nested values are shown instead. When selecting a workspace, all locations are displayed. When picking a location, all valid data sources are shown. This ignores any subfolder organization in your Eagle.io environment and may cause issues if multiple nodes share the same name.
- API Rate Limits – Eagle.io imposes API rate limits per key. To avoid issues, select a polling rate that matches your project requirements without exceeding this limit.
Tips
-
Because IMSURGE allows you to search for locations and data sources, it’s recommended that you use unique names for your project and data source nodes to avoid confusion during setup.
-
When choosing a polling rate, consider the rate at which data is imported into Eagle.io, even for
Processornodes. If your data source only receives or calculates data every 6 hours, set your pipeline polling rate to match it for optimal performance.