Using “Overwrite existing data” in ControlUp – Documentation Error and Recommended Interval for Pending Reboots

A user had a question about using the "Overwrite existing data" feature in ControlUp. After checking internally, it was discovered that the documentation was incorrect and the feature is not available for short/long interval triggers. The team recommended using a once a day interval instead and asked for more details on the user’s use case. The user mentioned it was for handling pending reboots and agreed to use a once a day interval. They had initially wanted a shorter interval but decided it wasn’t necessary.

Read the entire ‘Using "Overwrite existing data" in ControlUp – Documentation Error and Recommended Interval for Pending Reboots’ thread below:

Quesiton. Can I not use Overwrite existing data with short/long delay? If i look at the documentation it says I can. So I’m a bit confused.

I think the documentation is incorrect. @member?

Actually, thinking about it, I feel it should be the other way around

Let me check with the team internally as well

Ok, so the documentation is incorrect. The overwrite option is a very heavy operation on our back end, so we try to limit that and therefore excluding it from the short/long interval triggers

Can you tell me more about your use case?

Would once a day be enough? Is this related to patches failing to install due to the pending reboot?

its for pending reboot, once a day would be ok

Ill move to once a day, just didnt need historical data for every device, would be nice, but I dont think its that necessary, at least for us. Was just trying to keep the update to around 20-30 minutes with long delay.

Continue reading and comment on the thread ‘Using “Overwrite existing data” in ControlUp – Documentation Error and Recommended Interval for Pending Reboots’.  Not a member? Join Here!