DX Infrastructure Manager

Expand all | Collapse all

Custom Probe made with SDK toolkit keeps alerting

  • 1.  Custom Probe made with SDK toolkit keeps alerting

    Posted 01-15-2018 09:36 PM

    Hi

     

    We have created a custom probe using the Java SDK/Toolkit

     

    However, every cycle it raises 2 alerts (at severity 'clear')

    one is 'probe_discovery'

    The other is "Network Interfaces is now responding"

    ("Network Interfaces" is the name of the resource group)


    We need this custom probe since none of the CA probes can provide NIC usage as a percent of available bandwidth, and that information is required for capacity management.

     

    We decided to just switch to the Perl API.

    It doesn't support AC configuration, but it otherwise works fine.

     

    Will the Perl SDK be updated at some point (Perl 5.14 is quite old now)

    And if so, would it include the new AC interface?

     

    Regards

    Francis



  • 2.  Re: Custom Probe made with SDK toolkit keeps alerting

    Posted 01-15-2018 10:07 PM

    The probe framework SDK uses the probe_discovery message to send CI information to the discovery_server. The clear messages are harmless messages and every remote AC configured probe will send them, so I'm not sure what problem they would be causing in your environment? As for the PERL SDK, the only SDK that will ever interact with Admin Console is Java. 



  • 3.  Re: Custom Probe made with SDK toolkit keeps alerting

    Posted 01-15-2018 11:05 PM

    Thanks for the reply.

    One problem I face is that I'm going to have to run this against many thousands of resource groups.

    While the load is not excessive, it's more load, and that's not good.

     

    I don't see why a new discovery would need to be sent every cycle when nothing new is discovered. I am assuming I have made a mistake, because no other probe I've see nodes this.

    The same for the 'is now responding'. It never failed, and no other probe send these pointless alerts.

     

    And why limit AC to Java only? Maybe that's for a different thread.