Yeah, the behavior here is a little weird. Settings are restored automatically if the instance has never been configured (migrate flow) but must be specified explicitly if restoring over an already configured instance. We'll need to incorporate that bit of nuance here.

This would have been good to know. Any reason this little tidbit hasn't been merged in yet?

@tedvim Nope, just fell off my radar. I want to clarify the bit about new vs. already configured instances and then I'll get this merged down.

While we're at it, I'd like to make a feature request for overriding a single parameter when restoring: the hostname. The hostname is used to identify the instance within collectd - restoring a the configuration with github.example.com will mess with the monitoring setup. See the image attached where the hostname changed to something that is not our primary host at 10:31.

Tweaked the README copy to clarify the difference between restoring to an already configured instance vs. an instance that's never been configured in b4b8bdb.

I also created #128 to capture @xeago's request for overriding configuration on restore.

Merging ...