Forum Discussion

Ishanc's avatar
Ishanc
Icon for Contributor II rankContributor II
3 months ago

Persistent DA after device unavailable

Is it possible to make a dynamic app to keep collecting data even when a device becomes unavailable(e.g. Device failed availability check: icmp) ?
sl1
  • TonyAndres's avatar
    TonyAndres
    3 months ago

    Hello Ishanc,

    No, it is not possible for SL1 to collect data for devices that are unavailable. Whenever SL1 goes to collect data from a device, it first checks to make sure the device is available. If it is, then it collects the data. If it is not, then collection is skipped. 

    Antonio Andres

    Senior Technical Support Engineer | ScienceLogic

TonyAndres's avatar
TonyAndres
Icon for Moderator rankModerator
3 months ago

Hello Ishanc,

No, it is not possible for SL1 to collect data for devices that are unavailable. Whenever SL1 goes to collect data from a device, it first checks to make sure the device is available. If it is, then it collects the data. If it is not, then collection is skipped. 

Antonio Andres

Senior Technical Support Engineer | ScienceLogic

  • TaylorJohnson's avatar
    TaylorJohnson
    Icon for Moderator rankModerator
    3 months ago

    To add onto this. "Availability" is not as much a check of whether the device is online and working as much as it is a tool that SL1 itself uses to determine whether or not to attempt to collections. 

    You mentioned ICMP Ping, but component availability does not use this and you can turn off the availability check for components, which will allow DA execution to still happen. We have started to shift to delivering some PowerPacks without the availability check for components because sometimes it makes sense to continue collection even if the check fails. 

    You can configure a device to just not flip to "unavailable" if you want DA collection to continue attempts. This should be done with caution as if the device truly is unreachable from the SL1 collector, then letting Dynamic Applications run against it will waste collector resources, especially if they have a long timeout. 

    • Ishanc's avatar
      Ishanc
      Icon for Contributor II rankContributor II
      3 months ago

      TaylorJohnsonThanks for inputs, how can I configure a device to not flip to "unavailable", I think this might work for me.

      • TaylorJohnson's avatar
        TaylorJohnson
        Icon for Moderator rankModerator
        3 months ago

        If it's a component device, the availability check is almost always configured simply by selecting the "availability" component identifier for a collection object of your choosing in the dynamic application that is responsible for the discovery of that component. Look through the dynamic application that is responsible for discovering the component, then click through the collection objects using the wrench icon until you find which one has "availability" highlighted in the component identifier box. Do a "ctrl+click" on availability to uncheck it (this box is multiple select, so if you don't have control when you click, you'll also deselect other items).

        This may not be applicable in your case if it's not a component device or if the availability check is set with custom python.

        https://docs.sciencelogic.com/latest/Content/Web_Monitoring_Tools/Infrastructure_Health/monitoring_availability_and_latency.htm

        https://docs.sciencelogic.com/11-2-0/Content/Web_Content_Dev_and_Integration/REST_API_Cookbook/rest_cookbook_comp_disc.htm#component-identifiers