When troubleshooting a loadbalancer configuration, root cause analysis should always include the question, "for how long has this setting been enabled, and why was that done?" Far too often, searching backward through audit logs for LB configuration changes does not yield an answer. Manually diffing the POST content from audit logs is tedious at best, but it is also inherently limited to the audit log retention of the necessary event.

Allowing customers to grab scheduled backups (or better yet, simply integrate or inspect the underlying git implementation of the infra-as-code) would facilitate clearer understanding of historical state of a given object.