DX Unified Infrastructure Management

 View Only
Expand all | Collapse all

Schedule command in Logmon

  • 1.  Schedule command in Logmon

    Posted Sep 24, 2017 08:11 AM

    Hello,

     

    We would like to schedule a daily command check which run by logmon, we already configure all other parameters, except the running time.

     

    The idea is to schedule a daily check at 20:00 exactly, an 24 hours check will not going to help us cause we need thew check to run only at 20:00 and not 24 hours from the restart time. 

     

    any idea how to add the running time ?



  • 2.  Re: Schedule command in Logmon

    Posted Sep 28, 2017 04:18 PM

    What product is this question for its not clear to me and I want to be sure its in the right place.

    Thank you



  • 3.  Re: Schedule command in Logmon

    Broadcom Employee
    Posted Sep 28, 2017 04:56 PM

    This relates to UIM.

     

    Jason Allen

    Principal Support Engineer

     

     

    CA Technologies | 2950 East Harmony Road Suite 100 | Fort Collins, CO 80528

    Office: +33856 | Jason.Allen@ca.com

     

    <mailto:Jason.Allen@ca.com%0b%0b>[CA]

     

    <http://www.ca.com/us/default.aspx>[Twitter]<http://twitter.com/CAInc>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>[Facebook]<https://www.facebook.com/CATechnologies>[YouTube]<http://www.youtube.com/user/catechnologies>[Google]<https://plus.google.com/CATechnologies>[Slideshare]<http://www.slideshare.net/cainc>



  • 4.  Re: Schedule command in Logmon

    Broadcom Employee
    Posted Sep 29, 2017 03:54 AM

    I don't think it is possible through logmon probe.



  • 5.  Re: Schedule command in Logmon

    Posted Sep 29, 2017 04:20 AM

    As Yu has mentioned, you can't specify time.

    If it is required to execute on 20:00, I would setup cron or task scheduler which writes log on 20:00.

    Then, logmon monitor the log file and executes command on match.

    But, this is same with executing command from cron or task scheduler directory.



  • 6.  Re: Schedule command in Logmon

    Posted Oct 02, 2017 08:28 AM

    Hi,

     

    An old component (probe) of the product is always forget by the administrators ...


    Use the "nexec" probe to schedule commands at spécific date with specific recurring conditions.

     

    Best regards,

    Jonathan



  • 7.  Re: Schedule command in Logmon

    Posted Oct 09, 2017 10:06 AM

    Would a pre-processing "Exclude" rule work for you?

     

    Set it to exclude at all times apart from 20:00 - 20:05.  That way the alert will only appear at the time you want.  If not, the nexec probe is most useful as mentioned above.



  • 8.  Re: Schedule command in Logmon

    Posted Oct 17, 2017 04:45 AM

    The exclude rule works only on the input data, how can i check the the current running time to exclude it >? 



  • 9.  Re: Schedule command in Logmon

    Broadcom Employee
    Posted Oct 31, 2017 11:26 AM

    What about using a "Time Specification" in the probe's Edit option? (Right click probe, choose Edit)

     

    Just make sure that your interval is higher than 5 minutes and it should only run 1 time



  • 10.  Re: Schedule command in Logmon

    Posted Nov 01, 2017 05:06 AM

    I like that idea, but would that effect all profiles running within the probe?  If they all have different timings it wouldn't work.



  • 11.  Re: Schedule command in Logmon

    Broadcom Employee
    Posted Nov 01, 2017 10:13 AM

    Yes, it would affect all profiles on the probe.  You'd probably have to have a dedicated probe for this to function as described.



  • 12.  Re: Schedule command in Logmon

    Posted Nov 01, 2017 10:54 AM

    I've created an idea to try and get this included on the improvement roadmap, please vote it up!

     

    Scheduler in Logmon 



  • 13.  Re: Schedule command in Logmon

    Posted Nov 02, 2017 10:54 AM

    Hi everyone,

     

    Sorry to come back late in this conversation ...

    So, it exist an intermediate way with nexec and logmon !

    I've not the free time now for trying it myself but, if my memory don't make me mistakes, you can :

     

    Use the nexec probe to schedule a "pu" command like :

    ../../../bin/pu -u <user> -p <pass> logmon runprofile '<profilename>' ''
    I'm not sure for the last empty argument. I write the command on live without a CA UIM under my hands.

     

    Detail : the profile need to be in deactivated state (in your context)

     

    You keep the all features of the logmon probe with the scheduling capabilities of the nexec probe !!

     

    Please, if you can test that and make me a feedback ?

     

    Best regards,

    Jonathan



  • 14.  RE: Re: Schedule command in Logmon

    Posted Jun 17, 2019 09:32 AM
    ​Hi Jonathan,

    I've tested this and it does appear to kick the profile off within the log file of logmon, but I don't see any alarms produced from the profile.  The log doesn't show any alerts either.  My logmon profile is set to "cat" so I'm assuming it should read the file from top to bottom, and I'm alerting on anything.  But still no alarms.

    Here's the pu line I'm using:

    ./pu -u administrator -p PASSWORD /Domain/Hub/Hub/logmon runprofile test

    I've also tried:

    ./pu -u administrator -p PASSWORD /Domain/Hub/Hub/logmon runprofile 'test'

    And...

    ./pu -u administrator -p PASSWORD /Domain/Hub/Hub/logmon runprofile "test"

    When I run this command:

    ./pu -u administrator -p PASSWORD /Domain/Hub/Hub/logmon runprofile

    It returns asking for the profile name, which I input 'test'

    Then it asks for "isweb", but I've no idea what this means and there are no results on a Google search..

    Bit stuck!


  • 15.  RE: Re: Schedule command in Logmon

    Posted Jun 17, 2019 09:32 AM
    ​Hi, I just replied to this but it didn't save..

    ./pu -u administrator -p PASSWORD /Domain/Hub/Hub/logmon runprofile test

    Tried this but it doesn't work.


  • 16.  RE: Re: Schedule command in Logmon

    Posted Jun 17, 2019 10:01 AM
    ​Also tried leaving the profile name off the end..

    And it asks for isweb, but I've no idea what this means.


  • 17.  RE: Re: Schedule command in Logmon

    Broadcom Employee
    Posted Jun 17, 2019 01:09 PM

    Sam -

    I am not 100% sure, but I believe that the isweb argument needs to be set to 1 if the profile you are trying to execute is configured to monitor a URL.  If not, then the value of the isweb should be 0. The argument is required to be set to 0 or 1 when executing the runprofile callback.  It appears that the isweb argument controls the File Encoding of the monitored log file (if isweb is set, this sets to the file encoding to UTF-8).



    ------------------------------
    Kathy Maguire
    Technical Support Engineer 4
    Broadcom
    ------------------------------



  • 18.  RE: Schedule command in Logmon

    Posted 22 days ago

    FYI, this has been delivered today! Logmon 4.22 with scheduler and URL response count fixed.




  • 19.  RE: Schedule command in Logmon

    Posted 21 days ago

    Hi Sam, 

    great news about logmon. But what do you mean by ,,URL response count fixed?" 

    Regards

    Petr




  • 20.  RE: Schedule command in Logmon

    Posted 21 days ago

    Hi Petr,

    Logmon version 4.20 only counted 1 match when using url mode and the "Count matches" option in the QoS tab.

    Version 4.22 was released to resolve this.  However I've tested this in our Pre-prod and Prod and it still only counts 1, when there are many more matches.

    I've raised a case with support.