The device inventory is a comprehensive process of acquiring all relevant information about IT landscape devices. It forms the very soul of our product, is powering the principle of IT visibility through intelligent technology. In order to fully utilize it, this chapter is meant to highlight key parts of the process. The most powerful users of Raynet One are able to extend the inventory process with their own data sources and device information interpretation technology. Enrich the many views of the web interface by pushing inventory data from your organization's well established custom inventory scripts. In this chapter, we will learn the model behind the device inventory object.
Describes the overall inventory data flow from the point of collection to its persistent storage in the IT landscape device database. There are multiple stages to processing the inventory. First, a list of device inventory objects is collected per device. Additional sources such as (custom) WMI queries or scripts can produce inventory. This list is continuously put onto the device inventory interpretation desk. Interpretation involves complex contextual and common knowledge of all device details. After interpretation, all device information is merged into the IT landscape device database.
Inventory object classes
In order to connect valuable device information with a common interpretation solution, both the interpreter and the inventory collector need to speak the same language. This language is a set of predefined object types having distinct characteristic parameters. Inspiration for object definition was taken from Microsoft's WMI classses to aid WMI query compatibility. The full list of supported inventory object types is found in the respective sub-chapter.
Injection of inventory objects
The custom scripting system is the most powerful source of (custom) inventory objects. Use either .csm or .py script files to generate them based on your own business logic. On Windows devices, WMI queries are also an option.