# Developer Guide: Custom Daemons

By installing the PowerShell Framework as service you have the possibility to [register custom daemons](../110-Installation/05-Background-Daemons.md) which are executed in the background. This developer guide article will assist you in creating custom daemons.

## Creating A New Module

The best approach for creating a custom daemon is by creating an independent module which is installed in your PowerShell modules directly. This will ensure you are not overwriting your custom data with possible framework updates.

### Developer Tools

To get started easier, you can run this command to create the new module:

```powershell
New-IcingaForWindowsComponent -Name 'agentservice' -ComponentType 'daemon';
```

If you wish to create the module manually, please read on.

### Manual Creation

In this guide, we will assume the name of the module is `icinga-powershell-agentservice`.

At first we will have to create a new module. Navigate to the PowerShell modules folder the Framework itself is installed to. In this tutorial we will assume the location is

```powershell
C:\Program Files\WindowsPowerShell\Modules
```

Now create a new folder with the name `icinga-powershell-agentservice` and navigate into it.

As we require a `psm1` file which contains our code, we will create a new file with the name `icinga-powershell-agentservice.psm1`. This will allow the PowerShell autoloader to load the module automatically.

**Note:** It could be possible, depending on your [execution policies](https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-6), that your module is not loaded properly. If this is the case, you can try to unblock the file by opening a PowerShell and use the `Unblock-File` Cmdlet

```powershell
Unblock-File -Path 'C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-agentservice\icinga-powershell-agentservice.psm1'
```

## Testing The Module

Once the modules files are created and unblocked, we can start testing if the autoloader is properly working and our module is detected.

For this open the file `icinga-powershell-agentservice.psm1` in your preferred editor and add the following code snippet

```powershell
function Test-MyIcingaAgentServiceCommand()
{
    Write-Host 'Module was loaded';
}
```

Now open a **new** PowerShell terminal or write `powershell` into an already open PowerShell prompt and execute the command `Test-MyIcingaAgentServiceCommand`.

If everything went properly, you should now read the output `Module was loaded` in our prompt. If not, you can try to import the module by using

```powershell
Import-Module 'C:\Program Files\WindowsPowerShell\Modules\icinga-powershell-agentservice\icinga-powershell-agentservice.psm1';
```

inside your console prompt. After that try again to execute the command `Test-MyIcingaAgentServiceCommand` and check if it works this time. If not, you might check the naming of your module to ensure `folder name` and `.psm1 file name` is identical.

## Create A New function

Once everything is working properly we can create our starting function we will later use for [registering our daemon](../110-Installation/05-Background-Daemons.md).

For naming guidelines we will have to begin with the `Start` naming and an identifier of what are going to achieve with our daemon. In our example we will frequently check if the Icinga 2 agent service is active and running. In case it failed, we will restart the service.

So lets get started with the function

```powershell
function Start-IcingaAgentServiceTest()
{
    # Our code belongs here
}
```

## Basic Daemon Architecture

A basic daemon consists of two parts. At first we require a function our daemon loader will start, creating a new thread by using `New-IcingaThreadInstance`. In addition, we require another function which will then be executed as our thread call.

Each daemon must spawn within an own thread to ensure we are not blocking the execution of other daemons and interfere with the framework loader.

## Writing Our Thread Function

As we start a new thread, we will require at first to provide some basic details, like our `$IcingaGlobalData` variable.

At first we will create a new function which our thread is calling. As we intend to add some, we should use the `Add` convention.

```powershell
function Add-IcingaAgentServiceTest()
{
    # Everything which will be executed inside the thread
    # belongs here
}
```

Depending on our daemon, later usage and possible sharing of data between all loaded daemons might be required. In addition we might want to spawn child threads as single tasks being executed. To access the global, shared data, use can use the `Global:Icinga.Public` variable. This content is shared automatically between each single created thread.

Our recommendation is to always do this for every daemon, as later changes might be more complicated and time consuming.

```powershell
function Add-IcingaAgentServiceTest()
{
    # Everything which will be executed inside the thread
    # belongs here
}
```

Now as the basic part is finished, we will require to make our framework libraries available within this thread. To do so, we will initialise the framework with the `Use-Icinga` Cmdlet, do however only import libraries and tell the framework that the wish to utilize it as `daemon`. The last part is important, as this will change the handling for writing console outputs and instead of an `exit` for certain failures the module will log them internally.

```powershell
function Add-IcingaAgentServiceTest()
{
    # Import the framework library components and initialise it
    # as daemon
    Use-Icinga -LibOnly -Daemon;
}
```

As we will parse the `global` framework data anyways, we should already make use of it. In this case, we will write the current service state of Icinga 2 into a global `synchronized` hashtable. Before we can do this, we will have to add a new hashtable to our background daemons

```powershell
function Add-IcingaAgentServiceTest()
{
    # Import the framework library components and initialise it
    # as daemon
    Use-Icinga -LibOnly -Daemon;

    # Add a hashtable to the public data background
    # daemon hashtable to write data to. In addition it will
    # allow to share data collected from this daemon with others
    $Global:Icinga.Public.Daemons.Add('TestIcingaAgentService', @{ });

    # This will add another hashtable to our previous
    # TestIcingaAgentService hashtable to store actual service
    # information
    $Global:Icinga.Public.Daemons.TestIcingaAgentService.Add('ServiceState', @{ });
}
```

As now our base skeleton for daemon is ready we can start to write the actual part which will execute the code to check for our Icinga Agent service state.

Because the code is executed as separate thread, we will have to ensure it will run as long as the PowerShell service is being executed. This will be done with a simple `while` loop

```powershell
function Add-IcingaAgentServiceTest()
{
    # Import the framework library components and initialise it
    # as daemon
    Use-Icinga -LibOnly -Daemon;

    # Add a hashtable to the public data background
    # daemon hashtable to write data to. In addition it will
    # allow to share data collected from this daemon with others
    $Global:Icinga.Public.Daemons.Add('TestIcingaAgentService', @{ });

    # This will add another hashtable to our previous
    # TestIcingaAgentService hashtable to store actual service
    # information
    $Global:Icinga.Public.Daemons.TestIcingaAgentService.Add('ServiceState', @{ });

    # Keep our code executed as long as the PowerShell service is
    # being executed. This is required to ensure we will execute
    # the code frequently instead of only once
    while ($TRUE) {
    }
}
```

*ALWAYS* ensure you add some sort for `sleep` at the end of the `while` loop to allow your CPU some breaks. If you do not do this, you might suffer from high CPU loads. The `sleep duration` interval can depend either on a simple CPU cycle break or by telling the daemon to execute tasks only in certain Intervalls. In our case we wish to execute the daemon every `5 seconds`.

```powershell
function Add-IcingaAgentServiceTest()
{
    # Import the framework library components and initialise it
    # as daemon
    Use-Icinga -LibOnly -Daemon;

    # Add a hashtable to the public data background
    # daemon hashtable to write data to. In addition it will
    # allow to share data collected from this daemon with others
    $Global:Icinga.Public.Daemons.Add('TestIcingaAgentService', @{ });

    # This will add another hashtable to our previous
    # TestIcingaAgentService hashtable to store actual service
    # information
    $Global:Icinga.Public.Daemons.TestIcingaAgentService.Add('ServiceState', @{ });

    # Keep our code executed as long as the PowerShell service is
    # being executed. This is required to ensure we will execute
    # the code frequently instead of only once
    while ($TRUE) {
        # ALWAYS add some sort of sleep at the end. Either to
        # break the CPU cycle and give it some break or to
        # ensure daemon tasks are executed on a certain interval
        Start-Sleep -Seconds 5;
    }
}
```

This is basically the foundation of every single daemon you will write. Now we will add the actual task our daemon will execute while it is running. As mentioned before, we will test if our Icinga 2 Agent service is running and restart it if it is stopped. To keep track of the current status and possible errors during restart, we will add additional `synchronized` hashtables to store the `value` of the current service status and possible `restart_error` counts. To count the `restart_error` we will have to initialises a single variable we name `$RestartErrors` before we enter our `while` loop.

```powershell
function Add-IcingaAgentServiceTest()
{
    # Import the framework library components and initialise it
    # as daemon
    Use-Icinga -LibOnly -Daemon;

    # Add a hashtable to the public data background
    # daemon hashtable to write data to. In addition it will
    # allow to share data collected from this daemon with others
    $Global:Icinga.Public.Daemons.Add('TestIcingaAgentService', @{ });

    # This will add another hashtable to our previous
    # TestIcingaAgentService hashtable to store actual service
    # information
    $Global:Icinga.Public.Daemons.TestIcingaAgentService.Add('ServiceState', @{ });

    # Initialise our error counter variable
    [int]$RestartErrors = 0;

    # Keep our code executed as long as the PowerShell service is
    # being executed. This is required to ensure we will execute
    # the code frequently instead of only once
    while ($TRUE) {
        # Get the current service information. If the service is
        # not installed, continue silently to return $null
        $ServiceState = Get-Service 'icinga2' -ErrorAction SilentlyContinue;

        # Only execute our code if the Icinga Agent service is
        # installed
        if ($null -ne $ServiceState) {
            # Add the current service state to our hashtable.
            Add-IcingaHashtableItem `
                -Hashtable $Global:Icinga.Public.Daemons.TestIcingaAgentService.ServiceState `
                -Key 'value' `
                -Value $ServiceState.Status `
                -Override | Out-Null;

            # Restart the service if it is not running
            if ($ServiceState.Status -ne 'Running') {
                try {
                    # Try to restart the service
                    Restart-Service 'icinga2' -ErrorAction Stop;

                    Add-IcingaHashtableItem `
                        -Hashtable $Global:Icinga.Public.Daemons.TestIcingaAgentService.ServiceState `
                        -Key 'restart_error' `
                        -Value 0 `
                        -Override | Out-Null;
                } catch {
                    # Add an error counter in case we failed
                    $RestartErrors += 1;
                    Add-IcingaHashtableItem `
                        -Hashtable $Global:Icinga.Public.Daemons.TestIcingaAgentService.ServiceState `
                        -Key 'restart_error' `
                        -Value $RestartErrors `
                        -Override | Out-Null;
                }
            }
        }
        # ALWAYS add some sort of sleep at the end. Either to
        # break the CPU cycle and give it some break or to
        # ensure daemon tasks are executed on a certain interval
        Start-Sleep -Seconds 5;
    }
}
```

## Calling Our Function

Once our function is completed we only require to call it once our daemon is registered. Do to so, we will use the Cmdlet `New-IcingaThreadInstance`.

As arguments we will have to add a unique `name` to use for this thread as well as a `thread pool`, on which the function will be added to. The name of the thread is automatically constructed based on the caller function, the function being executed and the given name. If you create a thread which is used as a `main` thread for several sub-threads, you could call it `Main`. For our example, the constructed thread name will then internally be `Start-IcingaAgentServiceTest::IcingaAgentServiceTest::Main::0`. The last added digit will auto increment, in case you are adding the identical thread multiple times, allowing you to access certain threads again by their index id. For the thread pool, we will use the default thread pool `MainPool` of Icinga for Windows. To customize this, you can use `Add-IcingaThreadPool` with a unique name and the amount if allowed instances. Last but not least we require to parse possible `Arguments` to our function and tell the thread to `Start` right after being created.

This call will be added inside the `Start-IcingaAgentServiceTest` we created earlier and didn't touch so far yet.

```powershell
function Start-IcingaAgentServiceTest()
{
    # Now create a new thread and use our previous created
    # function as command to call it and parse all our
    # arguments to it
    New-IcingaThreadInstance `
        -Name 'Main' `
        -ThreadPool (Get-IcingaThreadPool -Name 'MainPool') `
        -Command 'Add-IcingaAgentServiceTest' `
        -CmdParameters @{ } `
        -Start;
```

## Register Our Daemon

Now as our daemon is ready we can simply [register it](../110-Installation/05-Background-Daemons.md) by using the Framework commands

```powershell
Register-IcingaBackgroundDaemon -Command 'Start-IcingaAgentServiceTest';
```

Once registered, you will have to restart the PowerShell service itself to apply the changes

```powershell
Restart-IcingaWindowsService;
```

Thats it! Now the daemon is loaded with every start, checking for the Agent state and restart it if it is not running.

**Note:** In order to restart the Icinga Agent service, the user the PowerShell service is running with requires these kind of privileges. Otherwise it will throw an error and the error counter will increase

## Developer Console

During development you might want to test the current implementation and check if everything is working as intended. To do so, you require to open a PowerShell terminal as `administrator`. We would recommend to `stop` the PowerShell service in this case to prevent possible daemons writing files to the system and overwriting each others.

Once the service is stopped and your `administrative PowerShell` is open, we will have to initialise the Framework and start the background daemon component

```powershell
Use-Icinga;
Start-IcingaForWindowsDaemon;
```

Once done you will receive back your prompt, however all registered background daemons are running. To access the collected data from daemons, you can print the content of the `global` framework data. If you wish to check if your daemon was loaded properly and data is actually written, we can access our created hashtable and get the current service state of it

```powershell
$Global:Icinga.Public.Daemons.TestIcingaAgentService.ServiceState['value'];
```

In case your Icinga Agent service is installed and your daemon is running properly, this should print the current state of the service.

Of course for more complex daemons you are able to manipulate data directly or add more detailed debug output.
