In reply to Russ Feeser, SE at CenturyLink.

Hi Russ.
At F5 Agility 2018 I presented a talk, Super-NetOps Source of Truth, https://github.com/joelwking/supernetops, which included a short demo of how the audit database can be queried and a simple report generated to show changes made to the router ACL over time, showing the initiating ServiceNow ticket number, the commands issued to the target device, and the time of day.

One solution to the connectivity troubleshooting issue is being addressed by Forward Networks (www.forwardnetworks.com) which captures snapshots of the network devices, both configuration and state, and uses a mathematical model to highlight connectivity and configuration issues.
More specially to the Tetration Network Policy Publisher, the policy published to Kafka is the same policy pushed to the enforcement agent on the hosts. The policy is derived from an application dependency mapping (ADM) run on Tetration.

Also notice in the blog, my example created an ACL, but did not apply it to an interface, so there is an opportunity to review before implementation.

Good points. The challenge we face as network engineers is the shear volume of configuration data has overrun the ability for an engineer to enter it manually.