Foglight does not raise an alarm when "The transaction log for database 'foglight' is full" (4313406)

Foglight does not raise an alarm when "The transaction log for database 'foglight' is full"

Within Foglight, new alarms are not being created. The following is populating in the Foglight Management Server logs:

YYYY-MM-DD HH:MM:SS.SSS ERROR  [Data-3-thread-11171] com.quest.nitro.service.alarm.AlarmService - Could not update an alarm  

org.hibernate.exception.SQLGrammarException: could not insert: [com.quest.nitro.service.alarm.AlarmImpl]  
  at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67)
...
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The transaction log for database 'foglight' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases  
  at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:197)  
  at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1493)  
  at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:390)  
  at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:340)  
  at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:4575)  
  at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1400)  
  at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:179)  
  at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:154)  
  at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeUpdate(SQLServerPreparedStatement.java:308)  
  at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:365)  
  at org.hibernate.id.IdentityGenerator$GetGeneratedKeysDelegate.executeAndExtract(IdentityGenerator.java:73)  
  at org.hibernate.id.insert.AbstractReturningDelegate.performInsert(AbstractReturningDelegate.java:33)  
  ... 38 more  

Foglight did not raise an alarm stating that the (MSSQL) transaction log is full.

Foglight product enhancement/defect FGL-17145 has been raised to address this. For example, when the transaction log hits a threshold, Foglight will notify the user of this and the appropriate action can be undertaken by the system Database Admin (DBA) to prevent the transaction log from becoming full.

FGL-17145

FGL-17145 will also address when the DB is running out of database space, connections being closed, and transactions failing.