Ad Widget

Collapse

log reading trigger problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Darius
    Junior Member
    • Feb 2017
    • 13

    #1

    log reading trigger problem

    Hi,

    I need a hand setting a trigger correctly:

    now it is set up like this:

    problem: log[C:\log.log,connection failed:|Connected:|ConsumerOk:].str("connection failed:",1)}=1

    recovery: log[C:\log.log,connection failed:|Connected:|ConsumerOk:].str("Connected:",1)}=1 or {C:\log.log,connection failed:|Connected:|ConsumerOk:].str("ConsumerOk:",1)}=1

    And if I get log in the exact second, it triggers problem, but recovery does not close it. It stays in problem state.
    Is there any chance to reconfigure this trigger correctly?

    2018-02-23 06:57:24 2018-02-23 07:56:50
    2018-02-23 07:56:50.606 | DEBUG | ConsumerOk:
    2018-02-23 06:57:24 2018-02-23 07:56:50
    2018-02-23 07:56:50.606 | ERROR | connection failed:
Working...