You'll also want to make sure that your controller has the configured profile to send AMON data to AirWave:
This is the main AMON setting showing which destination AMP server is using which AMON profile (you can have up to 4 destinations):
# show running-config | include mgmt
(ex) mgmt-server type amp primary-server 10.10.10.10 profile default-amp
Then you want to look at what is enabled in the profile:
# 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
The above is determined by:
(10.10.10.10) (config) #mgmt-server profile default-amp
(10.10.10.10) (Mgmt Config profile "default-amp") #?
airgroupinfo-enable AirGroup enable
clone Copy data from another Mgmt Config profile
location-enable Station RSSI/AP Neighbours enable
misc-enable AP System Stats/Spec Dev/Station Steer Info enable
monitored-info-enable Monitored AP/Station Info enable
no Delete Command
sessions-enable Firewall DNA/App/Aggregate Sessions enable
stats-enable Radio/VAP/Station Stats enable
tag-enable Tag enable
uccmonitoring-enable UCC Monitoring enable
For clients, you're mostly concerned with: location-enable (for VRF), stats-enable and monitored-info-enable (AP and client data), misc-enable (client match), sessions-enable (AppRF). By default, there is no profile on the controller.