{% extends 'generic/object_edit.html' %} {% block pre_form_fields %}
A mapping profile decides how NetBox objects become Checkmk hosts: the folder, the monitoring site, what happens per NetBox status, Checkmk's standard tags, parents and clusters.
Every Checkmk instance needs a default profile. A new installation brings the profile Default; most setups need only that one. Single devices, VMs or clusters can use another profile through the custom field Checkmk profile.
For a start a name is enough: the defaults work (folders
/{prefix}/{site}/{role}, the instance's central site, hosts for active objects,
downtimes for offline and failed ones). Every field explains itself below.