2006-11-20 David Villanueva <david.villanueva@artica.es>
* en/pandora_Chapter3.xml: Changed in sintaxis in XML file without change in PDF file. Added SNMP Console section. * en/pandora_Chapter4.xml: Changed in sintaxis in XML file without change in PDF file. Added the Messages section. * en/pandora_Chapter5.xml: Changed in sintaxis in XML file without change in PDF file. * en/pandora_Chapter6.xml: Changed in sintaxis in XML file without change in PDF file. * en/pandora_Chapter7.xml: New chapter. * en/pandora_Chapter8.xml: Changed in sintaxis in XML file without change in PDF file. Updated images and new organization of index. * en/pandora_Chapter9.xml: Changed in sintaxis in XML file without change in PDF file. Updated images and writed new items in parameters. git-svn-id: https://svn.code.sf.net/p/pandora/code/trunk@264 c3f86ba8-e40f-0410-aaad-9ba5e7f4b01f
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 37 KiB |
Before Width: | Height: | Size: 58 KiB After Width: | Height: | Size: 94 KiB |
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 34 KiB |
Before Width: | Height: | Size: 17 KiB After Width: | Height: | Size: 23 KiB |
Before Width: | Height: | Size: 18 KiB After Width: | Height: | Size: 32 KiB |
Before Width: | Height: | Size: 7.2 KiB After Width: | Height: | Size: 6.5 KiB |
Before Width: | Height: | Size: 6.6 KiB After Width: | Height: | Size: 6.9 KiB |
Before Width: | Height: | Size: 13 KiB After Width: | Height: | Size: 41 KiB |
Before Width: | Height: | Size: 7.4 KiB After Width: | Height: | Size: 6.1 KiB |
Before Width: | Height: | Size: 6.5 KiB After Width: | Height: | Size: 5.5 KiB |
|
@ -14,19 +14,20 @@
|
|||
<book lang="en">
|
||||
<bookinfo>
|
||||
<title>&pandora; &pandora_version;</title>
|
||||
<graphic fileref="./images/pandora_logo.jpg" valign="bottom" align="center"/>
|
||||
<graphic fileref="./images/pandora_logo.jpg" valign="bottom"
|
||||
align="center"/>
|
||||
<copyright>
|
||||
<year>2006</year>
|
||||
<holder>
|
||||
Ártica Soluciones Tecnológicas S.L, Sancho Lerena, Esteban
|
||||
Sánchez y otros.
|
||||
<EFBFBD>tica Soluciones Tecnol<6F>icas S.L, Sancho Lerena, Esteban
|
||||
S<EFBFBD>chez, David Villanueva and others.
|
||||
</holder>
|
||||
</copyright>
|
||||
<date>11/09/2006</date>
|
||||
<date>19/11/2006</date>
|
||||
<releaseinfo>&pandora_version;</releaseinfo>
|
||||
<edition>First Edition(&pandora_version;)</edition>
|
||||
<pubdate>
|
||||
September 11th, 2006</pubdate>
|
||||
November 19th, 2006</pubdate>
|
||||
<keywordset>
|
||||
<keyword>pandora user manual</keyword>
|
||||
</keywordset>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
<chapter id="chapter4">
|
||||
<title>Incident management</title>
|
||||
<title>Incident management and messages</title>
|
||||
|
||||
<para>
|
||||
The system monitoring process needs to follow up the incidents
|
||||
|
@ -30,7 +30,8 @@
|
|||
incidents the user is interested on.
|
||||
</para>
|
||||
|
||||
<graphic fileref="images/image034.png" valign="bottom" align="center"/>
|
||||
<graphic scale='70' fileref="images/image034.png" valign="bottom"
|
||||
align="center"/>
|
||||
|
||||
<para>
|
||||
The filters that can be applied are:
|
||||
|
@ -283,4 +284,28 @@
|
|||
<graphic fileref="images/image043.png" valign="bottom" align="center"/>
|
||||
<graphic fileref="images/image044.png" valign="bottom" align="center"/>
|
||||
</sect1>
|
||||
</chapter>
|
||||
<sect1 id="sec4.5">
|
||||
<title>Messages</title>
|
||||
<para>
|
||||
In Pandora 1.2 is possible send messages to others user. Each user can
|
||||
see his/her messages in Operation, Messages.
|
||||
</para>
|
||||
|
||||
<graphic scale='80' fileref="images/messages.png" valign="bottom"
|
||||
align="center"/>
|
||||
|
||||
<para>
|
||||
To send a message to other user you must click in Operation, Messages,
|
||||
"New mesage"
|
||||
</para>
|
||||
|
||||
<graphic scale='80' fileref="images/messages1.png" valign="bottom"
|
||||
align="center"/>
|
||||
<para>
|
||||
Is possible send a mmesage a group in Operation, Messages, Messages to
|
||||
group.
|
||||
</para>
|
||||
<graphic scale='80' fileref="images/messages2.png" valign="bottom"
|
||||
align="center"/>
|
||||
</sect1>
|
||||
</chapter>
|
|
@ -27,7 +27,8 @@
|
|||
at the top of the table.
|
||||
</para>
|
||||
|
||||
<graphic fileref="images/image045.png" valign="bottom" align="center"/>
|
||||
<graphic scale='70' fileref="images/image045.png" valign="bottom"
|
||||
align="center"/>
|
||||
|
||||
<para>
|
||||
The event information list shows the data in the following
|
||||
|
@ -41,18 +42,24 @@
|
|||
been validated</para>
|
||||
<para>
|
||||
<inlinegraphic fileref="images/dot_red.png"/> The event hasn't
|
||||
been validated</para>
|
||||
been validated
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Event name:</emphasis> Name assigned to the event by
|
||||
Pandora.</para>
|
||||
Pandora.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Agent name:</emphasis> Agent where the event happend.</para>
|
||||
<emphasis>Agent name:</emphasis> Agent where the event
|
||||
happend.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Group name:</emphasis> Group of the agent where the
|
||||
event has happened.</para>
|
||||
event has happened.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>User ID: </emphasis>User that validated the
|
||||
event.</para>
|
||||
event.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Timestamp:</emphasis> Date and time when the event
|
||||
was raised or validated - if it has been validated.
|
||||
|
@ -61,11 +68,14 @@
|
|||
<emphasis>Action:</emphasis> Action that can be executed over
|
||||
the event.
|
||||
</para>
|
||||
<para><inlinegraphic fileref="images/ok.png"/>
|
||||
This icon will validate the event, disappearing the icon</para>
|
||||
<para><inlinegraphic fileref="images/cancel.png"/>
|
||||
This icon will delete the event</para>
|
||||
|
||||
<para>
|
||||
<inlinegraphic fileref="images/ok.png"/>
|
||||
This icon will validate the event, disappearing the icon
|
||||
</para>
|
||||
<para>
|
||||
<inlinegraphic fileref="images/cancel.png"/>
|
||||
This icon will delete the event
|
||||
</para>
|
||||
<para>
|
||||
The events can be also validated or deleted in groups by
|
||||
selecting the tick boxes on the last column of the event,
|
||||
|
@ -86,21 +96,24 @@
|
|||
<para>
|
||||
Total number of events divided by revised and not
|
||||
revised
|
||||
<graphic fileref="images/image046.png" valign="bottom" align="center"/>
|
||||
<graphic fileref="images/image046.png" valign="bottom"
|
||||
align="center"/>
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Total events divided by the users who validated the
|
||||
events
|
||||
<graphic fileref="images/image047.png" valign="bottom" align="center"/>
|
||||
<graphic fileref="images/image047.png" valign="bottom"
|
||||
align="center"/>
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Total events divided by the group the agent raising
|
||||
the event belongs to
|
||||
<graphic fileref="images/image048.png" valign="bottom" align="center"/>
|
||||
<graphic fileref="images/image048.png" valign="bottom"
|
||||
align="center"/>
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
|
@ -9,15 +9,15 @@
|
|||
</para>
|
||||
|
||||
<para>
|
||||
In the actual version of Pandora the system audit includes actions
|
||||
that somehow try to by pass the security system: attempts to
|
||||
delete an incident by an unauthorised user, attemps to change user
|
||||
profiles by unauthoried users, etc. Its main function is, however,
|
||||
to trace the user connections (login/logout).
|
||||
The system audit includes actions that somehow try to by pass the
|
||||
security system: attempts to delete an incident by an unauthorised
|
||||
user, attemps to change user profiles by unauthoried users, etc.
|
||||
Its main function is, however, to trace the user connections
|
||||
(login/logout).
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The audit Logs can be found in the System Audit option of the
|
||||
The audit Logs can be found in the "System Audit Log" option of the
|
||||
Administration menu, ordered chronologicly.
|
||||
</para>
|
||||
|
||||
|
@ -31,19 +31,42 @@
|
|||
at that time.
|
||||
</para>
|
||||
|
||||
<graphic fileref="images/image049.png" valign="bottom" align="center"/>
|
||||
|
||||
<para>The following fields display the Audit Logs information:</para>
|
||||
|
||||
<para><emphasis>User:</emphasis> User that triggerd the event (SYSTEM isspecial user of the system).</para>
|
||||
<para><emphasis>Action:</emphasis> Action generated by the entry in the log.</para>
|
||||
<para><emphasis>Date:</emphasis> Date of the entry in the log.</para>
|
||||
<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>
|
||||
<graphic scale='70' fileref="images/image049.png" valign="bottom"
|
||||
align="center"/>
|
||||
|
||||
<para>
|
||||
The following fields display the Audit Logs information:
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>User:</emphasis> User that triggerd the event (SYSTEM
|
||||
isspecial user of the system).
|
||||
</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Action:</emphasis> Action generated by the entry in
|
||||
the log.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Date:</emphasis> Date of the entry in the log.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Source IP:</emphasis> IP of the machine or the agent
|
||||
that provoked the entry.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Comment:</emphasis> Comment describing the entry
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<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
|
||||
|
@ -52,12 +75,11 @@
|
|||
each one: the more active the user is the higher the number of
|
||||
entries.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The graph will also show entries of invalid users, i.e., those
|
||||
entries generated by failed attemps to log in.
|
||||
</para>
|
||||
|
||||
<graphic fileref="images/image050.png" valign="bottom" align="center"/>
|
||||
<graphic fileref="images/image050.png" valign="bottom"
|
||||
align="center"/>
|
||||
</sect1>
|
||||
</chapter>
|
|
@ -2,11 +2,94 @@
|
|||
<chapter id="chapter7">
|
||||
<title>Pandora Servers</title>
|
||||
<para>
|
||||
From "Manage Servers" section, in the Administration menu you can see a
|
||||
list of configured Pandora Servers and also can manage them.
|
||||
In Pandora 1.2 there are different type of servers, Network Server,
|
||||
Data Server or SNMP Server.
|
||||
</para>
|
||||
<para>
|
||||
From "Pandora Servers" in the Operation menu you can see a list
|
||||
of the Pandora Servers.
|
||||
Is posible manage the Pandora Servers in "Manage Servers" option of the
|
||||
Administration menu.
|
||||
</para>
|
||||
<graphic scale='60' fileref="images/Servers.png" valign="bottom"
|
||||
align="center"/>
|
||||
<para>
|
||||
The following fields are displayed in the Managed Servers page:
|
||||
</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Name:</emphasis> Name of the server.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Status:</emphasis> Status of the server. Green ok and
|
||||
Red fail.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>IP address:</emphasis> IP of the Server.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Description:</emphasis> Server´s description.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Network:</emphasis> Mark for Network Server..
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Data:</emphasis> Mark for Data Server.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>SNMP:</emphasis> Mark for SNMP Server.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Master:</emphasis> Mark when the server is Master and not
|
||||
mark when the master is backup.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Check:</emphasis>
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Started at:</emphasis> Date when the Server started.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Updated at:</emphasis> The date of the last update.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Action:</emphasis> Icons to modify a server´s properties or
|
||||
to delete a server.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<para>
|
||||
Is posible delete a with the icon <inlinegraphic
|
||||
fileref="images/cancel.png"/>
|
||||
</para>
|
||||
<para>
|
||||
Is posible change the server´s propirties with the icon <inlinegraphic
|
||||
fileref="images/config.png"/>
|
||||
</para>
|
||||
<para>
|
||||
In a Server is posiible modify: Name, IP Address and Description.
|
||||
</para>
|
||||
<graphic scale='70' fileref="images/Servers1.png" valign="bottom"
|
||||
align="center"/>
|
||||
</chapter>
|
|
@ -20,57 +20,66 @@
|
|||
|
||||
<para>
|
||||
As the database size will increase linearly, the data will be
|
||||
compacted to reduce the amount of stored data without loosing important
|
||||
information, specially the different graphs that are generated with
|
||||
the processed data.
|
||||
compacted to reduce the amount of stored data without loosing
|
||||
important information, specially the different graphs that are
|
||||
generated with the processed data.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Going to "DB Maintenance" from the Administration menu we will
|
||||
find the Database configuration defined in the "Pandora Setup" option
|
||||
of the Administration menu to compact and delete data.
|
||||
</para>
|
||||
|
||||
<graphic fileref="images/image054.png" valign="bottom" align="center"/>
|
||||
<graphic scale='70' fileref="images/image054.png" valign="bottom"
|
||||
align="center"/>
|
||||
<sect1 id="sec8.1">
|
||||
<title>DB Information</title>
|
||||
|
||||
<para>
|
||||
The DB statistics are generated by Agent, on the
|
||||
"DB Maintenance">"DB Information" in the Administration menu,
|
||||
and are represented in two kinds of graphs:
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Number of modules configured for each of the agents.</para>
|
||||
<para>
|
||||
Number of modules configured for each of the agents.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Number of packages sent by each agent.
|
||||
A package is the group of data linked to the module
|
||||
the agent sends in each interval of time.</para>
|
||||
<para>
|
||||
Number of packages sent by each agent. A package is the group
|
||||
of data linked to the module the agent sends in each interval of
|
||||
time.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<graphic fileref="images/image055.png" valign="bottom" align="center"/>
|
||||
<graphic fileref="images/image056.png" valign="bottom" align="center"/>
|
||||
<graphic fileref="images/image057.png" valign="bottom" align="center"/>
|
||||
|
||||
<para>These graphs can be also viewed from
|
||||
"View Agents">"Statistics" in the Operation menu.</para>
|
||||
<graphic scale='70' fileref="images/image055.png" valign="bottom"
|
||||
align="center"/>
|
||||
<graphic scale='70' fileref="images/image056.png" valign="bottom"
|
||||
align="center"/>
|
||||
<graphic scale='70' fileref="images/image057.png" valign="bottom"
|
||||
align="center"/>
|
||||
<para>
|
||||
These graphs can be also viewed from
|
||||
"View Agents">"Statistics" in the Operation menu.
|
||||
</para>
|
||||
<para>
|
||||
Is posible to view the Data Base information in mode text pich in the
|
||||
link "Press here to get DB Info as text"
|
||||
</para>
|
||||
<graphic scale='70' fileref="images/DBText.png" valign="bottom"
|
||||
align="center"/>
|
||||
</sect1>
|
||||
<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="sec8.3">
|
||||
<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>
|
||||
<sect2 id="sec8.2.1">
|
||||
<title>Agent's data purge</title>
|
||||
<sect2 id="sec8.3.1">
|
||||
<sect3 id="sec8.2.1.1">
|
||||
<title>Debuging selected data from a module</title>
|
||||
|
||||
<para>
|
||||
The option of purging selected data from a module is used
|
||||
to eliminate those out of range entries, whatever the reason
|
||||
|
@ -79,19 +88,18 @@
|
|||
the graphical representation more acuarate and shows the data
|
||||
without peaks or unreal scales.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
From "DB Maintenance">"Database Debug" in the
|
||||
Administration menu any of the out of range data received
|
||||
from a agent's module can be deleted.
|
||||
</para>
|
||||
|
||||
<graphic fileref="images/image058.png" valign="bottom" align="center"/>
|
||||
|
||||
<para>The purge settings are: agent, module, minimum and maximum
|
||||
data range. Any parameter out of this minimum/maximum range
|
||||
will be deleted.</para>
|
||||
|
||||
<graphic scale='70' fileref="images/image058.png" valign="bottom"
|
||||
align="center"/>
|
||||
<para>
|
||||
The purge settings are: agent, module, minimum and maximum data
|
||||
range. Any parameter out of this minimum/maximum range will be
|
||||
deleted.
|
||||
</para>
|
||||
<para>
|
||||
For example, in a module registering the number of processes,
|
||||
if we are only interested in values between 0 and 100, any values
|
||||
|
@ -100,127 +108,162 @@
|
|||
all those values below and above - such as -1, 100 or 100000 -
|
||||
will be permanently deleted from the database.
|
||||
</para>
|
||||
</sect2>
|
||||
<sect2 id="sec8.3.2">
|
||||
</sect3>
|
||||
<sect3 id="sec8.2.1.2">
|
||||
<title>Purging all the agent's data</title>
|
||||
|
||||
<para>
|
||||
All the out of range data received by an agent can be deleted
|
||||
from the "DB Maintainance">"Database Purge" option in the
|
||||
Administration menu.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The data is deleted by the following parameters from
|
||||
the "Delete data" screen:
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Purge all data</para>
|
||||
<para>
|
||||
Purge all data
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge data over 90 days</para>
|
||||
<para>
|
||||
Purge data over 90 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge data over 30 days</para>
|
||||
<para>
|
||||
Purge data over 30 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge data over 14 days</para>
|
||||
<para>
|
||||
Purge data over 14 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge data over 7 days</para>
|
||||
<para>
|
||||
Purge data over 7 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge data over 3 days</para>
|
||||
<para>
|
||||
Purge data over 3 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge data over 1 day</para>
|
||||
<para>
|
||||
Purge data over 1 day
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<graphic fileref="images/image059.png" valign="bottom" align="center"/>
|
||||
</sect2>
|
||||
</sect1>
|
||||
<sect1 id="sec8.4">
|
||||
<graphic scale='70' fileref="images/image059.png" valign="bottom"
|
||||
align="center"/>
|
||||
</sect3>
|
||||
</sect2>
|
||||
<sect2 id="sec8.2.2">
|
||||
<title>Purging system data</title>
|
||||
<sect2 id="sec8.4.1">
|
||||
<sect3 id="sec8.2.2.1">
|
||||
<title>Audit data purge</title>
|
||||
|
||||
<para>
|
||||
All the audit data generated by the system can be deleted from
|
||||
"DB Maintenance">"Database Audit", in the Administration menu
|
||||
"DB Maintenance">"Database Audit", in the Administration
|
||||
menu
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The data to be deleted is selected by setting the following
|
||||
parameters in the "Delete Data" screen
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Purge audit data over 90 days</para>
|
||||
<para>
|
||||
Purge audit data over 90 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge audit data over 30 days</para>
|
||||
<para>
|
||||
Purge audit data over 30 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge audit data over 14 days</para>
|
||||
<para>
|
||||
Purge audit data over 14 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge audit data over 7 days</para>
|
||||
<para>
|
||||
Purge audit data over 7 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge audit data over 3 days</para>
|
||||
<para>
|
||||
Purge audit data over 3 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge audit data over 1 day</para>
|
||||
<para>
|
||||
Purge audit data over 1 day
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge all audit data</para>
|
||||
<para>
|
||||
Purge all audit data
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<graphic fileref="images/image060.png" valign="bottom" align="center"/>
|
||||
</sect2>
|
||||
<sect2 id="sec8.4.2">
|
||||
<graphic scale='70' fileref="images/image060.png" valign="bottom"
|
||||
align="center"/>
|
||||
</sect3>
|
||||
<sect3 id="sec8.2.2.2">
|
||||
<title>Event data purge</title>
|
||||
|
||||
<para>
|
||||
All the event data generated by the system can be deleted from
|
||||
"DB Maintenance">"Database Event", in the Administration menu
|
||||
</para>
|
||||
|
||||
<para>
|
||||
The data to be deleted is selected by setting the following
|
||||
parameters in the "Delete Data" screen
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Purge event data over 90 days</para>
|
||||
<para>
|
||||
Purge event data over 90 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge event data over 30 days</para>
|
||||
<para>
|
||||
Purge event data over 30 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge event data over 14 days</para>
|
||||
<para>
|
||||
Purge event data over 14 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge event data over 7 days</para>
|
||||
<para>
|
||||
Purge event data over 7 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge event data over 3 days</para>
|
||||
<para>
|
||||
Purge event data over 3 days
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge event data over 1 day</para>
|
||||
<para>
|
||||
Purge event data over 1 day
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Purge all event data</para>
|
||||
<para>
|
||||
Purge all event data
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<graphic fileref="images/image061.png" valign="bottom" align="center"/>
|
||||
</sect2>
|
||||
<graphic scale='70' fileref="images/image061.png" valign="bottom"
|
||||
align="center"/>
|
||||
</sect3>
|
||||
</sect2>
|
||||
</sect1>
|
||||
</chapter>
|
|
@ -2,62 +2,88 @@
|
|||
|
||||
<chapter id="chapter9">
|
||||
<title>Pandora Configuration</title>
|
||||
|
||||
<para>All the configurable parameters in Pandora can be set in the
|
||||
"Pandora Setup" section, in the Administration menu.</para>
|
||||
|
||||
<graphic fileref="images/image051.png" valign="bottom" align="center"/>
|
||||
|
||||
<para>These parameters are:</para>
|
||||
|
||||
<para><emphasis>Language:</emphasis> In following versions or revisions
|
||||
of the actual Pandora version will support more languages.
|
||||
At the moment version 1.2 supports English, Spanish, Bable, Italian,
|
||||
French, Catalan and Portuguese of Brazil.
|
||||
<para>
|
||||
All the configurable parameters in Pandora can be set in the
|
||||
"Pandora Setup" section, in the Administration menu.
|
||||
</para>
|
||||
<para><emphasis>Page block size:</emphasis> Maximum size of the lists
|
||||
in the event, incident and audit log sections.
|
||||
<graphic scale='70' fileref="images/image051.png" valign="bottom"
|
||||
align="center"/>
|
||||
<para>
|
||||
These parameters are:
|
||||
</para>
|
||||
<para><emphasis>Max. days before compact data:</emphasis> This parameter
|
||||
controls data compacting. From the number of days in this parameter the
|
||||
data starts getting compacted. For large amounts of data it is recommended
|
||||
to set this parameter to a number between 14 and 28; for systems with
|
||||
less data load or very powerful systems, a number
|
||||
between 30 and 50 will be enough.
|
||||
<para>
|
||||
<emphasis>Language:</emphasis> In following versions or
|
||||
revisions of the actual Pandora version will support more
|
||||
languages. At the moment version 1.2 supports English, Spanish,
|
||||
Spanish Latin-AMerica Bable, Italian, French, Catalan and
|
||||
Portuguese of Brazil.
|
||||
</para>
|
||||
<para><emphasis>Max. days before purge:</emphasis>
|
||||
This parameter controls how long the data is kept
|
||||
before it is permanently deleted. The recommended value is 60.
|
||||
For systems with little resources or large work load the recommended value
|
||||
is between 40 and 50.
|
||||
<para>
|
||||
<emphasis>Block size for pagination:</emphasis> Maximum size of
|
||||
the lists in the event, incident and audit log sections.
|
||||
</para>
|
||||
<para><emphasis>Graphic resolution (1 low, 5 high):</emphasis>
|
||||
This value represents the precision of the
|
||||
interpolation logarithm to generate the graphics.
|
||||
<para>
|
||||
<emphasis>Max. days before compact data:</emphasis> This
|
||||
parameter controls data compacting. From the number of days in
|
||||
this parameter the data starts getting compacted. For large
|
||||
amounts of data it is recommended to set this parameter to a
|
||||
number between 14 and 28; for systems with less data load or very
|
||||
powerful systems, a number between 30 and 50 will be enough.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Max. days before purge:</emphasis> This parameter
|
||||
controls how long the data is kept before it is permanently
|
||||
deleted. The recommended value is 60. For systems with little
|
||||
resources or large work load the recommended value is between 40
|
||||
and 50.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Graphic resolution (1 low, 5 high):</emphasis> This
|
||||
value represents the precision of the interpolation logarithm to
|
||||
generate the graphics.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Compact interpolation (Hours: 1 fine, 10 medium, 20
|
||||
bad):</emphasis> This is the grade of compression used to compact
|
||||
the Data Base, being 1 the lowest compression rate and 20 the
|
||||
highest. A value above 12 means a considerable data loss. It's
|
||||
not recommended to use value above 6 if the data needs to be
|
||||
represented graphically in large time intervals.
|
||||
bad):</emphasis> This is the grade of compression used to
|
||||
compact the Data Base, being 1 the lowest compression rate and
|
||||
20 the highest. A value above 12 means a considerable data
|
||||
loss. It's not recommended to use value above 6 if the data
|
||||
needs to be represented graphically in large time intervals.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Graph order:</emphasis> This value represents the order
|
||||
to create the graphs. The posibility are Righ to left, or left to
|
||||
right.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Truetype fonts:</emphasis> This value represents the
|
||||
capacity to active the truetypefonts.The posibility are Active or
|
||||
Disable.
|
||||
</para>
|
||||
<para>
|
||||
<emphasis>Background image:</emphasis> This value represents the
|
||||
image to background, is possibel change it bettwen severaql
|
||||
different images.
|
||||
</para>
|
||||
<sect1 id="sec9.1">
|
||||
<title>Links</title>
|
||||
|
||||
<para>Links to different Internet or private network links can be
|
||||
configured in Pandora. These could be search engines, applications or
|
||||
company Intranets.</para>
|
||||
|
||||
<para>The links configured in Pandora can be edited through the
|
||||
"Pandora Setup">"Links" option in the Administration menu.</para>
|
||||
|
||||
<graphic fileref="images/image052.png" valign="bottom" align="center"/>
|
||||
|
||||
<para>A new link is created by clicking on "Create".
|
||||
The link can be then edited:</para>
|
||||
|
||||
<graphic fileref="images/image053.png" valign="bottom" align="center"/>
|
||||
<para>
|
||||
Links to different Internet or private network links can be
|
||||
configured in Pandora. These could be search engines, applications
|
||||
or company Intranets.
|
||||
</para>
|
||||
<para>
|
||||
The links configured in Pandora can be edited through the
|
||||
"Pandora Setup">"Links" option in the Administration
|
||||
menu.
|
||||
</para>
|
||||
<graphic scale='70' fileref="images/image052.png" valign="bottom"
|
||||
align="center"/>
|
||||
<para>
|
||||
A new link is created by clicking on "Add".The link can be then
|
||||
edited:
|
||||
</para>
|
||||
<graphic fileref="images/image053.png" valign="bottom"
|
||||
align="center"/>
|
||||
</sect1>
|
||||
</chapter>
|
|
@ -19,18 +19,20 @@
|
|||
<book lang="en">
|
||||
<bookinfo>
|
||||
<title>&pandora; &pandora_version;</title>
|
||||
<graphic fileref="./images/pandora_logo.jpg" valign="bottom" align="center"/>
|
||||
<graphic fileref="./images/pandora_logo.jpg" valign="bottom"
|
||||
align="center"/>
|
||||
<copyright>
|
||||
<year>2006</year>
|
||||
<holder>
|
||||
Artica Soluciones Tecnologicas S.L, Sancho Lerena, Esteban Sanchez y otros.
|
||||
Artica Soluciones Tecnologicas S.L, Sancho Lerena, Esteban
|
||||
Sanchez, David Villanueva and others.
|
||||
</holder>
|
||||
</copyright>
|
||||
<date>11/09/2006</date>
|
||||
<date>19/11/2006</date>
|
||||
<releaseinfo>&pandora_version;</releaseinfo>
|
||||
<edition>First Edition(&pandora_version;)</edition>
|
||||
<pubdate>
|
||||
September 11th, 2006</pubdate>
|
||||
November 19th, 2006</pubdate>
|
||||
<keywordset>
|
||||
<keyword>pandora user manual</keyword>
|
||||
</keywordset>
|
||||
|
|