2006-09-14 Raul Mateos <raulofpandora@gmail.com>

* Updated id in pandora_doc/en/pandora_chapter[1-9].xml (!7)

git-svn-id: https://svn.code.sf.net/p/pandora/code/trunk@170 c3f86ba8-e40f-0410-aaad-9ba5e7f4b01f
This commit is contained in:
raulmateos 2006-09-14 11:52:24 +00:00
parent a2c12da531
commit ffd63928db
9 changed files with 56 additions and 52 deletions

View File

@ -1,8 +1,12 @@
2006-09-14 Raul Mateos <raulofpandora@gmail.com>
* Updated id in pandora_doc/en/pandora_chapter[1-9].xml (!7)
2006-09-13 Raul Mateos <raulofpandora@gmail.com>
* New /en/images/ files
* New pandora_doc/en/images/ files
* Updated /en/pandora_chapter 1 to 9.xml
* Updated pandora_doc/en/pandora_chapter 1 to 9.xml
2006-09-12 Raul Mateos <raulofpandora@gmail.com>
@ -12,9 +16,9 @@
* Updated fdl.xml & gpl.xml
* Moved all the english files to /en/ directory
* Moved all the english files to pandora_doc/en/ directory
* Created /es/ directory
* Created pandora_doc/es/ directory
2006-09-11 Sancho Lerena <slerena@artica.es>

View File

@ -2,7 +2,7 @@
<chapter id="chapter1">
<title>Introduction</title>
<sect1 id="1.1">
<sect1 id="sec1.1">
<title>What is Pandora?</title>
<para>Pandora is a monitoring tool that allows a system administrator
@ -88,7 +88,7 @@
in virtually any language, given its simple API and being open source.
</para>
</sect1>
<sect1 id="1.2">
<sect1 id="sec1.2">
<title>Pandora Administration</title>
<para>

View File

@ -40,7 +40,7 @@
incidents, manage database or other.
</para>
<sect1 id="2.1">
<sect1 id="sec2.1">
<title>Profile manager</title>
<para>
@ -119,7 +119,7 @@
</itemizedlist>
</sect1>
<sect1 id="2.2">
<sect1 id="sec2.2">
<title>Adding a user</title>
<para>
@ -153,7 +153,7 @@
hand side of the profile.
</para>
</sect1>
<sect1 id="2.3">
<sect1 id="sec2.3">
<title>Deleting a user</title>
<para>
@ -164,7 +164,7 @@
<graphic fileref="images/image005.png" valign="bottom" align="center"/>
</para>
</sect1>
<sect1 id="2.4">
<sect1 id="sec2.4">
<title>Statistics</title>
<para>
The user activity statistics show a graph with the
@ -177,14 +177,14 @@
menu to show this graph:
<graphic fileref="images/image006.png" valign="bottom" align="center"/> </para>
</sect1>
<sect1 id="2.5">
<sect1 id="sec2.5">
<title>Messages to users</title>
<para>
To create a new message to other user, go to "Messages"
section in the Operation menu. You can also read the
received messages, but the sent messages are not stored.
</para>
<sect2 id="2.5.1">
<sect2 id="sec2.5.1">
<title>Messages to groups</title>
<para>
From "Messages"&gt;"Messages to groups" section in the

View File

@ -34,7 +34,7 @@
</listitem>
</itemizedlist>
<sect1 id="3.1">
<sect1 id="sec3.1">
<title>Group Manager</title>
<para>Groups are added in "Manage Profiles" &gt; "Manage Groups",
@ -77,7 +77,7 @@
<inlinegraphic fileref="images/cancel.gif"/>
in the right hand side of each group.</para>
</sect1>
<sect1 id="3.2">
<sect1 id="sec3.2">
<title>Adding an agent</title>
<para>Before an agent is added, the public key of the
@ -163,7 +163,7 @@
</para>
</listitem>
</itemizedlist>
<sect2 id="3.2.1">
<sect2 id="sec3.2.1">
<title>Assigning modules</title>
<para>Pandora's agents use the operating system own commands to
@ -262,7 +262,7 @@
However, the type of data of the module can't be modified.
</para>
</sect2>
<sect2 id="3.2.2">
<sect2 id="sec3.2.2">
<title>Alerts</title>
<para>
@ -273,7 +273,7 @@
anything that can be triggered by a script configured in
Pandora's Operating System.
</para>
<sect3 id="3.2.2.1">
<sect3 id="sec3.2.2.1">
<title>Adding an Alert</title>
<para>
@ -377,7 +377,7 @@
</listitem>
</itemizedlist>
</sect3>
<sect3 id="3.2.2.2">
<sect3 id="sec3.2.2.2">
<title>Assigning Alerts</title>
<para>
@ -453,7 +453,7 @@
in the Adminitration menu and selecting the agent.</para>
</sect3>
</sect2>
<sect2 id="3.2.3">
<sect2 id="sec3.2.3">
<title>Agent module and agent's alert management</title>
<para>It might happen that the user finds that modules and alerts
@ -490,7 +490,7 @@
deletion is performed, the data associated to them will also be
deleted.</para>
</sect2>
<sect2 id="3.2.4">
<sect2 id="sec3.2.4">
<title>Agents group detail</title>
<para>Once you have configured your groups and agents, you can
@ -507,7 +507,7 @@
that group.</para>
</sect2>
</sect1>
<sect1 id="3.3">
<sect1 id="sec3.3">
<title>Agent monitoring</title>
<para>When the agents start the data transmission to the server,
@ -515,7 +515,7 @@
the data in the Database. The data are consolidated and can be
accessed from the Web console, either as row data or as graphs.</para>
<sect2 id="3.3.1">
<sect2 id="sec3.3.1">
<title>Agent view</title>
<para>All the Agents can be accessed from the Operation menu.
@ -601,12 +601,12 @@
Administration menu.
</para>
</sect2>
<sect2 id="3.3.2">
<sect2 id="sec3.3.2">
<title>Accessing the data of an agent</title>
<para>When an agent is accessed, by clicking on its name, all the
information related to that agent is displayed.</para>
<sect3 id="3.3.2.1">
<sect3 id="sec3.3.2.1">
<title>Agent general info</title>
<para>This shows the data introduced when the agent was created
@ -614,7 +614,7 @@
<graphic fileref="images/image016.png" valign="bottom" align="center"/>
</sect3>
<sect3 id="3.3.2.2">
<sect3 id="sec3.3.2.2">
<title>Last data received</title>
<para>This is the description of all the agent modules
@ -666,7 +666,7 @@
<para> - <inlinegraphic fileref="images/data_w.gif"/> Last week</para>
<para> - <inlinegraphic fileref="images/data_d.gif"/> Last day</para>
</sect3>
<sect3 id="3.3.2.3">
<sect3 id="sec3.3.2.3">
<title>Complete list of monitors</title>
<para>This is the description of all the monitors defined by
@ -696,7 +696,7 @@
the last data packaged received from the agent</para>
</sect3>
<sect3 id="3.3.2.4">
<sect3 id="sec3.3.2.4">
<title>Complete list of alerts</title>
<para>This is the description of all the alarms defined
@ -724,7 +724,7 @@
one alert has been sent</para>
</sect3>
</sect2>
<sect2 id="3.3.3">
<sect2 id="sec3.3.3">
<title>Group details</title>
<para>The groups configured in Pandora can be
@ -758,7 +758,7 @@
<para><emphasis>Failed:</emphasis> Number of failing monitors.</para>
<para><emphasis>Down:</emphasis> Number of down monitors.</para>
</sect2>
<sect2 id="3.3.4">
<sect2 id="sec3.3.4">
<title>Monitors view</title>
<para>The description of all the monitors defined in the server
@ -771,7 +771,7 @@
in the individual view, but now they are shown all together.
This allows a deeper analisys of each monitor.</para>
</sect2>
<sect2 id="3.3.5">
<sect2 id="sec3.3.5">
<title>Alert details</title>
<para>The description of all the alerts defined in the server
@ -784,7 +784,7 @@
as in the individual view, but now they are shown all together.
This allows a deeper analisys of each alert.</para>
</sect2>
<sect2 id="3.3.6">
<sect2 id="sec3.3.6">
<title>Data Export</title>
<para>The Data Export tool can be found in the "View Agents"&gt;"
@ -812,7 +812,7 @@
<graphic fileref="images/image030.png" valign="bottom" align="center"/>
</sect2>
<sect2 id="3.3.7">
<sect2 id="sec3.3.7">
<title>Statistics</title>
<para>Two kinds of graphical statistics are displayed from the
@ -834,10 +834,10 @@
<graphic fileref="images/image033.png" valign="bottom" align="center"/>
</sect2>
</sect1>
<sect1 id="3.4">
<sect1 id="sec3.4">
<title>SNMP Console</title>
<para></para>
<sect2 id="3.4.1">
<sect2 id="sec3.4.1">
<title>SNMP Alerts</title>
<para></para>
</sect2>

View File

@ -125,7 +125,7 @@
from one user to another. The incident can be assigned to another user
by its owner, or by a user with management privileges over the group
the incidents belong to.</para>
<sect1 id="4.1">
<sect1 id="sec4.1">
<title>Adding an incident</title>
<para>The creation of incidents is performed by clicking on
@ -137,7 +137,7 @@
fields to define the incident. The process is completed by clicking
on the "Create" button.</para>
</sect1>
<sect1 id="4.2">
<sect1 id="sec4.2">
<title>Incident follow up</title>
<para>All the open incidents can be followed up. The tool is reached by
@ -175,7 +175,7 @@
</listitem>
</itemizedlist>
<para>The indicent is updated by clicking on the "Update incident" button.</para>
<sect2 id="4.2.1">
<sect2 id="sec4.2.1">
<title>Adding comments to an incident</title>
<para> Comments about the incident can added clicking on "Add note".
@ -195,7 +195,7 @@
and only the owners of the incident or of the notes can delete them.
</para>
</sect2>
<sect2 id="4.2.2">
<sect2 id="sec4.2.2">
<title>Attaching files to an incident</title>
<para>Sometimes it is necessary to link an incident with an image,
@ -219,7 +219,7 @@
<graphic fileref="images/image040.png" valign="bottom" align="center"/>
</sect2>
</sect1>
<sect1 id="4.3">
<sect1 id="sec4.3">
<title>Searching for an incident</title>
<para>A specific incident can be found amongst the incidents created
@ -236,7 +236,7 @@
the attached files. The search can be performed in addition to group, priority
or status filters.</para>
</sect1>
<sect1 id="4.4">
<sect1 id="sec4.4">
<title>Statistics</title>
<para>The incident statisticts are shown in the "Manage Incidents"&gt;"Statistics"

View File

@ -21,7 +21,7 @@
<para>The event information list shows the data in the following columns:</para>
<para><emphasis>Status:</emphasis> The event status is represented by the icon bellow:</para>
<para><emphasis>Status:</emphasis> The event status is represented by the icon below:</para>
<para><inlinegraphic fileref="images/dot_green.gif"/> The event has been validated</para>
<para><inlinegraphic fileref="images/dot_red.gif"/> The event hasn't been validated</para>
<para><emphasis>Event name:</emphasis> Name assigned to the event by Pandora.</para>
@ -39,7 +39,7 @@
<para>The events can be also validated or deleted in groups by selecting
the tick boxes on the last column of the event, and pressing "Validate" or
"Delete" at the bottom of the list.</para>
<sect1 id="5.1">
<sect1 id="sec5.1">
<title>Statistics</title>
<para>Three different kinds of graphical statistic representation can be

View File

@ -27,7 +27,7 @@
<para><emphasis>Source IP:</emphasis> IP of the machine or the agent that provoked the entry.</para>
<para><emphasis>Comment:</emphasis> Comment describing the entry</para>
<sect1 id="6.1">
<sect1 id="sec6.1">
<title>Statistics</title>
<para>There isn't a special section to view system audit statistics. However, we could use a graph generated in the Users section to evaluate the actions of each user, as this graph would represent the total

View File

@ -31,7 +31,7 @@
</para>
<graphic fileref="images/image054.png" valign="bottom" align="center"/>
<sect1 id="8.1">
<sect1 id="sec8.1">
<title>DB Information</title>
<para>The DB statistics are generated by Agent, on the
@ -57,16 +57,16 @@
<para>These graphs can be also viewed from
"View Agents"&gt;"Statistics" in the Operation menu.</para>
</sect1>
<sect1 id="8.2">
<sect1 id="sec8.2">
<title>Manual purge of the Datadase</title>
<para>Pandora counts with powerful tools for the
Administrator to manually purge the majority of data stored in the Database.
This includes data generated by both the agents and the own server.</para>
</sect1>
<sect1 id="8.3">
<sect1 id="sec8.3">
<title>Agent's data purge</title>
<sect2 id="8.3.1">
<sect2 id="sec8.3.1">
<title>Debuging selected data from a module</title>
<para>
@ -99,7 +99,7 @@
will be permanently deleted from the database.
</para>
</sect2>
<sect2 id="8.3.2">
<sect2 id="sec8.3.2">
<title>Purging all the agent's data</title>
<para>
@ -140,9 +140,9 @@
<graphic fileref="images/image059.png" valign="bottom" align="center"/>
</sect2>
</sect1>
<sect1 id="8.4">
<sect1 id="sec8.4">
<title>Purging system data</title>
<sect2 id="8.4.1">
<sect2 id="sec8.4.1">
<title>Audit data purge</title>
<para>
@ -181,7 +181,7 @@
<graphic fileref="images/image060.png" valign="bottom" align="center"/>
</sect2>
<sect2 id="8.4.2">
<sect2 id="sec8.4.2">
<title>Event data purge</title>
<para>

View File

@ -42,7 +42,7 @@
It's not recommended to use value above 6 if the data needs to be
represented graphically in large time intervals.
</para>
<sect1 id="9.1">
<sect1 id="sec9.1">
<title>Links</title>
<para>Links to different Internet or private network links can be