2006-09-12 Raul Mateos <raulofpandora@gmail.com>
* Updated pandora_chapter 3 to 9.
* Updated pandora.xml
git-svn-id: https://svn.code.sf.net/p/pandora/code/trunk@162 c3f86ba8-e40f-0410-aaad-9ba5e7f4b01f
This commit is contained in:
raulmateos
parent
128eeb2c02
commit
1c5972c264
|
|
@ -1,7 +1,11 @@
|
|||
2006-09-12 Raul Mateos <raulofpandora@gmail.com>
|
||||
|
||||
* Updated pandora_chapter 3 to 9.
|
||||
|
||||
* Updated pandora.xml
|
||||
|
||||
2006-09-11 Sancho Lerena <slerena@artica.es>
|
||||
|
||||
* Creation of ChangeLog
|
||||
|
||||
* Updated pandora_chapter 1 2 3 and part of 4.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -1,10 +1,8 @@
|
|||
<?xml version="1.0" encoding="ISO-8859-15" standalone="no" ?>
|
||||
<?xml version="1.0" encoding="utf-8" standalone="no" ?>
|
||||
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V4.4//EN"
|
||||
"/usr/share/xml/docbook/schema/dtd/4.4/docbookx.dtd" [
|
||||
"docbookx.dtd" [
|
||||
<!ENTITY pandora_version "v1.2">
|
||||
<!ENTITY pandora "<emphasis>Pandora</emphasis>">
|
||||
<!ENTITY include_fdl SYSTEM "fdl.xml">
|
||||
<!ENTITY include_gpl SYSTEM "gpl.xml">
|
||||
<!ENTITY include_pandora_chapter1 SYSTEM "pandora_chapter1.xml">
|
||||
<!ENTITY include_pandora_chapter2 SYSTEM "pandora_chapter2.xml">
|
||||
<!ENTITY include_pandora_chapter3 SYSTEM "pandora_chapter3.xml">
|
||||
|
|
@ -23,7 +21,7 @@
|
|||
<copyright>
|
||||
<year>2006</year>
|
||||
<holder>
|
||||
Ártica Soluciones Tecnológicas S.L, Sancho Lerena, Esteban Sánchez y otros.
|
||||
Ártica Soluciones Tecnológicas S.L, Sancho Lerena, Esteban Sánchez y otros.
|
||||
</holder>
|
||||
</copyright>
|
||||
<date>11/09/2006</date>
|
||||
|
|
@ -67,7 +65,5 @@
|
|||
&include_pandora_chapter7;
|
||||
&include_pandora_chapter8;
|
||||
&include_pandora_chapter9;
|
||||
&include_fdl;
|
||||
&include_gpl;
|
||||
|
||||
</book>
|
||||
|
|
@ -419,7 +419,7 @@
|
|||
button shows the modules for that agent in the Modules list box.
|
||||
</para>
|
||||
|
||||
<para><emphasis><i>The copy process</i></emphasis> is performed to copy
|
||||
<para><emphasis>The copy process</emphasis> is performed to copy
|
||||
the module and/or alert configuration from the selected source
|
||||
agents to the selected destination agents. Several agents can be
|
||||
selected, pressing CTRL and the mouse right button simultaneously.
|
||||
|
|
@ -427,7 +427,7 @@
|
|||
if the configuration to copy is from modules and/or from alerts.
|
||||
</para>
|
||||
|
||||
<para><emphasis><i>The delete process</i></emphasis> is performed to delete the
|
||||
<para><emphasis>The delete process</emphasis> is performed to delete the
|
||||
configuration of the destination agents, in the multiple selection
|
||||
list box. Several agents can be selected at a time, and the tick
|
||||
boxes at the top of the form indicate whether it is the modules
|
||||
|
|
@ -561,7 +561,7 @@
|
|||
<para><emphasis>Module name:</emphasis> Name given to the module
|
||||
in the agent's config file.</para>
|
||||
<para><emphasis>Module type:</emphasis> Type of module as described
|
||||
in <a href="#321">section 3.2.1</a>.</para>
|
||||
in <link linkend="#321">section 3.2.1</link>.</para>
|
||||
<para><emphasis>Description:</emphasis> Description given to the module
|
||||
in the agent's config file.</para>
|
||||
<para><emphasis>Data:</emphasis> Last data sent by the agent.</para>
|
||||
|
|
|
|||
|
|
@ -1,64 +1,78 @@
|
|||
<?xml version="1.0" encoding="ISO-8859-15"?>
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
<chapter>
|
||||
<title>Incident management</title>
|
||||
|
||||
<para>The system monitoring process needs to follow up the incidents
|
||||
<para>
|
||||
The system monitoring process needs to follow up the incidents
|
||||
arising in the system besides receiving and processing the data to be
|
||||
monitored in each time interval</para>
|
||||
monitored in each time interval
|
||||
</para>
|
||||
|
||||
<para>Pandora uses a tool called Incident Manager for this task, where
|
||||
<para>
|
||||
Pandora uses a tool called Incident Manager for this task, where
|
||||
each user can open an incident, where a description of what happened
|
||||
in the network is shown. This can be completed with comments and files
|
||||
when necessary.</para>
|
||||
when necessary.
|
||||
</para>
|
||||
|
||||
<para>This system is designed for group work. Different roles and
|
||||
<para>
|
||||
This system is designed for group work. Different roles and
|
||||
workflow systems permit to move incidents from one group to another.
|
||||
The system allows different groups and different users to work on
|
||||
the same incident, sharing information and files.</para>
|
||||
the same incident, sharing information and files.
|
||||
</para>
|
||||
|
||||
<para>Clicking on "Manage Incidents", in the Operation menu, a list
|
||||
<para>
|
||||
Clicking on "Manage Incidents", in the Operation menu, a list
|
||||
showing all the incidents is displayed, ordered by the date-time they
|
||||
were last updated. Filters can be applied to display only those
|
||||
incidents the user is interested on.</para>
|
||||
incidents the user is interested on.
|
||||
</para>
|
||||
|
||||
<graphic fileref="images/image034.png" valign="bottom" align="center"/>
|
||||
|
||||
<para>The filters that can be applied are:</para>
|
||||
<para>
|
||||
The filters that can be applied are:
|
||||
</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><b>Incident status filter</b>. The user can display:
|
||||
<para><emphasis>Incident status filter</emphasis>.
|
||||
The user can display:</para>
|
||||
<para>- All incidents</para>
|
||||
<para>- Active incidents</para>
|
||||
<para>- Closed incidents</para>
|
||||
<para>- Rejected incidents</para>
|
||||
<para>- Expired incidents</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Property filter</emphasis>.
|
||||
The incidents are shown by:
|
||||
</para>
|
||||
<para>- All priorities</para>
|
||||
<para>- Informative priority</para>
|
||||
<para>- Low priority</para>
|
||||
<para>- Medium priority</para>
|
||||
<para>- High priority</para>
|
||||
<para>- Very high priority</para>
|
||||
<para>- Maintenance</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
<b>Property filter</b>. The incidents are shown by:
|
||||
<para>- All priorities</para>
|
||||
<para>- Informative priority</para>
|
||||
<para>- Low priority</para>
|
||||
<para>- Medium priority</para>
|
||||
<para>- High priority</para>
|
||||
<para>- Very high priority</para>
|
||||
<para>- Maintenance</para>
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Group filter</b>. It can be selected to display just the
|
||||
incidents of a given Pandora group.</para>
|
||||
<para><emphasis>Group filter</emphasis>.
|
||||
It can be selected to display just the
|
||||
incidents of a given Pandora group.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>The incident list is displayed showing information in the following
|
||||
columns:</para>
|
||||
<para>
|
||||
The incident list is displayed showing information in the following columns:
|
||||
</para>
|
||||
|
||||
<para><b>ID:</b> ID of the incident.</para>
|
||||
<para><b>Status:</b> The incident status is represented by the following
|
||||
<para><emphasis>ID:</emphasis> ID of the incident.</para>
|
||||
<para><emphasis>Status:</emphasis> The incident status is represented by the following
|
||||
icons:</para>
|
||||
|
||||
<para><graphic fileref="../../images/dot_red.gif"/> Active incident</para>
|
||||
|
|
@ -68,8 +82,8 @@
|
|||
<para><graphic fileref="../../images/dot_green.gif"/> Closed incident</para>
|
||||
<para><graphic fileref="../../images/dot_white.gif"/> Expired incident</para>
|
||||
|
||||
<para><b>Incident name:</b> Name given to the incident</para>
|
||||
<para><b>Priority:</b> The incident assigned priority is represented
|
||||
<para><emphasis>Incident name:</emphasis> Name given to the incident</para>
|
||||
<para><emphasis>Priority:</emphasis> The incident assigned priority is represented
|
||||
by the following icons:</para>
|
||||
|
||||
<para><graphic fileref="../../images/dot_red.gif"/>
|
||||
|
|
@ -96,15 +110,15 @@
|
|||
<graphic fileref="../../images/dot_green.gif"/>
|
||||
<graphic fileref="../../images/dot_green.gif"/> Maintenance priority</para>
|
||||
|
||||
<para><b>Group:</b> The name of the group the incident has been assigned
|
||||
<para><emphasis>Group:</emphasis> The name of the group the incident has been assigned
|
||||
to. One incident can only belong to a single group.</para>
|
||||
<para><b>Updated at:</b> This is the date/time the incident was updated
|
||||
<para><emphasis>Updated at:</emphasis> This is the date/time the incident was updated
|
||||
for the last time.</para>
|
||||
<para><b>Source:</b> The source of the incident. The source is selected
|
||||
<para><emphasis>Source:</emphasis> The source of the incident. The source is selected
|
||||
from a list stored
|
||||
in the data base. This list can only be modified by the database base
|
||||
administrator.</para>
|
||||
<para><b>Owner:</b> User to whom the incident has been assigned to.
|
||||
<para><emphasis>Owner:</emphasis> User to whom the incident has been assigned to.
|
||||
It doesn't coinced
|
||||
with the creator of the incident, as the incident may have been moved
|
||||
from one user to another. The incident can be assigned to another user
|
||||
|
|
@ -141,22 +155,22 @@
|
|||
<para>From this form the following values can be updated:</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><b>Incident name</b></para>
|
||||
<para><emphasis>Incident name</emphasis></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Incident owner</b></para>
|
||||
<para><emphasis>Incident owner</emphasis></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Incident status</b></para>
|
||||
<para><emphasis>Incident status</emphasis></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Incident source</b></para>
|
||||
<para><emphasis>Incident source</emphasis></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Group the indicent will belong to</b></para>
|
||||
<para><emphasis>Group the indicent will belong to</emphasis></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Indicent priority</b></para>
|
||||
<para><emphasis>Indicent priority</emphasis></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
<para>The indicent is updated by clicking on the "Update incident" button.</para>
|
||||
|
|
@ -193,7 +207,7 @@
|
|||
<title>Searching for an incident</title>
|
||||
|
||||
<para>A specific incident can be found amongst the
|
||||
incidents created in Pandora by either using a filter – as explained in the
|
||||
incidents created in Pandora by either using a filter _ as explained in the
|
||||
first section of this chapter - or by making a query using the "Manage Incidents">"Searh Incident" tool, in the Operation menu.</para>
|
||||
|
||||
<graphic fileref="images/image041.png" valign="bottom" align="center"/>
|
||||
|
|
@ -212,19 +226,19 @@
|
|||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><b>Incident status</b></para>
|
||||
<para><emphasis>Incident status</emphasis></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Incident priority</b></para>
|
||||
<para><emphasis>Incident priority</emphasis></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Users with the incident opened</b></para>
|
||||
<para><emphasis>Users with the incident opened</emphasis></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Incidents by group</b></para>
|
||||
<para><emphasis>Incidents by group</emphasis></para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><b>Incident source</b></para>
|
||||
<para><emphasis>Incident source</emphasis></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<?xml version="1.0" encoding="ISO-8859-15"?>
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
<chapter>
|
||||
<title>Events</title>
|
||||
|
|
@ -21,18 +21,18 @@
|
|||
|
||||
<para>The event information list shows the data in the following columns:</para>
|
||||
|
||||
<para><b>Status:</b> The event status is represented by the icon bellow:</para>
|
||||
<graphic fileref="../../images/dot_green.gif"/> The event has been validated
|
||||
<graphic fileref="../../images/dot_red.gif"/> The event hasn't been validated
|
||||
<para><b>Event name:</b> Name assigned to the event by Pandora.</para>
|
||||
<para><b>Agent name:</b> Agent where the event happend.</para>
|
||||
<para><b>Group name:</b> Group of the agent where the event has happened.</para>
|
||||
<para><b>User ID: </b>User that validated the event.</para>
|
||||
<para><b>Timestamp:</b> Date and time when the event was raised or validated
|
||||
<para><emphasis>Status:</emphasis> The event status is represented by the icon bellow:</para>
|
||||
<para><graphic fileref="../../images/dot_green.gif"/> The event has been validated</para>
|
||||
<para><graphic 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>
|
||||
<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>
|
||||
<para><emphasis>User ID: </emphasis>User that validated the event.</para>
|
||||
<para><emphasis>Timestamp:</emphasis> Date and time when the event was raised or validated
|
||||
- if it has been validated.</para>
|
||||
<para><b>Action:</b> Action that can be executed over the event.</para>
|
||||
<graphic fileref="../../images/ok.gif"/> This icon will validate the event, disappearing the icon
|
||||
<graphic fileref="../../images/cancel.gif"/> This icon will delete the event
|
||||
<para><emphasis>Action:</emphasis> Action that can be executed over the event.</para>
|
||||
<para><graphic fileref="../../images/ok.gif"/> This icon will validate the event, disappearing the icon</para>
|
||||
<para><graphic fileref="../../images/cancel.gif"/> 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, and pressing "Validate" or
|
||||
|
|
|
|||
|
|
@ -21,11 +21,11 @@
|
|||
|
||||
<para>The following fields display the Audit Logs information:</para>
|
||||
|
||||
<para><b>User:</b> User that triggerd the event (SYSTEM isspecial user of the system).</para>
|
||||
<para><b>Action:</b> Action generated by the entry in the log.</para>
|
||||
<para><b>Date:</b> Date of the entry in the log.</para>
|
||||
<para><b>Source IP:</b> IP of the machine or the agent that provoked the entry.</para>
|
||||
<para><b>Comment:</b> Comment describing the entry</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>
|
||||
|
||||
<sect1>
|
||||
<title>Statistics</title>
|
||||
|
|
|
|||
|
|
@ -1,10 +1,16 @@
|
|||
<?xml version="1.0" encoding="ISO-8859-15"?>
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
<chapter>
|
||||
<title>Pandora Servers</title>
|
||||
<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.</para>
|
||||
<para>
|
||||
From "Manage Servers" section, in the Administration menu you can see a
|
||||
list of configured Pandora Servers and also can manage them.
|
||||
</para>
|
||||
|
||||
<para>From "Pandora Servers" in the Operation menu you can see a list of the Pandora Servers.</para>
|
||||
<para>
|
||||
From "Pandora Servers" in the Operation menu you can see a list
|
||||
of the Pandora Servers.
|
||||
</para>
|
||||
|
||||
</chapter>
|
||||
|
|
@ -1,4 +1,4 @@
|
|||
<?xml version="1.0" encoding="ISO-8859-15"?>
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
<chapter>
|
||||
<title>Database Maintenance</title>
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<?xml version="1.0" encoding="ISO-8859-15"?>
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
|
||||
<chapter>
|
||||
<title>Pandora Configuration</title>
|
||||
|
|
@ -9,19 +9,19 @@
|
|||
|
||||
<para>These parameters are:</para>
|
||||
|
||||
<para><b>Language:</b> 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>
|
||||
<para><b>Page block size:</b> Maximum size of the lists in the event, incident and audit log sections.</para>
|
||||
<para><b>Max. days before compact data:</b> This parameter controls data compacting. From the
|
||||
<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>
|
||||
<para><emphasis>Page block size:</emphasis> Maximum size of the lists in the event, incident and audit log sections.</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>
|
||||
<para><b>Max. days before purge:</b> This parameter controls how long the data is kept
|
||||
<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><b>Graphic resolution (1 low, 5 high):</b> This value represents the precision of the
|
||||
<para><emphasis>Graphic resolution (1 low, 5 high):</emphasis> This value represents the precision of the
|
||||
interpolation logarithm to generate the graphics.</para>
|
||||
<para><b>Compact interpolation (Hours: 1 fine, 10 medium, 20 bad):</b> 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
|
||||
<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.</para>
|
||||
<sect1>
|
||||
<title>Links</title>
|
||||
|
|
|
|||
Loading…
Reference in New Issue