diff --git a/pandora_doc/en/images/Pandora_DataServer_Diagram.png b/pandora_doc/en/images/Pandora_DataServer_Diagram.png new file mode 100755 index 0000000000..bebdf99c0c Binary files /dev/null and b/pandora_doc/en/images/Pandora_DataServer_Diagram.png differ diff --git a/pandora_doc/en/images/Pandora_NetworkServer_Diagram.png b/pandora_doc/en/images/Pandora_NetworkServer_Diagram.png new file mode 100755 index 0000000000..c18ea2748b Binary files /dev/null and b/pandora_doc/en/images/Pandora_NetworkServer_Diagram.png differ diff --git a/pandora_doc/en/images/Pandora_SNMP_Diagram.png b/pandora_doc/en/images/Pandora_SNMP_Diagram.png new file mode 100755 index 0000000000..839777c483 Binary files /dev/null and b/pandora_doc/en/images/Pandora_SNMP_Diagram.png differ diff --git a/pandora_doc/en/images/access_graph_full.jpg b/pandora_doc/en/images/access_graph_full.jpg new file mode 100644 index 0000000000..cc74407caf Binary files /dev/null and b/pandora_doc/en/images/access_graph_full.jpg differ diff --git a/pandora_doc/en/images/access_graph_peak.jpg b/pandora_doc/en/images/access_graph_peak.jpg new file mode 100644 index 0000000000..2be141f366 Binary files /dev/null and b/pandora_doc/en/images/access_graph_peak.jpg differ diff --git a/pandora_doc/en/images/module_graph_full.jpg b/pandora_doc/en/images/module_graph_full.jpg new file mode 100644 index 0000000000..4a2485b330 Binary files /dev/null and b/pandora_doc/en/images/module_graph_full.jpg differ diff --git a/pandora_doc/en/images/module_graph_peak.jpg b/pandora_doc/en/images/module_graph_peak.jpg new file mode 100644 index 0000000000..bd629be655 Binary files /dev/null and b/pandora_doc/en/images/module_graph_peak.jpg differ diff --git a/pandora_doc/en/images/pandora-webbanner.jpg b/pandora_doc/en/images/pandora-webbanner.jpg new file mode 100755 index 0000000000..ca7062c2bb Binary files /dev/null and b/pandora_doc/en/images/pandora-webbanner.jpg differ diff --git a/pandora_doc/en/images/pandora_alert.jpg b/pandora_doc/en/images/pandora_alert.jpg new file mode 100644 index 0000000000..7cc3d586d8 Binary files /dev/null and b/pandora_doc/en/images/pandora_alert.jpg differ diff --git a/pandora_doc/en/images/pandora_database.jpg b/pandora_doc/en/images/pandora_database.jpg new file mode 100644 index 0000000000..b753e21e3d Binary files /dev/null and b/pandora_doc/en/images/pandora_database.jpg differ diff --git a/pandora_doc/en/pandora.xml b/pandora_doc/en/pandora.xml index eb1b253981..6b47d09dfe 100644 --- a/pandora_doc/en/pandora.xml +++ b/pandora_doc/en/pandora.xml @@ -5,6 +5,7 @@ Pandora"> + ]> @@ -55,6 +56,7 @@ &include_pandora_introduction; &include_pandora_install; + &include_pandora_advanced; &include_fdl; &include_gpl; diff --git a/pandora_doc/en/pandora_advanced.xml b/pandora_doc/en/pandora_advanced.xml new file mode 100644 index 0000000000..823973eadb --- /dev/null +++ b/pandora_doc/en/pandora_advanced.xml @@ -0,0 +1,168 @@ + + + Pandora. Advanced section + Pandora High availabilty features + + You may setup Pandora for use HA in several scenarios: + + + + Database Clustering for HA. You need to + setup a MySQL5 Cluster. In support forums / wiki are + information to make this, you only need to convert DB schama + in a MySQL Cluster compatible tables. This scenario has been + tested and works fine, but you need some advanced knowledgue + for MySQL Clustering administration. + + + + + Multiple Pandora Console. It's easy, + you only need to setup another one. No locking problems or + incompatibility has been detected in several Pandora + deployments. + + + + + Multiple Pandora Data Servers for HA + . This is the more complex scenario, because you + dont need to know nothing special about Pandora Server + setup, and you need to use of another tool to implement + Network HA, like VRRP or Keepalive. For Pandora Data server + you need to setup two identical machines, with the same + public keys for all agents connecting to server (and + duplicate server SSH host key). And setup Network HA to + point one of them. If one fails, VRRP or Keepalive "promote" + the other server up, and Pandora Agents, will connect it for + the next data packets. There is no need to change anything + in each of Pandora Data server, only need to be sure that + Pandora Server name is the same on both machines (in pandora + server setup, not in the system hostname). + + + + + Multiple Pandora Network Servers for HA + . This is more easy. You need to setup multiple + network servers in several machines across your network (or + all of them in the same segment), and assign modules to the + same server. If this servers fails, and there ara other + Network Servers active, marked as "primary" server, + automatically, the first network server available marked as + "Primary" launch the network module query. If you have many + servers marked as "primary", any of them could launch query. + + + + + Multiple Pandora Network Servers for load + balancing. . You need to setup multiple network + servers in several machines across your network (or all of + them in the same segment), and assign agent/modules to + different servers, balancing yourself load between all + servers available. + + + + + + Pandora virtual servers + + An special case for implement more processing power in servers + could be to implement "virtual" servers. Using virtual servers + (another instance of the same server in the same machine) is used + when Pandora Server cannot process all information without delay + too much. Pandora 1.2 it's using a limited number of threads to + process information (this will change in future versions), so you + can install another instance of Pandora Network or Pandora Data + server (with another data_in directory!), to be able to process + more information with the same machine. + + + + Pandora Database design (and redesign from 1.1) + + First Pandora versions, from 0.83 until 1.1 was based on a simple + idea: ona data, one database insertion. This was very easy to + develop and allow to program easily searches, insertions and other + operations. + + + This had many advantages and a great problem: the + scalability. This system has a limit defined in maximum number of + modules that could support in a "easy" way, from that number of + modules the management was too slow. + + + Solutions based on MySQL cluster was difficult and comes with some + problems and they did not offer either a solution in the long + term. + + + Data compression based on interpolation and data purge, makes a + smaller database, but this was not enought. Production systems has + a limit based on 100 agents, with about ten modules each one. This + was not a high limit for huge enviroments. + + + This problem was very important for Pandora future, so we are + changed the way Pandora store its pada. New data management system + store only "new" data. If a duplicate value enter the system, it + doesnt be stored in database. It's very useful to keep database + small. This works for all pandora data modules: numerical, + incremental, boolean and string. + + + This solves part of scalability problem reducing considerably + database usage, in about 40%-70%. We also have another solution + for scalability problems: total segregation of components in + Pandora and a built-in method to implement High Availability + solutions on Pandora components. You may have many Pandora + servers (network, data or SNMP), Pandora Consoles, and Pandora + Database (in a MySQL5 Cluster setup). + + + Changes come with some different ways to reading data. With new + version, if an agent cannot communicate with Pandora, and Pandora + Server doesnt receive data from agent, this "no data" cannot have + a graphical representation, for module graph there will be no + changes. You will have a graph with a perfect horizontal + line. Pandora, if doesnt receive new values, thinks that is no new + values, and everything seems to be equal that in the last + notification. + + + This graph, for example, show changes for each data, received each + 180 seconds. + + + + This would be the equivalent graph for the same data, excepting a + conexión failure, from 05:55 to 15:29 aproximately. + + + + + In Pandora 1.2 we introduce a new general agent graph for show + connectivity. It reflects access from modules to this agent. This + graph complements all other graphs showing when agent has activity + and it's receiving data. This is an example of an agent connecting + regulary to server: + + If you have low leaks in this graph, you could have experiencing + some problems or slow connections in Pandora Agent connectivity + with Pandora Server. This graph with previous example could have + an aspect similar to this: + + + + Programmers guide to Pandora architecture + + + + + + + + diff --git a/pandora_doc/en/pandora_chapter3.xml b/pandora_doc/en/pandora_chapter3.xml index 8eb864d373..16157d4291 100644 --- a/pandora_doc/en/pandora_chapter3.xml +++ b/pandora_doc/en/pandora_chapter3.xml @@ -150,7 +150,7 @@ - Normal mode: The modules in this mode - must be configured manually. The self – definition of the + must be configured manually. The self definition of the modules is not allowed in this mode. @@ -842,4 +842,4 @@ - \ No newline at end of file + diff --git a/pandora_doc/en/pandora_introduction.xml b/pandora_doc/en/pandora_introduction.xml index 830b1c901a..62245c4583 100644 --- a/pandora_doc/en/pandora_introduction.xml +++ b/pandora_doc/en/pandora_introduction.xml @@ -19,7 +19,7 @@ - Pandora detailed introduction. + Introducing Pandora. &pandora; is a monitoring tool that allows a system administrator to visually analise the status and efficiency of @@ -300,10 +300,48 @@ Pandora servers - Pandora Server is a Perl script that processes the information - sent by the agents. The agents send the XML data file via SSH and - the server periodically verifies if it has new data files waiting - to be processed. + With Pandora 1.2 version, you have three different types of servers: + + + + Pandora Data Server. This is a PERL + application that that processes the information sent by the + agents. The agents send the XML data file via SSH and the + server periodically verifies if it has new data files + waiting to be processed. You can setup different data + servers in different systems or in the same host (that will + be different virtual servers). + + + + + Pandora Network Server. This is a PERL + application that execute network tasks like sending pings, + TCP requests, SNMP requests and UDP request. When you assign + an agent to a server, you are assigning to a network server, + not a data server, so, this is very important that machines + running network servers have "network visibility" to hosts + assigned in network modules. + + + For example, if you create a module to make a ping check to + 192.168.1.1 and assign this agent/module to a server in a + 192.168.2.0/24 network without access to 192.168.1.0/24 + module always report DOWN. + + + + + Pandora SNMP Server. This is a PERL + application that parse output from standard snmptradp (we + provide one binary for snmptrapd, but its possible you need + to replace it with a binary that runs better in your + system). This daemon receives SNMP traps, and Pandora SNMP + Server stores in database and fire alerts assigned in + Pandora SNMP Console. + + + Data are extracted from the data file, identifying origin, type @@ -397,14 +435,66 @@ + + Pandora 1.2 new features + + Alert system. Now its possible to define a + "minimun" and "maximum" limit to fire an alert, just to delete + "noisy" data that fires false positives. + + + Network Subsystem. Now its possible to + monitor and analyze data using remote network tools, without using + agents, from the new Pandora Network Server component. All + management are made from Pandora Console, and now you will be able + to make ICMP checks (Ping), size network latency, get all types of + SNMP values (including scanning MIB), and makes TCP/UDP + connections to check ports, and test text applications, sending + texts and waiting for a specific response. + + + Module groups.Modules now could be grouped + using a new "module groups". + + + Network data refresh on demand. Could + be for each module or using a "global group refresh", forcing + Pandora Network Servers to refresh all network modules inside a + group. + + + Online contextual help, for Pandora WEB Console. + + + New Pandora server infraestructure. + + + New SNMP trap console to receive SNMP traps + and assigning alerts. + + + Internal messaging system, to notify events + to Pandora users. + + + Agent detail view autorefresh + + + New main agent group view + + + Improved database management system, that + allows to manage much more data. + + About Pandora Pandora is a project initiated and mainly developed by Sancho - Lerena, at present other people is working on it: Raúl Mateos, - David Villanueva, Esteban Sánchez, Jose Navarro and Jonathan + Lerena, at present other people is working on it: Raul Mateos, + David Villanueva, Esteban Sanchez, Jose Navarro and Jonathan Barajas. We want to give thanks for many other people who help us with translation, graphic design, bugs reporting and interesting ideas. diff --git a/pandora_doc/en/pandora_userguide.xml b/pandora_doc/en/pandora_userguide.xml index 540a99ce37..b124e4b90d 100644 --- a/pandora_doc/en/pandora_userguide.xml +++ b/pandora_doc/en/pandora_userguide.xml @@ -19,11 +19,11 @@ &pandora; &pandora_version; - + 2006 - Ártica Soluciones Tecnológicas S.L, Sancho Lerena, Esteban Sánchez y otros. + Artica Soluciones Tecnologicas S.L, Sancho Lerena, Esteban Sanchez y otros. 11/09/2006 @@ -70,4 +70,4 @@ &include_fdl; &include_gpl; - \ No newline at end of file +