The 23.10 release brings a long-requested addition to NQE data modeling: device uptime. With this, our users will be able to build queries that analyze when devices were last reloaded. Having this bit of information helps in many use cases, here a few examples:
- Devices restarting within 24 hours need to be matched with a change ticket. A device restarting without having an assigned change ticket is a strong signal that somewhere a process has failed. The problem needs to be flagged and followed upon.
- Knowing the device uptime is valuable when checking whether a device configuration has been saved from the running-config into the startup-config. It's not uncommon for network operations teams to make changes and forget to write those changes to memory after editing a device. The uptime is an element used to check against the last saved time for the config.
- Identification of devices that have a long uptime. If devices have not been rebooted in a number of years, then it is likely that the device has not been updated with proper security patches for some time. Identifying outdated devices allows networking teams to schedule downtime for upgrades.
Forward Enterprise supports the parsing of device uptime for the following vendor operating systems:
- Cisco:
IOS, IOS XE, IOS XR, NXOS, ASA - Arista:
EOS - Juniper:
JUNOS, SRX, NETSCREEN
