Pros to keeping up with mismatches:
1 - The jump to managing your network from AMP isn't too far off
2 - Once you've spent the hard hour in AMP creating the 'desired' templates, it's not more than 5-10 mins to clean up future mismatches (time to resolve mismatches is even less after you've gotten the hang of it).
3 - The config audit report becomes more useful (especially for deployments that are supposed to be uniform)
4 - Tracking changes in your network config is easier (with time stamps to go along with relative time of the actual change on the controller for when the templates were updated)
5 - Should your network go down, AMP has the config in a ready to restore state
6 - It benefits future network admin (may or may not be your concern)
7 - You don't have to pay more for the feature, it's already there
Cons to keeping up with mismatches:
- A decent investment of time
Config audits don't take a lot of process power from AMP, so disabling audits isn't saving much in the long run. For those who really don't care to see mismatches - it's a simple AMP Setup -> General tab -> Top Header stats box -> uncheck 'mismatches'. You can even leave the group settings for audits as is, and instead hide the 'config status' column on list views.
At the recent Airheads (Las Vegas, 2013), existing customers were coming up to me saying they use AirWave to 25-30% of it's potential, how can they get more out of it?
Emphasis on point #7 - it's a feature you already have access to. If it's at your fingertips and doesn't cost more money, make use of it.