Skip to main content

Collection Retries

Forward Collector uses retries in case of various failures, to make collection robust. Retries happen at different levels:

  • Collection retry. If collection of a device fails for any reason, retry attempts will be made. This includes both connection retries and device-level retries. For instance, during collection, Forward Collector will connect to the device with a credential (configured or auto-discovered during connectivity test). If connection fails for any reason (e.g., authentication failure of the provided credential), then a connection retry will be made. Retry behavior is configured in Platform → Collectors → Organization collection settings → Advanced → Retries. The default Number of retries is 5, so in total 6 collection attempts will be made. The total is shared by the connection retries and device-level retries. Retry delay interval has an exponential backoff. See Collection Settings for the full field list. Collection Retry

  • Command-level retry. After Forward Collector is connected to the device, it will run commands and capture the output. If a command cannot be run for any reason (e.g., authorization failure), then retry will be made to run the command again. Default number of command-level retry is 6, so in total 7 attempts will be made at maximum. Retry delay interval has an exponential backoff, with the first delay as 2 seconds by default. This retry option is not configurable in GUI right now.