{% extends 'admin/master.html' %} {% block body %}
What the generation rules would make of the hosts you have right now. The same host attributes are read, the same groups are looked up in the directory and the same Jinja is rendered as in a real run — only the writing is left out. Nothing is created, updated or deleted here. Documentation
{% if not rules %}{{ rows|length }} group(s). new in Checkmk = no user with this ID exists yet and one would be created, update = the user exists and the marked fields would change, already correct = the user exists and nothing would change, skipped = no user is written, with the reason next to it.
| Rule | Host value | Searched as | In the directory | Checkmk user ID | In Checkmk | Fields of that user | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| {{ row.rule }} | {{ row.original_name }} |
{{ row.name }}
{% if row.name != row.original_name %}
rewritten
{% endif %}
|
{% if not row.searched %} no LDAP account on the rule, not looked up {% elif row.found %} found, {{ row.attributes|length }} attribute(s) {% else %} no such group in the directory {% endif %} | {{ row.user_id or '—' }} |
{% if row.action == 'create' %} new in Checkmk {% elif row.action == 'update' %} update {% elif row.action == 'unchanged' %} already correct {% else %} skipped {% endif %} |
{% if row.note %}
{{ row.note }}
{% else %}
Variables the group carries ({{ row.attributes|length }}){% if not row.attributes %}
{% if not row.searched %}
The rule has no LDAP account, so the
directory was never asked and no
variable exists. Every Jinja field can
only use
|