DX Unified Infrastructure Management

 View Only
  • 1.  problems with variables on Logmon probe

    Posted Aug 03, 2020 06:22 PM

    Hi 

    I have a problem monitoring some strings with logmon probe, we need monitoring the dicovery_server.log and that nimsoft sends alarms when on the log shows error string, but we need that the alarm contein all the line where is the match the string error, we can see alarms when on the log there are error string but the alarm not shows all the line using the ${WatcherMatchedLine} variable, we see the logmon probe documenta, and it says that this variable should send all the line.

    Could you help us please?

    Best regard.


  • 2.  RE: problems with variables on Logmon probe
    Best Answer

    Posted Aug 04, 2020 08:11 AM
    Edited by Christopher Hackett Aug 07, 2020 04:59 PM
    Hi,

    what about to use regex  as Matchin Expression and put $1 in a variable?

    /(.*error.*)/ as Matching Expression
    Then define a variable with a name you like (e.g. log_line) and set RegEx to 1.
    Then you can use ${log_line} in "Message to Send on Match" expression.

    Regards,
    Olaf





  • 3.  RE: problems with variables on Logmon probe

    Broadcom Employee
    Posted Aug 04, 2020 08:55 AM
    Also I believe logmon variables are case sensitive. Notice your $PROFILE is all caps so try $WATCHERMATCHEDLINE. Is is written in the docs like this too.

    https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/logmon-log-monitoring/logmon-im-configuration/logmon-advanced-im-configuration.html


  • 4.  RE: problems with variables on Logmon probe

    Posted Aug 04, 2020 07:16 PM
    Hi Olaf

    Thank you very much, we did the recommendation that you indicated us, and it works very well.

    Thanks for the help.

    Best regard.