Topic
  • 5 replies
  • Latest Post - ‏2013-09-21T12:30:19Z by sweety@123
SystemAdmin
SystemAdmin
1283 Posts

Pinned topic Configuring Probes for probestats

‏2012-06-06T12:15:18Z |
According to the documentation http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=%2Fcom.ibm.netcool_OMNIbus.doc_7.3.1%2Fomnibus%2Fwip%2Fprobegtwy%2Fconcept%2Fomn_prb_enablingroi.html
the ProbeWatchHeartbeatInterval property needs to be set to a non zero value, the Opl parameter needs to be changed in the probewatch.include file and the genevent has to be updated with a registered target object server.
but even though on completing these steps it seems that the functionality doesn't works

Also found something wierd in the procedure probestats_data ( PFA ) shouldn't status.alerts be alerts.status
I tried running the sql file once again but still no change

Any idea why these things are happening ???

I am using Omnibus 7.3.1 FP 3 on Linux
Updated on 2012-09-24T17:32:31Z at 2012-09-24T17:32:31Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    1283 Posts

    Re: Configuring Probes for probestats

    ‏2012-09-19T21:01:08Z  
    Hi ,

    I am also going through this issue..

    any update on this ?

    Regards,
    Manish Agrawal
  • SystemAdmin
    SystemAdmin
    1283 Posts

    Re: Configuring Probes for probestats

    ‏2012-09-21T22:27:04Z  
    Hi All,

    Can any body provide any suggestion on this .

    Your kind support shall be highly appreciated..

    Thanks,
    Manish
  • Ken Tyler
    Ken Tyler
    38 Posts

    Re: Configuring Probes for probestats

    ‏2012-09-24T14:33:46Z  
    I just went thru the configuration steps and did not encounter any issues. Here is what I did using the Simnet Probe:
    1. Edit simnet.props and set
    ProbeWatchHeartbeatInterval : 60
    2. Copied probewatch.include to probes directory
    cd $OMNIHOME/extensions/roi
    cp probewatch.include $OMNIHOME/probes/linux2x86
    3. Installed ObjectServer modifications
    cd $OMNIHOME/extensions/roi
    nco_sql -server USISA < probestats.sql
    4. Modified trigger settings
    Enable stats_triggers Trigger Group
    Enable probe_statistics_cleanup Trigger
    5. Modified simnet.rules file:
    Commented out the existing Probe Watch rules and replaced with
    # Generate probe statistics events
    DefaultAlerts = registertarget( "USISA", "", "alerts.status" )
    if( match( @Manager, "ProbeWatch" ) )
    {
    include "$OMNIHOME/probes/linux2x86/probewatch.include"
    }
    else

    6. Modified probewatch.include
    cd $OMNIHOME/probes/linux2x86
    vi probewatch.include
    $OplHeartbeat_discard=1
    # Set if you want to discard the heartbeat events.
    # By default discard Heartbeat events to maintain backwards compatability

    $OplHeartbeat_populate_master_probestats=1
    # Enable if you want to send probestat data to the master.probestats table
    # stats_triggers trigger group must be enabled

    $OplHeartbeat_write_to_probe_log=1
    # Set if you want to log probestat data to the probe logfile at INFO level

    $OplHeartbeat_generate_threshold_events=0

    • Scroll down in the file and find the "genevent" statement:
    genevent( DefaultAlerts )

    These settings cause statistics to be written to a log file, and to
    generate entries in master.probe.stats every 60 seconds

    7. Started the Simnet Probe
    8. Log file entries
    cd $OMNIHOME/log
    more USISA_probestats.log
    Mon Sep 24 13:31:44 2012: master.probestats report:
    Mon Sep 24 13:31:44 2012: ProbeId: simnet@omnihost
    Mon Sep 24 13:31:44 2012: ProbeAgent: simnet
    Mon Sep 24 13:31:44 2012: ProbeHost: omnihost
    Mon Sep 24 13:31:44 2012: ProbeUpTime: 60
    Mon Sep 24 13:31:44 2012: ProbePID: 24053
    Mon Sep 24 13:31:44 2012: NumEventsProcessed: 62
    Mon Sep 24 13:31:44 2012: NumEventsGenerated: 1
    Mon Sep 24 13:31:44 2012: NumEventsDiscarded: 1
    Mon Sep 24 13:31:44 2012: RulesFileTimeSec: 0
    Mon Sep 24 13:31:44 2012: AvgRulesFileTime: 35
    Mon Sep 24 13:31:44 2012: CPUTimeSec: 0
    Mon Sep 24 13:31:44 2012: ProbeMemory: 227268
    Mon Sep 24 13:31:44 2012: master.probestats report end
    Mon Sep 24 13:32:44 2012: master.probestats report:
    Mon Sep 24 13:32:44 2012: ProbeId: simnet@omnihost
    Mon Sep 24 13:32:44 2012: ProbeAgent: simnet
    Mon Sep 24 13:32:44 2012: ProbeHost: omnihost
    Mon Sep 24 13:32:44 2012: ProbeUpTime: 120
    Mon Sep 24 13:32:44 2012: ProbePID: 24053
    Mon Sep 24 13:32:44 2012: NumEventsProcessed: 123
    Mon Sep 24 13:32:44 2012: NumEventsGenerated: 2
    Mon Sep 24 13:32:44 2012: NumEventsDiscarded: 2
    Mon Sep 24 13:32:44 2012: RulesFileTimeSec: 0
    Mon Sep 24 13:32:44 2012: AvgRulesFileTime: 35
    Mon Sep 24 13:32:44 2012: CPUTimeSec: 0
    Mon Sep 24 13:32:44 2012: ProbeMemory: 227268
    Mon Sep 24 13:32:44 2012: master.probestats report end

    Contents of master.probestats (attached file).

    I did not make any changes to the probestats_data procedure. This procedure is called from a database trigger. The trigger passes the
    entire event event to the procedure. The event is referenced within
    the procedure as "rowdata". Because the event is passed to the procedure by the trigger, I believe the "... row of status.alerts" doesn't make any difference. The procedure is not actually querying the alerts.status table. My procedure has the same "typo" and it appears to work just fine.
  • SystemAdmin
    SystemAdmin
    1283 Posts

    Re: Configuring Probes for probestats

    ‏2012-09-24T17:32:31Z  
    • Ken Tyler
    • ‏2012-09-24T14:33:46Z
    I just went thru the configuration steps and did not encounter any issues. Here is what I did using the Simnet Probe:
    1. Edit simnet.props and set
    ProbeWatchHeartbeatInterval : 60
    2. Copied probewatch.include to probes directory
    cd $OMNIHOME/extensions/roi
    cp probewatch.include $OMNIHOME/probes/linux2x86
    3. Installed ObjectServer modifications
    cd $OMNIHOME/extensions/roi
    nco_sql -server USISA < probestats.sql
    4. Modified trigger settings
    Enable stats_triggers Trigger Group
    Enable probe_statistics_cleanup Trigger
    5. Modified simnet.rules file:
    Commented out the existing Probe Watch rules and replaced with
    # Generate probe statistics events
    DefaultAlerts = registertarget( "USISA", "", "alerts.status" )
    if( match( @Manager, "ProbeWatch" ) )
    {
    include "$OMNIHOME/probes/linux2x86/probewatch.include"
    }
    else

    6. Modified probewatch.include
    cd $OMNIHOME/probes/linux2x86
    vi probewatch.include
    $OplHeartbeat_discard=1
    # Set if you want to discard the heartbeat events.
    # By default discard Heartbeat events to maintain backwards compatability

    $OplHeartbeat_populate_master_probestats=1
    # Enable if you want to send probestat data to the master.probestats table
    # stats_triggers trigger group must be enabled

    $OplHeartbeat_write_to_probe_log=1
    # Set if you want to log probestat data to the probe logfile at INFO level

    $OplHeartbeat_generate_threshold_events=0

    • Scroll down in the file and find the "genevent" statement:
    genevent( DefaultAlerts )

    These settings cause statistics to be written to a log file, and to
    generate entries in master.probe.stats every 60 seconds

    7. Started the Simnet Probe
    8. Log file entries
    cd $OMNIHOME/log
    more USISA_probestats.log
    Mon Sep 24 13:31:44 2012: master.probestats report:
    Mon Sep 24 13:31:44 2012: ProbeId: simnet@omnihost
    Mon Sep 24 13:31:44 2012: ProbeAgent: simnet
    Mon Sep 24 13:31:44 2012: ProbeHost: omnihost
    Mon Sep 24 13:31:44 2012: ProbeUpTime: 60
    Mon Sep 24 13:31:44 2012: ProbePID: 24053
    Mon Sep 24 13:31:44 2012: NumEventsProcessed: 62
    Mon Sep 24 13:31:44 2012: NumEventsGenerated: 1
    Mon Sep 24 13:31:44 2012: NumEventsDiscarded: 1
    Mon Sep 24 13:31:44 2012: RulesFileTimeSec: 0
    Mon Sep 24 13:31:44 2012: AvgRulesFileTime: 35
    Mon Sep 24 13:31:44 2012: CPUTimeSec: 0
    Mon Sep 24 13:31:44 2012: ProbeMemory: 227268
    Mon Sep 24 13:31:44 2012: master.probestats report end
    Mon Sep 24 13:32:44 2012: master.probestats report:
    Mon Sep 24 13:32:44 2012: ProbeId: simnet@omnihost
    Mon Sep 24 13:32:44 2012: ProbeAgent: simnet
    Mon Sep 24 13:32:44 2012: ProbeHost: omnihost
    Mon Sep 24 13:32:44 2012: ProbeUpTime: 120
    Mon Sep 24 13:32:44 2012: ProbePID: 24053
    Mon Sep 24 13:32:44 2012: NumEventsProcessed: 123
    Mon Sep 24 13:32:44 2012: NumEventsGenerated: 2
    Mon Sep 24 13:32:44 2012: NumEventsDiscarded: 2
    Mon Sep 24 13:32:44 2012: RulesFileTimeSec: 0
    Mon Sep 24 13:32:44 2012: AvgRulesFileTime: 35
    Mon Sep 24 13:32:44 2012: CPUTimeSec: 0
    Mon Sep 24 13:32:44 2012: ProbeMemory: 227268
    Mon Sep 24 13:32:44 2012: master.probestats report end

    Contents of master.probestats (attached file).

    I did not make any changes to the probestats_data procedure. This procedure is called from a database trigger. The trigger passes the
    entire event event to the procedure. The event is referenced within
    the procedure as "rowdata". Because the event is passed to the procedure by the trigger, I believe the "... row of status.alerts" doesn't make any difference. The procedure is not actually querying the alerts.status table. My procedure has the same "typo" and it appears to work just fine.
    Hi Mr. Tyler,

    Realy appreciate your support.. Many Many thanks..

    Issue resolved..

    I have wrongly configured below parameeter.

    • In probs rule file - DefaultAlerts = registertarget( "USISA", "", "alerts.status" )*

    • genevent( DefaultAlerts )*

    Regards,
    Manish
  • sweety@123
    sweety@123
    1 Post

    Re: Configuring Probes for probestats

    ‏2013-09-21T12:30:19Z  
    • Ken Tyler
    • ‏2012-09-24T14:33:46Z
    I just went thru the configuration steps and did not encounter any issues. Here is what I did using the Simnet Probe:
    1. Edit simnet.props and set
    ProbeWatchHeartbeatInterval : 60
    2. Copied probewatch.include to probes directory
    cd $OMNIHOME/extensions/roi
    cp probewatch.include $OMNIHOME/probes/linux2x86
    3. Installed ObjectServer modifications
    cd $OMNIHOME/extensions/roi
    nco_sql -server USISA < probestats.sql
    4. Modified trigger settings
    Enable stats_triggers Trigger Group
    Enable probe_statistics_cleanup Trigger
    5. Modified simnet.rules file:
    Commented out the existing Probe Watch rules and replaced with
    # Generate probe statistics events
    DefaultAlerts = registertarget( "USISA", "", "alerts.status" )
    if( match( @Manager, "ProbeWatch" ) )
    {
    include "$OMNIHOME/probes/linux2x86/probewatch.include"
    }
    else

    6. Modified probewatch.include
    cd $OMNIHOME/probes/linux2x86
    vi probewatch.include
    $OplHeartbeat_discard=1
    # Set if you want to discard the heartbeat events.
    # By default discard Heartbeat events to maintain backwards compatability

    $OplHeartbeat_populate_master_probestats=1
    # Enable if you want to send probestat data to the master.probestats table
    # stats_triggers trigger group must be enabled

    $OplHeartbeat_write_to_probe_log=1
    # Set if you want to log probestat data to the probe logfile at INFO level

    $OplHeartbeat_generate_threshold_events=0

    • Scroll down in the file and find the "genevent" statement:
    genevent( DefaultAlerts )

    These settings cause statistics to be written to a log file, and to
    generate entries in master.probe.stats every 60 seconds

    7. Started the Simnet Probe
    8. Log file entries
    cd $OMNIHOME/log
    more USISA_probestats.log
    Mon Sep 24 13:31:44 2012: master.probestats report:
    Mon Sep 24 13:31:44 2012: ProbeId: simnet@omnihost
    Mon Sep 24 13:31:44 2012: ProbeAgent: simnet
    Mon Sep 24 13:31:44 2012: ProbeHost: omnihost
    Mon Sep 24 13:31:44 2012: ProbeUpTime: 60
    Mon Sep 24 13:31:44 2012: ProbePID: 24053
    Mon Sep 24 13:31:44 2012: NumEventsProcessed: 62
    Mon Sep 24 13:31:44 2012: NumEventsGenerated: 1
    Mon Sep 24 13:31:44 2012: NumEventsDiscarded: 1
    Mon Sep 24 13:31:44 2012: RulesFileTimeSec: 0
    Mon Sep 24 13:31:44 2012: AvgRulesFileTime: 35
    Mon Sep 24 13:31:44 2012: CPUTimeSec: 0
    Mon Sep 24 13:31:44 2012: ProbeMemory: 227268
    Mon Sep 24 13:31:44 2012: master.probestats report end
    Mon Sep 24 13:32:44 2012: master.probestats report:
    Mon Sep 24 13:32:44 2012: ProbeId: simnet@omnihost
    Mon Sep 24 13:32:44 2012: ProbeAgent: simnet
    Mon Sep 24 13:32:44 2012: ProbeHost: omnihost
    Mon Sep 24 13:32:44 2012: ProbeUpTime: 120
    Mon Sep 24 13:32:44 2012: ProbePID: 24053
    Mon Sep 24 13:32:44 2012: NumEventsProcessed: 123
    Mon Sep 24 13:32:44 2012: NumEventsGenerated: 2
    Mon Sep 24 13:32:44 2012: NumEventsDiscarded: 2
    Mon Sep 24 13:32:44 2012: RulesFileTimeSec: 0
    Mon Sep 24 13:32:44 2012: AvgRulesFileTime: 35
    Mon Sep 24 13:32:44 2012: CPUTimeSec: 0
    Mon Sep 24 13:32:44 2012: ProbeMemory: 227268
    Mon Sep 24 13:32:44 2012: master.probestats report end

    Contents of master.probestats (attached file).

    I did not make any changes to the probestats_data procedure. This procedure is called from a database trigger. The trigger passes the
    entire event event to the procedure. The event is referenced within
    the procedure as "rowdata". Because the event is passed to the procedure by the trigger, I believe the "... row of status.alerts" doesn't make any difference. The procedure is not actually querying the alerts.status table. My procedure has the same "typo" and it appears to work just fine.

    Hello Tyler,

     

    your information is very Really appreciate . i have one question if i want to get the event to tip . how i can get it,

    i change in this property also $OplHeartbeat_discard=0 put i can't get the event on tip.

    One more question i can get the data in TDW for reports

    Thanks & Regards

    MANISH

    manish19sharma@gmail.com