tyler.durden/icingaweb2-module-director
1
0
Fork 0
mirror of https://github.com/Icinga/icingaweb2-module-director.git synced 2025-07-31 01:34:12 +02:00
Code Issues Packages Projects Releases Wiki Activity

doc/agents: update 24-Working-with-agents.md

Browse Source 
fixed some grammar so it can be more easily understood

fixes #32
This commit is contained in:
Jack Torres 2016-10-19 14:49:09 -10:00 committed by Thomas Gelf
parent f7d1444fd9
commit 58f77d39a9
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
doc/24-Working-with-agents.md
View File

@ -4,8 +4,8 @@
Working with Icinga 2 Agents can be quite tricky, as each Agent needs Working with Icinga 2 Agents can be quite tricky, as each Agent needs
its own Endpoint and Zone definition, correct parent, peering host and its own Endpoint and Zone definition, correct parent, peering host and
log settings. There may always be reasons for a completely custom-made log settings. There may always be reasons for a completely custom-made
configuration. I'd however strongly suggest to give the Director-assisted configuration. However, I'd strongly suggest to give the Director-assisted
variant at least a try first. It might safe you a lot of headaches. variant at least a try first. It might save you a lot of headaches.
Preparation Preparation
@ -13,14 +13,14 @@ Preparation
Agent settings are not available for modification directly on a host Agent settings are not available for modification directly on a host
object. This requires you to create an "Icinga Agent" template. You object. This requires you to create an "Icinga Agent" template. You
could name it exactly like that, it's important to use meaningful names could name it exactly like that; it's important to use meaningful names
for your templates. for your templates.
![Create an Agent template](screenshot/director/24-agents/2401_agent_template.png) ![Create an Agent template](screenshot/director/24-agents/2401_agent_template.png)
As long as you're not using Satellite nodes a single Agent zone is all As long as you're not using Satellite nodes, a single Agent zone is all
you need. Otherwise you should create one Agent template per satellite you need. Otherwise, you should create one Agent template per satellite
zone. If you want to move an Agent to a specific zone just assign it zone. If you want to move an Agent to a specific zone, just assign it
the correct template and you're all done. the correct template and you're all done.
@ -31,7 +31,7 @@ Well, create a host, choose an Agent template, that's it:
![Create an Agent-based host](screenshot/director/24-agents/2402_create_agent_based_host.png) ![Create an Agent-based host](screenshot/director/24-agents/2402_create_agent_based_host.png)
Once you import the "Icinga Agent" template you'll see a new "Agent" tab. Once you import the "Icinga Agent" template, you'll see a new "Agent" tab.
It tries to assist you with the initial Agent setup by showing a sample It tries to assist you with the initial Agent setup by showing a sample
config: config:
@ -48,8 +48,8 @@ for your newly created host:
Create Agent-based services Create Agent-based services
--------------------------- ---------------------------
Similar game for services that should run on your Agents. First create a Similar game for services that should run on your Agents. First, create a
template with a meaningful name and define that Services inheriting from template with a meaningful name. Then, define that Services inheriting from
this template should run on your Agents. this template should run on your Agents.
![Agent-based service](screenshot/director/24-agents/2406_agent_based_service.png) ![Agent-based service](screenshot/director/24-agents/2406_agent_based_service.png)
@ -57,7 +57,7 @@ this template should run on your Agents.
Please do not set a cluster zone, as this would rarely be necessary. Please do not set a cluster zone, as this would rarely be necessary.
Agent-based services will always be deployed to their Agent's zone by Agent-based services will always be deployed to their Agent's zone by
default. All you need to do now for services that should be executed default. All you need to do now for services that should be executed
on your Agents ist importing that template: on your Agents is importing that template:
![Agent-based load check](screenshot/director/24-agents/2407_create_agent_based_load_check.png) ![Agent-based load check](screenshot/director/24-agents/2407_create_agent_based_load_check.png)
@ -70,7 +70,7 @@ generated config differs now:
![Agent-based service assigned to host template](screenshot/director/24-agents/2410_agent_based_service_rendered_for_host_template.png) ![Agent-based service assigned to host template](screenshot/director/24-agents/2410_agent_based_service_rendered_for_host_template.png)
While a service added to a host template are implicitely rendered as While services added to a host template are implicitly rendered as
assign rules, you could of course also use your `Agent-based service` assign rules, you could of course also use your `Agent-based service`
template in custom apply rules: template in custom apply rules: