In Raynet One , plugins are core functional elements ensuring that inventory and discovery jobs can be processed. This chapter series is about the management of plugins.
What is a plugin?
A plugin is a provider of communication, interpretation and scanning technology to the platform. Its main logic is executed on the runner device. It can recognize IT resource descriptions from foreign domains/systems and translate it into Raynet One inventory objects. Technical platform-based restrictions exist. Every plugin is divided into a set of plugin instruments, each addressable on its own (other undocumented and negligible plugin feature types exist). If two plugins serve the same purpose, the quality of their results may differ (for ex. legacy vs. recommended).
When platform jobs are executed, they are handed the selection of plugin instruments. This selection is defined during platform job configuration. It is important to emphasize instrument selection conflicts. If at least 2 plugin instruments are selected, their order of application is not guaranteed. Although, certain factors are known to influence it.
•plugin DLL filename order
•plugin-internal arrangement
•filesystem design & implementation
•C# runtime library implementation
Thus, avoid the selection of multiple plugins for distinct and predictable job results.
Settle on the truly required set of enabled plugins to focus the platform user experience. After all, disabled plugins and their instruments are not mentioned as part of job configuration wizards. Purely Unix-like-based IT landscapes are safe to disable all Windows-specific plugins (and vice-versa).
Only Raynet is meant to create plugins. You can suggest their creation and improvement. On the other hand, skill and new technological developments inspire the product's evolution.
Runner commands for job execution are sent to individual runner device with the entire job configuration. In conclusion, the runner can select and configure the right plugins for the job. Furthermore, IP network communication load and form does differ from one plugin to another. You should optimize plugin use to impact the platform performance positively (custom inventory scripts, plugin improvement, best-practice IT landscape device-internal configuration).
|
Note: |
|
Tip: •support of new authentication methods •inventory collection quality |
Currently provided set of plugins at the time of writing (24th of April, 2025). Choose the right ones and configure them in the most appropriate way to get the most out of Raynet One!