We've noticed that alarms with \n in them cause the sdgtw probe to not display the alarm message properly.
For example, an alarm from the cdm probe which is monitoring a file share:
File Share: Disk free on \\nas01\FTP is now 48.68%, which is below threshold (60%) out of total size 200.0 GB
will go through the sdgtw probe and display like this in snow:
UIM: File Share: Disk free on \as01\FTP is now 48.68%, which is below threshold (60%) out of total size 200.0 GB
Please check with Engineering team for the build ( sdgtw-2.2.8-20220811.120650-4 ) .
Please note that after this fix will not accept \n in any part of the probe.
For example, our sdgtw probe is configured with the following for the description:
*** Alarm Details ***\nMessage: $message\nAlarm ID: $nimid\nAlarm Severity: $severity\nHostname: $hostname ($user_tag1)\nProbe: $probe\nAlarm time: $time_origin\n
that template allows our alarms to appear like this:
*** Alarm Details ***Message: notepad.exe: Process notepad.exe is not runningAlarm ID: HI51870285-91445Alarm Severity: criticalHostname: nucpuimump02 (WIN~UIM)Probe: processesAlarm time: 23/08/22 21:06:49
However, since the sdgtw probe update provided, it doesn't accept the \n in the custom value box leaving us with our alarms looking like this:
*** Alarm Details ***\nMessage: Average (4 samples) disk free on C:\ is now 9%, which is below the error threshold (10%) out of total size 59.1 GB\nAlarm ID: TL98822676-60095\nAlarm Severity: minor\nHostname: acapkvssum01 (WIN~Stratus)\nProbe: cdm\nAlarm time: 23/08/22 20:21:58\n