It's a known issue that Slack, PagerDuty and other XML-based trigger actions trip on unescaped backslashes.
For straight Volume alerts, it's usually resolve by substituting Volume Caption variable with this statement that basically escapes backslashes.
${SQL: SELECT REPLACE(Caption, '\', '\\') FROM Volumes WHERE VolumeID = ${VolumeID}}
Question: how do I modify this to make it work for volume capacity forecast alerts? (The only ones where volume thresholds are accessible.)
My usual one below works for *nix paths, but not Windows.
payload={"channel": "@slackbot","username": "solarwinds","color": "Warning","text": "<${N=Alerting;M=AlertDetailsUrl}|${N=Alerting;M=Severity}>: `<${N=SwisEntity;M=Volume.DetailsUrl}|${N=SwisEntity;M=Volume.Caption}>` on `<${N=SwisEntity;M=Volume.Node.DetailsUrl}|${N=SwisEntity;M=Volume.Node.Caption}>`: ${N=SwisEntity;M=Volume.VolumePercentUsed} used."}
Thank you!