Icinga for Windows custom Plugin

Icinga 2 Icinga for Windows
1

Good Day all,

I’m currently trying to create a custom plugin following the Icinga guide. When I manually import and unblock, it works in one PowerShell session. However, if I close that PowerShell session and start a new one, I only get the following message from PowerShell: 'is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

In the web interface, I only see: 'Icinga Invalid Configuration Error was thrown: PluginNotInstalled.

Can anyone tell me which setting it is to permanently set the unblock and import?
Because I believe I’m currently putting obstacles in my own way.

THX

2

Hello and thank you for your message.
Did you create the PowerShell Module manually or did you use the developer tools to do so?

In general, you can try to import a module by using the -Global flag.

However, Icinga for Windows should deal with module imports by itself.

Does your project contains a module .psm1 file inside the root folder of the module?

In case it does, please make sure a function like this is present:

function Import-IcingaPowerShellComponentMyCustomModule()
{
    # Allows other components to load this component
}

Does functions are fetched by Icinga for Windows during startup and ensures the autoloading of the plugins is done.

3

Yes i create it with dev.-tools
If I unblock and import this custom check it works only for this powershell session. I tried a lot of ways to import this checks permanently. If I open up a new powershell session i directly got the message “is not recognized as the name of a cmdlet”