Forum Discussion

Issac's avatar
Issac
Contributor III
6 months ago

Extend Internal Interface collection

Hi All,   As a default Sl1 is polling the interfaces with limited metrics , if i need to add few metrics additional is is possible to extend the internal collection?   Basically i don't want to c...
sciencelogic platform
  • JohnProctor's avatar
    JohnProctor
    5 months ago

    I have confirmed with Engineering that ifOperStatus is initially collected by our interface discovery process and then updated by our interface collection process. Therefore, if the interface Collection Frequency is set to 5 minutes, then ifOperStatus will be collected every 5 minutes.

JohnProctor's avatar
JohnProctor
Icon for Moderator rankModerator

As a general rule, it not possible for an application administrator to alter the metrics collected by internal collections processed. However, not all interface collection is enabled by default. For example, metrics for errors, discards, and packets are disabled by default. Which metrics did you want to add?

Issac's avatar
Issac
Contributor III
5 months ago

Basically i need the data for ifoper status for interface every 5 mins 

  • JohnProctor's avatar
    JohnProctor
    Icon for Moderator rankModerator
    5 months ago

    I have confirmed with Engineering that ifOperStatus is initially collected by our interface discovery process and then updated by our interface collection process. Therefore, if the interface Collection Frequency is set to 5 minutes, then ifOperStatus will be collected every 5 minutes.

    • Issac's avatar
      Issac
      Contributor III
      5 months ago

      Thanks John , Can i map the data into a performance graph or access the data via api from backend 

      • JohnProctor's avatar
        JohnProctor
        Icon for Moderator rankModerator
        5 months ago

        You can access this data via the APIs. Here are some examples...

        Example #1 (GQL)

        query Interfaces {
  interfaces (search: { device: { has: { id: { eq: 8 }}}}) {
    edges {
      node {
        device {
          id
          name
        }
        id
        name
        interfaceOperationalStatus
      }
    }
  }
}


        Example #2 (GQL)

        query Device {
  device (id: 8) {
    interfaces {
      edges {
        node {
          id
          name
          interfaceOperationalStatus
        }
      }
    }
  }
}


        Example #3 (REST)

        https://10.100.100.69/api/device/X/interface/Y
where X is the device id and Y is the interface id

Sample Results
--------------
URI: https://10.100.100.69/api/device/8/interface/3

RESULT:
<interface>
<device>/api/device/8</device>
<organization>/api/organization/7</organization>
<ifIndex>2</ifIndex>
<ifPhysAddress>00:50:56:85:1d:20</ifPhysAddress>
<ifType>6</ifType>
<ifSpeed>4294967295</ifSpeed>
<ifHighSpeed>10000</ifHighSpeed>
<ifOperStatus>1</ifOperStatus>
<ifAdminStatus>1</ifAdminStatus>
<ifConnectorPresent>1</ifConnectorPresent>
<ifLastChange>0</ifLastChange>
<ifDescr>ens192</ifDescr>
<ifblade>0</ifblade>
<ifport>2</ifport>
<ifsub>0</ifsub>
<alias/>
<state>1</state>
<collect_type>64</collect_type>
<name>ens192</name>
<rollover_alert>0</rollover_alert>
<measure>mega</measure>
<perc_type>accumulative</perc_type>
<skup_id>0</skup_id>
<poll_rate>5</poll_rate>
<alerts>1</alerts>
<edit_user>/api/account/1</edit_user>
<edit_date>1711379971</edit_date>
<disable_name_update>0</disable_name_update>
<if_speed_update>0</if_speed_update>
<collect_errors>0</collect_errors>
<collect_discards>0</collect_discards>
<collect_packet_metrics>0</collect_packet_metrics>
<virtual_topo_ignore>0</virtual_topo_ignore>
<cbqos_collection_enabled elemtype="null"/>
<discovery_type>0</discovery_type>
<max_delta>0</max_delta>
<modifier_id/>

        You can try these out on your system, by going to...
        https://<your_sl1_instance_name_or_ip_address>/gql, or 
        https://<your_sl1_instance_name_or_ip_address>/api