Statseeker polls different objects and stores values at different rates depending on the type of data, its relative importance, the likely number of the objects on the network and the likely frequency that the data is going to change.
For example, the number of octets transmitted from an interface is of relatively high importance and is likely to change frequently, so it is polled every minute. Configuration data, such as device name, is unlikely to change and is consequently only collected during the initial discovery and daily rewalks.
Outside of API-only integrations, such as Cisco ACI, Statseeker polls your network devices via SNMP. Due to manufacturer specific differences in what data is available via SNMP, and the location of that data in the MIB, Statseeker identifies the devices and then polls accordingly.
Statseeker also creates Custom Data Types (CDTs) in response to advances in technology making:
- New devices network aware
- Enhancements to existing network aware devices resulting in a wider range of data/metrics being made available for collection and analysis
CDTs are data description packages provided by Statseeker that can be used to:
- Extend the types of devices that can be polled by Statseeker
- Extend the data that can be collected by Statseeker’s polling process
As a customer, you can request a CDT package to suit your requirements and Statseeker will work with you to provide a package with the ability to poll the device, return the data and provide the reporting functionality to make use of the custom data. Periodically, released CDTs are rolled into the Statseeker product, becoming part of the default Statseeker deployment.
For more information on CDTs see Custom Data Types.