We have a SWQL report that shows all nodes currently muted, which user account muted it, and what time the mute window starts/ends. This was very useful in holding the user accountable for unmuting their own nodes or establishing an end time.
Ever since upgrading to SW Platform 2025.4, our report shows the account who muted the server as "system" no matter who muted it. I tried to use Copilot a bunch of different ways to update the report based on the conditions below, but it kept returning "query is not valid." I'm at a loss. Can anyone help?
SolarWinds support said:
The user who initiated the action (admin) is still logged -but not under “Alerts muted” (ActionTypeDisplayName LIKE ‘%mute%’) anymore.Instead:
- User actions now appear under:
- ActionTypeID 314 (Schedule added)
- ActionTypeID 317 (Schedule assignment added)
- System-level execution appears under:
- ActionTypeID 66 (Alerts muted)
- ActionTypeID 322 (Schedule executed)
This means your custom condition:
WHERE [AT].ActionTypeDisplayName LIKE '%mute%'
no longer aligns with how mute events are recorded in 2025.4, which is why your report always returns “system”.
ActionTypeID values are not universal. They may vary between environments, so you should verify the correct mappings in:
SELECT ActionTypeID, ActionTypeDisplayName
FROM Orion.AuditingActionTypes
What This Means for Your Custom SWQL Query In Your Report
Your custom SWQL query will likely need adjustments to adapt to the new behavior, especially around filtering and correlating entries from ActionTypeDisplayName or ActionTypeID.