AnsweredAssumed Answered


Question asked by dsg0304 on Jun 14, 2018
Latest reply on Jun 15, 2018 by David_Kim

We found out today there appears to be an issue with the dirscan probe Message Name size! We are scanning directories on a Linux server and checking for any javadump files. The Message Name that we have set up is 25 characters long and only produces an Informational message, even though there are no Informational Messages defined in the Message Pool.

I have added a new message, set to Major, which is only 17 characters and the message alerts correctly. We also have a message that is 24 characters in length and this appears to alert correctly.

Is this a known issue? If not, then can this either be corrected, or have the dirscan documentation updated to advise of the amount of characters available?