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!
Original Message:
Sent: 11-02-2017 10:53 AM
From: Jonathan Gentilhomme
Subject: Re: Schedule command in Logmon
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