Alert_faults table problems

When the script 2026_06_02_120000_create_alert_faults_table.php runs, it stalls the database server completely after creating the alert_faults table and adding the fault_id column to the alert_log table. We have close to 800 000 posts in the alert_log table, and I see in the script that it’s supposed to copy information from alert_log to alert_faults. Is the number of posts the problem here? When I migrated our test system, I had no issues but the alert_log table was almost empty there…

Are the 800k entries all from within the last year (just wondering if you’ve increased the purge value or cleanup isn’t running). But yes, it’s updating the data to support the new per entity alerting feature.

Yes, they were from the last year. Had it set to 365 days. I changed it to 30 days and now there’s only roughly 8k log entries. I had many issues with the last update (26.10) and not sure which measure actually did the trick. I think our system ended up in limbo a bit because it was also missing some columns in the devices table, or I wasn’t able to create a new device. It worked with “lnms device:add X.X.X.X” though, just not by using the web interface.

Now I think I only have one issue left and that has something to do with the template we use for an API call for an alert rule.

Could not issue warning alert for rule ‘Rule LibreAdapter’ to transport ‘api’ Error: Transport delivery failed with 400 for Transport LibreAdapter: {“statusCode”:400,“message”:“One or more errors occurred!”,“errors”:{“serializerErrors”:[“‘A’ is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.”]}}