...
Devo offers a generic collector monitoring activeboard, which allows to notice the following data by using the devo.collectors.out as data source:
Number of collectors active / failing.
Collectors that stop sending data in the last hour.
Errors & Warnings distribution by collector.
General activity and types of messages.
Errors in credentials (401/403)
Errors for API limits retries (429)
Server errors (500, 501, 503)
To query SQS messages successfully processed by SQS collectors, use
...
The number of SQS messages may be more or less than the number of events sent to Devo. An inactivity alert that keeps track of job_id :will inform you if messages are not being processed.
Monitoring with AWS
CloudWatch allows you to create alarms for:
Messages sent below threshold, which can occur if data is no longer entering the S3 bucket.
Number of messages visible is too high, which can occur if the SQS collector was turned off.