From 58f77d39a910c231cb992543c1eb0124d409d184 Mon Sep 17 00:00:00 2001 From: Jack Torres Date: Wed, 19 Oct 2016 14:49:09 -1000 Subject: [PATCH] doc/agents: update 24-Working-with-agents.md fixed some grammar so it can be more easily understood fixes #32 --- doc/24-Working-with-agents.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/24-Working-with-agents.md b/doc/24-Working-with-agents.md index 33e9c312..dc019ccc 100644 --- a/doc/24-Working-with-agents.md +++ b/doc/24-Working-with-agents.md @@ -4,8 +4,8 @@ Working with Icinga 2 Agents can be quite tricky, as each Agent needs its own Endpoint and Zone definition, correct parent, peering host and log settings. There may always be reasons for a completely custom-made -configuration. I'd however strongly suggest to give the Director-assisted -variant at least a try first. It might safe you a lot of headaches. +configuration. However, I'd strongly suggest to give the Director-assisted +variant at least a try first. It might save you a lot of headaches. Preparation @@ -13,14 +13,14 @@ Preparation Agent settings are not available for modification directly on a host 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. ![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 -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 +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 +zone. If you want to move an Agent to a specific zone, just assign it 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) -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 config: @@ -48,8 +48,8 @@ for your newly created host: Create Agent-based services --------------------------- -Similar game for services that should run on your Agents. First create a -template with a meaningful name and define that Services inheriting from +Similar game for services that should run on your Agents. First, create a +template with a meaningful name. Then, define that Services inheriting from this template should run on your Agents. ![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. 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 -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) @@ -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) -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` template in custom apply rules: