While the AMP may have the setting for AMON, you also need to verify it from the controller end.
From controller CLI:
# show running-config | include mgmt
(looking for a command that looks like:
mgmt-server type amp primary-server 10.10.10.10 profile default-amp
where primary-server = AirWave IP
and profile = whatever you decided to use for the AMON profile - in this case it's default-amp)
# show mgmt-server profile default-amp
Mgmt Config profile "default-amp" (Predefined (changed))
--------------------------------------------------------
Parameter Value
--------- -----
Stats Enabled
Tag Enabled
Sessions Enabled
Monitored Info Enabled
Misc Enabled
Location Enabled
UCC Monitoring Disabled
AirGroup Info Disabled
Inline DHCP stats Enabled
Inline AP stats Enabled
Inline Auth stats Enabled
Inline DNS stats Enabled
A simplified breakdown of what these data points are:
1) general data collection = stats, monitored info, misc
2) VisualRF = location, tags (if you use wifi tags, example: ekahau)
3) UCC = UCC monitoring (Lync calls)
4) AppRF = sessions
5) AMP 8.2 upcoming feature: Clarity = the 4 'inline' stats
note that speed/goodput values for rf performance page are also transmitted via AMON