From c84e7816fce481a3662ef37eb17f5e72b5e8e261 Mon Sep 17 00:00:00 2001 From: raulmateos Date: Tue, 12 Sep 2006 15:17:32 +0000 Subject: [PATCH] 2006-09-12 Raul Mateos * 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 --- pandora_doc/ChangeLog | 8 ++- pandora_doc/pandora.xml | 10 +-- pandora_doc/pandora_chapter3.xml | 6 +- pandora_doc/pandora_chapter4.xml | 108 +++++++++++++++++-------------- pandora_doc/pandora_chapter5.xml | 24 +++---- pandora_doc/pandora_chapter6.xml | 10 +-- pandora_doc/pandora_chapter7.xml | 14 ++-- pandora_doc/pandora_chapter8.xml | 2 +- pandora_doc/pandora_chapter9.xml | 14 ++-- 9 files changed, 108 insertions(+), 88 deletions(-) diff --git a/pandora_doc/ChangeLog b/pandora_doc/ChangeLog index e2640d558c..a5d671c63c 100644 --- a/pandora_doc/ChangeLog +++ b/pandora_doc/ChangeLog @@ -1,7 +1,11 @@ +2006-09-12 Raul Mateos + + * Updated pandora_chapter 3 to 9. + + * Updated pandora.xml + 2006-09-11 Sancho Lerena * Creation of ChangeLog * Updated pandora_chapter 1 2 3 and part of 4. - - diff --git a/pandora_doc/pandora.xml b/pandora_doc/pandora.xml index 94c1452b43..aedeae7981 100644 --- a/pandora_doc/pandora.xml +++ b/pandora_doc/pandora.xml @@ -1,10 +1,8 @@ - + Pandora"> - - @@ -23,7 +21,7 @@ 2006 - Á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. 11/09/2006 @@ -67,7 +65,5 @@ &include_pandora_chapter7; &include_pandora_chapter8; &include_pandora_chapter9; - &include_fdl; - &include_gpl; \ No newline at end of file diff --git a/pandora_doc/pandora_chapter3.xml b/pandora_doc/pandora_chapter3.xml index fac53498b8..7dd9f9a6e8 100644 --- a/pandora_doc/pandora_chapter3.xml +++ b/pandora_doc/pandora_chapter3.xml @@ -419,7 +419,7 @@ button shows the modules for that agent in the Modules list box. - The copy process is performed to copy + The copy process 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. - The delete process is performed to delete the + The delete process 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 @@ Module name: Name given to the module in the agent's config file. Module type: Type of module as described - in section 3.2.1. + in section 3.2.1. Description: Description given to the module in the agent's config file. Data: Last data sent by the agent. diff --git a/pandora_doc/pandora_chapter4.xml b/pandora_doc/pandora_chapter4.xml index 40431fac6f..b1765251f7 100644 --- a/pandora_doc/pandora_chapter4.xml +++ b/pandora_doc/pandora_chapter4.xml @@ -1,64 +1,78 @@ - + Incident management - The system monitoring process needs to follow up the incidents + + 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 + monitored in each time interval + - Pandora uses a tool called Incident Manager for this task, where + + 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. + when necessary. + - This system is designed for group work. Different roles and + + 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. + the same incident, sharing information and files. + - Clicking on "Manage Incidents", in the Operation menu, a list + + 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. + incidents the user is interested on. + - The filters that can be applied are: + + The filters that can be applied are: + - Incident status filter. The user can display: + Incident status filter. + The user can display: - All incidents - Active incidents - Closed incidents - Rejected incidents - Expired incidents + + + + Property filter. + The incidents are shown by: + - All priorities + - Informative priority + - Low priority + - Medium priority + - High priority + - Very high priority + - Maintenance - - Property filter. The incidents are shown by: - - All priorities - - Informative priority - - Low priority - - Medium priority - - High priority - - Very high priority - - Maintenance - - - - Group filter. It can be selected to display just the - incidents of a given Pandora group. + Group filter. + It can be selected to display just the + incidents of a given Pandora group. + - The incident list is displayed showing information in the following - columns: + + The incident list is displayed showing information in the following columns: + - ID: ID of the incident. - Status: The incident status is represented by the following + ID: ID of the incident. + Status: The incident status is represented by the following icons: Active incident @@ -68,8 +82,8 @@ Closed incident Expired incident - Incident name: Name given to the incident - Priority: The incident assigned priority is represented + Incident name: Name given to the incident + Priority: The incident assigned priority is represented by the following icons: @@ -96,15 +110,15 @@ Maintenance priority - Group: The name of the group the incident has been assigned + Group: The name of the group the incident has been assigned to. One incident can only belong to a single group. - Updated at: This is the date/time the incident was updated + Updated at: This is the date/time the incident was updated for the last time. - Source: The source of the incident. The source is selected + Source: 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. - Owner: User to whom the incident has been assigned to. + Owner: 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 @@ From this form the following values can be updated: - Incident name + Incident name - Incident owner + Incident owner - Incident status + Incident status - Incident source + Incident source - Group the indicent will belong to + Group the indicent will belong to - Indicent priority + Indicent priority The indicent is updated by clicking on the "Update incident" button. @@ -193,7 +207,7 @@ Searching for an incident 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. @@ -212,19 +226,19 @@ - Incident status + Incident status - Incident priority + Incident priority - Users with the incident opened + Users with the incident opened - Incidents by group + Incidents by group - Incident source + Incident source diff --git a/pandora_doc/pandora_chapter5.xml b/pandora_doc/pandora_chapter5.xml index ef6edddf8e..a86bcd4edb 100644 --- a/pandora_doc/pandora_chapter5.xml +++ b/pandora_doc/pandora_chapter5.xml @@ -1,4 +1,4 @@ - + Events @@ -21,18 +21,18 @@ The event information list shows the data in the following columns: - Status: The event status is represented by the icon bellow: - The event has been validated - The event hasn't been validated - Event name: Name assigned to the event by Pandora. - Agent name: Agent where the event happend. - Group name: Group of the agent where the event has happened. - User ID: User that validated the event. - Timestamp: Date and time when the event was raised or validated + Status: The event status is represented by the icon bellow: + The event has been validated + The event hasn't been validated + Event name: Name assigned to the event by Pandora. + Agent name: Agent where the event happend. + Group name: Group of the agent where the event has happened. + User ID: User that validated the event. + Timestamp: Date and time when the event was raised or validated - if it has been validated. - Action: Action that can be executed over the event. - This icon will validate the event, disappearing the icon - This icon will delete the event + Action: Action that can be executed over the event. + This icon will validate the event, disappearing the icon + This icon will delete the event 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 diff --git a/pandora_doc/pandora_chapter6.xml b/pandora_doc/pandora_chapter6.xml index 37a918493f..3213d6b08a 100644 --- a/pandora_doc/pandora_chapter6.xml +++ b/pandora_doc/pandora_chapter6.xml @@ -21,11 +21,11 @@ The following fields display the Audit Logs information: - User: User that triggerd the event (SYSTEM isspecial user of the system). - Action: Action generated by the entry in the log. - Date: Date of the entry in the log. - Source IP: IP of the machine or the agent that provoked the entry. - Comment: Comment describing the entry + User: User that triggerd the event (SYSTEM isspecial user of the system). + Action: Action generated by the entry in the log. + Date: Date of the entry in the log. + Source IP: IP of the machine or the agent that provoked the entry. + Comment: Comment describing the entry Statistics diff --git a/pandora_doc/pandora_chapter7.xml b/pandora_doc/pandora_chapter7.xml index 5ab30d7f10..14648754ed 100644 --- a/pandora_doc/pandora_chapter7.xml +++ b/pandora_doc/pandora_chapter7.xml @@ -1,10 +1,16 @@ - + -Pandora Servers + Pandora Servers -From "Manage Servers" section, in the Administration menu you can see a list of configured Pandora Servers and also can manage them. + + From "Manage Servers" section, in the Administration menu you can see a + list of configured Pandora Servers and also can manage them. + -From "Pandora Servers" in the Operation menu you can see a list of the Pandora Servers. + + From "Pandora Servers" in the Operation menu you can see a list + of the Pandora Servers. + \ No newline at end of file diff --git a/pandora_doc/pandora_chapter8.xml b/pandora_doc/pandora_chapter8.xml index 3096a47ac0..867a4dc19c 100644 --- a/pandora_doc/pandora_chapter8.xml +++ b/pandora_doc/pandora_chapter8.xml @@ -1,4 +1,4 @@ - + Database Maintenance diff --git a/pandora_doc/pandora_chapter9.xml b/pandora_doc/pandora_chapter9.xml index 2d3490c051..f46e1ef3eb 100644 --- a/pandora_doc/pandora_chapter9.xml +++ b/pandora_doc/pandora_chapter9.xml @@ -1,4 +1,4 @@ - + Pandora Configuration @@ -9,19 +9,19 @@ These parameters are: - Language: 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. - Page block size: Maximum size of the lists in the event, incident and audit log sections. - Max. days before compact data: This parameter controls data compacting. From the + Language: 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. + Page block size: Maximum size of the lists in the event, incident and audit log sections. + Max. days before compact data: 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. - Max. days before purge: This parameter controls how long the data is kept + Max. days before purge: 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. - Graphic resolution (1 low, 5 high): This value represents the precision of the + Graphic resolution (1 low, 5 high): This value represents the precision of the interpolation logarithm to generate the graphics. - Compact interpolation (Hours: 1 fine, 10 medium, 20 bad): 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 + Compact interpolation (Hours: 1 fine, 10 medium, 20 bad): 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. Links