- Does the device actually meet the alert condition? (did it actually do what the alert would catch?) - Don't forget we can use agent browser to look at files, services, etc. remotely
- Is policy they expect to raise the alert active?
- Check policy targets of this policy – is the device actually in the site/group/filter that is targeted?
- Does this policy show in the policies section on the device level?
- Is the device online and connected to the platform?
- Is AEMAgent running properly on the device (do any monitors show a "last reading" value? - Remember, event log monitors don't by default though)
- Check AEMAgent.log at time of when alert should have been raised
- Try repushing the policy – does AEMAgent.log show any error getting the policy?
- If AEMAgent looks to be running correctly, can we put the device in alert state to test?
- Grab the key file from the device via agent browser (C:\ProgramData\CentraStage\AEMAgent\key) and plug in the platform, device ID, and Key ID in this URL:
https://<platform>-monitoring.centrastage.net/device/<DeviceUID>/monitor?key=<KeyID>- Are you able to find the monitor in the configuration?
- If you're able to find the monitor in the config, locate the monitor ID and search the AEMAgent.log for this ID. This should show you all readings for the monitor
Alerts and Monitors: Alert Not Received
Have more questions?
Was this article helpful?
Provide feedback for the Documentation team!
Browse this section
- How to Read Logs: SSL Error The remote certificate is invalid according to the validation procedure
- How to Read Logs: Software Management
- How to Read Logs: Policy Updates
- How to Read Logs: Monitoring
- How to Read Logs: Jobs
- How to Read Logs: Branding
- How to Read Logs: Agent Start Up (Service Start)
- How to Read Logs: Antivirus Detection
- How to Read Logs: Agent Connectivity Issues (Offline Devices)
- How To Read Logs: SSL Error The remote certificate is invalid according to the validation procedure
- See more