This page aims to provide answers to the most frequently asked questions related to IMSURGE. If you don’t see your question, you can always reach out to our support team or reference our other documentation articles for answers.

Q: Do you store collected data?
A: We store event data files but do not index data in a database. Event files are retained for 90 days.

Q: How far back can I fetch data when creating a pipeline?
A: It depends on the capabilities of the source integration. When launching a manual pipeline execution for a data pull type integration, the API’s capabilities are reflected in the launch option configuration.

Q: How do you handle API limits?
A: For IP-based request limits, we work with vendors to lift restrictions or raise request limits for our servers. Some integrations impose limits based on API keys; in these cases, we recommend setting reasonable polling rates or distributing load across multiple keys. Details on specific integration API restrictions can be found in that integration’s documentation.

Q: What’s the difference between cloning a pipeline and just creating another one?
A: Some pipelines save configuration information for subsequent executions. This is particularly true for target integrations that create new sensors via API calls. Cloning a pipeline preserves this configuration information so data can go to the same sensor. This is useful when you want two pipelines targeting the same sensor: you can set a regular schedule and a 24-hour nightly resync to reduce gaps in data caused by sensor downtime. Creating a new pipeline does not preserve existing configuration and could result in duplicate sensors in the target software.

Q: How do I choose a polling interval?
A: We provide recommended polling rates for each integration based on user feedback and testing. In some cases, a faster or slower polling rate may be desirable. Choose a rate that balances your reporting requirements with API and data usage restrictions. See the source integration documentation for details.

Q: What if my pipeline fails?
A: The execution log provides detailed information to help with troubleshooting. Errors are presented in a user-friendly format, but unexpected issues can still occur. See Monitor Executions for more info.

Q: Why does my pipeline execution keep resulting in an aborted execution?
A: The most common reason for an aborted execution is that no data is available when requested. This may not always indicate a problem, but it could point to sensor issues. It can also happen if the polling rate is too high and the instrument has not reported new data yet. Try selecting a polling interval that better matches your collection needs.

Q: Which vendors are supported?
A: See the Integration Library for a list of source and target integrations.

Q: I don’t understand what this parameter is in my integration setup page?
A: Documentation for each integration is available in the Integration Library, including details on each parameter: what it is, why it’s needed, and how to obtain it.