[icinga-checkins] icinga.org: icinga-doc/master: beginners: add some architecture hints as well as pkg specific locations info refs #3263

git at icinga.org git at icinga.org
Thu Jan 3 01:10:33 CET 2013


Module: icinga-doc
Branch: master
Commit: 1483a37234950f9eb554138e87f140e5b4182cdb
URL:    https://git.icinga.org/?p=icinga-doc.git;a=commit;h=1483a37234950f9eb554138e87f140e5b4182cdb

Author: Michael Friedrich <michael.friedrich at netways.de>
Date:   Thu Jan  3 01:08:51 2013 +0100

beginners: add some architecture hints as well as pkg specific locations info refs #3263

---

 de/beginners.xml |   17 +++++++++++++++--
 en/beginners.xml |   24 ++++++++++++++++++------
 2 files changed, 33 insertions(+), 8 deletions(-)

diff --git a/de/beginners.xml b/de/beginners.xml
index 085ae53..46750d3 100644
--- a/de/beginners.xml
+++ b/de/beginners.xml
@@ -24,8 +24,9 @@
     <listitem>
       <para><emphasis role="bold">Verwenden Sie Pakete.</emphasis> Inzwischen gibt es für viele Distributionen passende Pakete. Denken Sie
       über die Verwendung nach anstatt aus Sourcen zu installieren. Es spart Ihnen ein bisschen Zeit. Bitte beachten Sie dabei, dass sich
-      die Pfade von denen unterscheiden, die in der Dokumentation beschrieben sind. Informationen zu Paketen finden Sie <link
-      linkend="icinga_packages">hier</link>.</para>
+      die Pfade von denen unterscheiden, die in der Dokumentation beschrieben sind. Eine detailierte Liste finden Sie auf dieser 
+      <link xlink:href="https://wiki.icinga.org/display/howtos/Package+Specific+Locations">Wiki Seite</link>.
+      Informationen zu Paketen finden Sie <link linkend="icinga_packages">hier</link>.</para>
     </listitem>
 
     <listitem>
@@ -45,6 +46,18 @@
     </listitem>
 
     <listitem>
+      <para><emphasis role="bold">Verstehen Sie die Architektur.</emphasis> &name-icinga; Core wird mit 2 GUIs ausgeliefert, &name-ui; und &name-web; &name-ui; verwendet
+      die nativen Status und Log Dateien, während &name-web; &name-idoutils; mit Datenbankbackend benötigt. Beide GUIs können am
+      am selben Host installiert sein, unterhalb von /icinga und /icinga-web.
+      Die &name-idoutils; Datenbank wird ebenso von &name-rep; auf Basis von &name-jasper; verwendet, welches als Cronk in &name-web;
+      integriert werden kann. Lesen Sie im <link linkend="ch12">&name-idoutils; Kapitel</link> weiter, um weitere Information zu den
+      &name-idoutils; Komponenten zu erhalten.
+      <link linkend="plugins">Plugins</link> sind für Ihre Checks essenziell, ebenso sollten Sie sich Gedanken über <link linkend="ch10">Addons</link>
+      in Ihrem Setup machen.
+      </para>
+    </listitem>
+
+    <listitem>
       <para><emphasis role="bold">Suchen Sie die Hilfe von anderen.</emphasis> Wenn Sie die Dokumentation gelesen haben, sich die
       Beispiel-Konfigurationsdateien angesehen und immer noch Probleme haben, dann senden Sie eine e-Mail mit der Beschreibung Ihrer
       Probleme an die <emphasis>&name-icinga;-users</emphasis>-Mailing-Liste. Aufgrund der Arbeit an diesem Projekt können wir die meisten
diff --git a/en/beginners.xml b/en/beginners.xml
index 4ec54f9..baf2bc5 100644
--- a/en/beginners.xml
+++ b/en/beginners.xml
@@ -14,26 +14,27 @@
   what it can do for you, you'll never want to be without it. :-) Here are some important things to keep in mind for first-time
   &name-icinga; users:<orderedlist>
       <listitem>
-        <para>Relax - it's going to take some time. Don't expect to be able to get things working exactly the way you want them right off
+        <para><emphasis role="bold">Relax - it's going to take some time.</emphasis> Don't expect to be able to get things working exactly the way you want them right off
         the bat. It's not that easy. Setting up &name-icinga; can involve a bit of work - partly because of the options that &name-icinga;
         offers, partly because you need to know what to monitor on your network (and how best to do it).</para>
       </listitem>
 
       <listitem>
-        <para>Meanwhile you will find packages for the most important distributions. Please consider using one of them instead of installing
-        from source. It will save you some time. Please keep in mind that the paths differ from the ones mentioned in this documentation.
+	<para><emphasis role="bold">Use package instead of source install.</emphasis> Meanwhile you will find packages for the most important distributions. Please consider
+	using one of them instead of installing from source. It will save you some time. Please keep in mind that the paths differ from the ones mentioned in this documentation.
+	For a detailed list of package specific locations, check <link xlink:href="https://wiki.icinga.org/display/howtos/Package+Specific+Locations">wiki page</link>.
         For information on packages please take a look <link linkend="icinga_packages">here</link>.</para>
       </listitem>
 
       <listitem>
-        <para>If you don't find a package or don't want to use if for whatever reason then please use the <link
+        <para><emphasis role="bold">Use the Quickstart guides.</emphasis> If you don't find a package or don't want to use if for whatever reason then please use the <link
         linkend="quickstart">quickstart</link> instructions. The quickstart installation guide is designed to get most new users up and
         running with a basic &name-icinga; setup fairly quickly. Within 20 minutes you can have &name-icinga; installed and monitoring your
         local system. Once that's complete, you can move on to learning how to configure &name-icinga; to do more.</para>
       </listitem>
 
       <listitem>
-        <para>Read the documentation. &name-icinga; can be tricky to configure when you've got a good grasp of what's going on, and nearly
+        <para><emphasis role="bold">Read the documentation.</emphasis> &name-icinga; can be tricky to configure when you've got a good grasp of what's going on, and nearly
         impossible if you don't. Make sure you read the documentation (particularly the sections on <link linkend="ch03">"Configuring
         &name-icinga;"</link> and <link linkend="ch05">"The Basics"</link>). It is important to know how <link
         linkend="plugins">plugins</link> work. Take a look at the <link linkend="monitoring_overview">monitoring overview</link> as well.
@@ -41,7 +42,18 @@
       </listitem>
 
       <listitem>
-        <para>Seek the help of others. If you've read the documentation, reviewed the sample config files, and are still having problems,
+        <para><emphasis role="bold">Understand the architecture.</emphasis> &name-icinga; Core ships with 2 GUIs, &name-ui; and &name-web;. &name-ui; uses the native status
+	and log file format, while &name-ui; requires &name-idoutils; with a database backend. Both GUIs can co-exist on the same host below
+	/icinga and /icinga-web.
+	The &name-idoutils; database is also a requirement for &name-rep; based on &name-jasper; which can be integrated into &name-web; as cronk.
+	Check <link linkend="ch12">&name-idoutils; chapter</link> for details on the &name-idoutils; components involved.
+	<link linkend="plugins">Plugins</link> are essential to your checks, as well as <link linkend="ch10">addons</link> may enhance your setup. 
+	</para>
+
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Seek the help of others.</emphasis> If you've read the documentation, reviewed the sample config files, and are still having problems,
         send an email message describing your problems to the icinga-users mailing list. If you've done some background reading and you
         provide a good problem description, odds are that someone will give you some pointers on getting things working properly. "good
         description" means to include details on your operating system, the version of &name-icinga;, as well as what you tried and the





More information about the icinga-checkins mailing list