No Collection Data within Monitor, or Collection Stops Updating.

Data collection stops within Monitor, or there is no longer any new data from a certain point. 

This is due to the following database error involving lack of space in the primary file group for the database (.mdf file).  Here is a snippet from the Monitor Logs that you will see in the "VeeamDCS.log" or "VeeamDCS.number.log" where number is a generated number for separating the log files.

01/17/12 13:36:54 Inform  0x0BC0 alarms        "A database error (code:0x80040E14, ) has occured in context of { ? = CALL sp_triggered_alarm_save;1 (?, ?, ?, ?, ?, ?, ?) }. Error information follows"
01/17/12 13:36:54 Inform  0x0BC0 alarms        "Error record 1 of 1: Could not allocate space for object 'dbo.HistoryTriggAlarm' in database 'VeeamMonitor' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup."
01/17/12 13:36:54 Inform  0x0BC0 alarms        "Throwing exception."
01/17/12 13:36:54 Error   0x0BC0 alarms        "IDispatch error #3092 (Source: Microsoft SQL Native Client, Description: Could not allocate space for object 'dbo.HistoryTriggAlarm' in database 'VeeamMonitor' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.)"

The issue is usually caused by the SQL Server Express edition which limits the database size to 10GBs. For more information: https://www.veeam.com/kb2357

Contact Veeam Technical support if any assistance is required.