Announcement

Collapse
No announcement yet.

Log Monitor - How to turn off

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Log Monitor - How to turn off

    I have the LogMonitor on and have for over a year. I am trying to trouble shoot an issue with my log dropping entries so I need to turn off the log monitor.

    It has been so long since I turned it on, I am not sure how to turn it off. Since it is not a plug in but its own exe in the root folder, I was not sure how it was being called to start. I looked in the startup script but it is not called there.

    Can I just rename the exe to .old so it does not start up?

    Thanks,

    Michael

  • #2
    It should be run via startup.vb but yes you can rename it once it is not running.

    I very much doubt it is the cause of your issue as it uses the published HS3 calls to query the log.
    Jon

    Comment


    • #3
      I have similar question, but didn't like starting a new thread.
      I created an event which monitors log for errors and sends Pushower notification:

      Click image for larger version  Name:	Capture.PNG Views:	1 Size:	192.9 KB ID:	1275133

      As you can see the event is disabled (I'm doing some tests and getting too many errors). But it still runs:

      Click image for larger version  Name:	Capture1.PNG Views:	1 Size:	16.2 KB ID:	1275134

      Doesn't look right. I suspect it's a bug?

      Comment


      • #4
        Originally posted by alexbk66 View Post
        I have similar question, but didn't like starting a new thread.
        I created an event which monitors log for errors and sends Pushower notification:

        As you can see the event is disabled (I'm doing some tests and getting too many errors). But it still runs:

        Doesn't look right. I suspect it's a bug?
        If I remember correctly disabling an event only disables the trigger. If you call the event from another event or, as in this case, from a script it still runs. HS3 bug or feature🙂
        Steve

        Comment


        • #5
          Originally posted by alexbk66 View Post
          I have similar question, but didn't like starting a new thread.
          I created an event which monitors log for errors and sends Pushower notification:

          Click image for larger version Name:	Capture.PNG Views:	1 Size:	192.9 KB ID:	1275133

          As you can see the event is disabled (I'm doing some tests and getting too many errors). But it still runs:

          Click image for larger version Name:	Capture1.PNG Views:	1 Size:	16.2 KB ID:	1275134

          Doesn't look right. I suspect it's a bug?
          As Steve said!
          Jon

          Comment


          • #6
            Originally posted by jon00 View Post
            As Steve said!
            I understand, but I don't call the event - the plugin calls it? I'm not sure.

            Comment


            • #7
              Yes, the Log Monitor will run the event regardless if it is disabled or not. That is how HST designed it when using the hs.RunEvent scripting command (which Log Monitor uses). Its identical to pressing the run button on the actual event setup screen which will run the event regardless of its disabled status.
              Jon

              Comment


              • #8
                Originally posted by jon00 View Post
                Yes, the Log Monitor will run the event regardless if it is disabled or not. That is how HST designed it when using the hs.RunEvent scripting command (which Log Monitor uses). Its identical to pressing the run button on the actual event setup screen which will run the event regardless of its disabled status.
                Pardon my ignorance Jon, but how do I disable it then? Do I remove the exe? I'm not sure how it works...

                Comment


                • #9
                  For the event to run, you must of configured it in the Jon00HSLogMonitor.ini file. Just remove the entry under the respective EventTrigger=XXXXXXXXXX entry.
                  Jon

                  Comment


                  • #10
                    Thank you, found it. But why not make it available through normal HS plugin interface?

                    Comment


                    • #11
                      Because it is an unmanged plugin......
                      Jon

                      Comment


                      • #12
                        Originally posted by jon00 View Post
                        Because it is an unmanged plugin......
                        What do you mean by "unmanged"? Ah, it's old and you are not working on it?

                        Comment


                        • #13
                          No, it means it does not have tight integration with HS3 i.e not tied in to the UI. They are simpler to code.
                          Jon

                          Comment

                          Working...
                          X