I would like to use some kind of a “two step” Migration from a legacy monitoring system to an icinga2 based one.
Step 1: import all hosts and associate them with a “ping-only” host template
- fiddle around with custom attributes, grouping etc.
- hosts don’t have a self-service key!
Step 2: Rollout Agents
- agents will be installed using self-service API
- using self-service API Key for host-template to be used from now on
The problem I am struggling with:
Step 2 works like charm - except: the Host-Template associated with the used Self-Service API key gets not assigned to the already existing host.
What I would like to accomplish is:
During agent-installation the template of a host does change to the one denoted by the Self-Service API key - even if there is already a template on a host.
Maybe I can use an API-Call after registration to change the template - but this needs to use Self-Service API & Templatename during installation - and I hoped to just somehow could use one parameter only: key or template name.
I have nearly the same problem.
My hosts are imported by the vSphere DB module.
I thought the template I use for the Self Service Api Is automatically assigned to the Host during installation. In my host template I have a custom var that flags the host as “Agent was installed” to assign additional services to the host.
Option 1)
in your VShpere db import you can add a sync property
Destination field inheritance (import)
Source Column → choose your template
based on filters you could do that for all of your host types
Option 2)
create in import source director
set up a sync rule with this sourcename
Destination field inheritance (import)
Source Column → choose your template
based on filters you could do that for all of your host types
Option 3)
Use IcingaWeb Director Api to fetch the Host object
change the import field
use PUT to replace the object object should be merged with your changes
or i think you can also just post a json {“imports”: [“yourtemplatename”]}
to https://icinga-master/director/host?name=hostname.example.com
I already import 1-2 Templates depending of OS. One that sets a custom property to identify that the host is a vmware vm, and one for the os from the infos given by vsphere db
But it seems its not possible trigger the import of the template that holds the self-service api key. I get an updated host in the Activity Log after installing the agent but that has no changes.
Your idea to call the Director API after installation by PowerScript seems like a good idea as I have all information i need. I’ll test this!
