From fc3b671897822811e342e7191e5cd643bff576af Mon Sep 17 00:00:00 2001 From: slerena Date: Fri, 29 Sep 2006 17:21:14 +0000 Subject: [PATCH] 2006-09-29 Sancho Lerena * pandora_userguide.xml, pandora_chapter*: Many changes to use PNG graphics instead .GIF. Many format changes. * many *.gif - > *.png: .GIF files deleted and replaced by .PNG. git-svn-id: https://svn.code.sf.net/p/pandora/code/trunk@204 c3f86ba8-e40f-0410-aaad-9ba5e7f4b01f --- pandora_doc/en/images/b_blue.gif | Bin 372 -> 0 bytes pandora_doc/en/images/b_blue.png | Bin 0 -> 557 bytes pandora_doc/en/images/b_down.gif | Bin 182 -> 0 bytes pandora_doc/en/images/b_down.png | Bin 0 -> 310 bytes pandora_doc/en/images/b_green.gif | Bin 345 -> 0 bytes pandora_doc/en/images/b_green.png | Bin 0 -> 509 bytes pandora_doc/en/images/b_red.gif | Bin 345 -> 0 bytes pandora_doc/en/images/b_red.png | Bin 0 -> 509 bytes pandora_doc/en/images/b_white.gif | Bin 375 -> 0 bytes pandora_doc/en/images/b_white.png | Bin 0 -> 555 bytes pandora_doc/en/images/b_yellow.gif | Bin 354 -> 0 bytes pandora_doc/en/images/b_yellow.png | Bin 0 -> 515 bytes pandora_doc/en/images/cancel.gif | Bin 529 -> 0 bytes pandora_doc/en/images/cancel.png | Bin 0 -> 754 bytes pandora_doc/en/images/config.gif | Bin 561 -> 0 bytes pandora_doc/en/images/config.png | Bin 0 -> 816 bytes pandora_doc/en/images/convert.sh | 8 + pandora_doc/en/images/data_d.gif | Bin 256 -> 0 bytes pandora_doc/en/images/data_d.png | Bin 0 -> 322 bytes pandora_doc/en/images/data_m.gif | Bin 279 -> 0 bytes pandora_doc/en/images/data_m.png | Bin 0 -> 373 bytes pandora_doc/en/images/data_w.gif | Bin 282 -> 0 bytes pandora_doc/en/images/data_w.png | Bin 0 -> 376 bytes pandora_doc/en/images/dot_blue.gif | Bin 223 -> 0 bytes pandora_doc/en/images/dot_blue.png | Bin 0 -> 386 bytes pandora_doc/en/images/dot_down.gif | Bin 172 -> 0 bytes pandora_doc/en/images/dot_down.png | Bin 0 -> 308 bytes pandora_doc/en/images/dot_green.gif | Bin 200 -> 0 bytes pandora_doc/en/images/dot_green.png | Bin 0 -> 337 bytes pandora_doc/en/images/dot_red.gif | Bin 200 -> 0 bytes pandora_doc/en/images/dot_red.png | Bin 0 -> 337 bytes pandora_doc/en/images/dot_white.gif | Bin 196 -> 0 bytes pandora_doc/en/images/dot_white.png | Bin 0 -> 334 bytes pandora_doc/en/images/dot_yellow.gif | Bin 223 -> 0 bytes pandora_doc/en/images/dot_yellow.png | Bin 0 -> 385 bytes pandora_doc/en/images/grafica_d.gif | Bin 144 -> 0 bytes pandora_doc/en/images/grafica_d.png | Bin 0 -> 226 bytes pandora_doc/en/images/grafica_h.gif | Bin 145 -> 0 bytes pandora_doc/en/images/grafica_h.png | Bin 0 -> 224 bytes pandora_doc/en/images/grafica_m.gif | Bin 145 -> 0 bytes pandora_doc/en/images/grafica_m.png | Bin 0 -> 232 bytes pandora_doc/en/images/grafica_w.gif | Bin 147 -> 0 bytes pandora_doc/en/images/grafica_w.png | Bin 0 -> 232 bytes pandora_doc/en/images/ok.gif | Bin 295 -> 0 bytes pandora_doc/en/images/ok.png | Bin 0 -> 460 bytes pandora_doc/en/images/outof.gif | Bin 273 -> 0 bytes pandora_doc/en/images/outof.png | Bin 0 -> 296 bytes pandora_doc/en/images/setup.gif | Bin 1475 -> 0 bytes pandora_doc/en/images/setup.png | Bin 0 -> 1832 bytes pandora_doc/en/images/target.gif | Bin 578 -> 0 bytes pandora_doc/en/images/target.png | Bin 0 -> 734 bytes pandora_doc/en/pandora_chapter1.xml | 252 +++++++------ pandora_doc/en/pandora_chapter2.xml | 106 +++--- pandora_doc/en/pandora_chapter4.xml | 543 ++++++++++++++------------- pandora_doc/en/pandora_chapter5.xml | 143 ++++--- pandora_doc/en/pandora_chapter6.xml | 95 +++-- pandora_doc/en/pandora_chapter7.xml | 22 +- pandora_doc/en/pandora_chapter8.xml | 440 +++++++++++----------- pandora_doc/en/pandora_chapter9.xml | 117 +++--- pandora_doc/en/pandora_userguide.xml | 1 - pandora_doc/en/schemas.xml | 1 + 61 files changed, 909 insertions(+), 819 deletions(-) delete mode 100644 pandora_doc/en/images/b_blue.gif create mode 100644 pandora_doc/en/images/b_blue.png delete mode 100644 pandora_doc/en/images/b_down.gif create mode 100644 pandora_doc/en/images/b_down.png delete mode 100644 pandora_doc/en/images/b_green.gif create mode 100644 pandora_doc/en/images/b_green.png delete mode 100644 pandora_doc/en/images/b_red.gif create mode 100644 pandora_doc/en/images/b_red.png delete mode 100644 pandora_doc/en/images/b_white.gif create mode 100644 pandora_doc/en/images/b_white.png delete mode 100644 pandora_doc/en/images/b_yellow.gif create mode 100644 pandora_doc/en/images/b_yellow.png delete mode 100644 pandora_doc/en/images/cancel.gif create mode 100644 pandora_doc/en/images/cancel.png delete mode 100644 pandora_doc/en/images/config.gif create mode 100644 pandora_doc/en/images/config.png create mode 100755 pandora_doc/en/images/convert.sh delete mode 100644 pandora_doc/en/images/data_d.gif create mode 100644 pandora_doc/en/images/data_d.png delete mode 100644 pandora_doc/en/images/data_m.gif create mode 100644 pandora_doc/en/images/data_m.png delete mode 100644 pandora_doc/en/images/data_w.gif create mode 100644 pandora_doc/en/images/data_w.png delete mode 100644 pandora_doc/en/images/dot_blue.gif create mode 100644 pandora_doc/en/images/dot_blue.png delete mode 100644 pandora_doc/en/images/dot_down.gif create mode 100644 pandora_doc/en/images/dot_down.png delete mode 100644 pandora_doc/en/images/dot_green.gif create mode 100644 pandora_doc/en/images/dot_green.png delete mode 100644 pandora_doc/en/images/dot_red.gif create mode 100644 pandora_doc/en/images/dot_red.png delete mode 100644 pandora_doc/en/images/dot_white.gif create mode 100644 pandora_doc/en/images/dot_white.png delete mode 100644 pandora_doc/en/images/dot_yellow.gif create mode 100644 pandora_doc/en/images/dot_yellow.png delete mode 100644 pandora_doc/en/images/grafica_d.gif create mode 100644 pandora_doc/en/images/grafica_d.png delete mode 100644 pandora_doc/en/images/grafica_h.gif create mode 100644 pandora_doc/en/images/grafica_h.png delete mode 100644 pandora_doc/en/images/grafica_m.gif create mode 100644 pandora_doc/en/images/grafica_m.png delete mode 100644 pandora_doc/en/images/grafica_w.gif create mode 100644 pandora_doc/en/images/grafica_w.png delete mode 100644 pandora_doc/en/images/ok.gif create mode 100644 pandora_doc/en/images/ok.png delete mode 100644 pandora_doc/en/images/outof.gif create mode 100644 pandora_doc/en/images/outof.png delete mode 100644 pandora_doc/en/images/setup.gif create mode 100644 pandora_doc/en/images/setup.png delete mode 100644 pandora_doc/en/images/target.gif create mode 100644 pandora_doc/en/images/target.png diff --git a/pandora_doc/en/images/b_blue.gif b/pandora_doc/en/images/b_blue.gif deleted file mode 100644 index aef45ab000197120acf82e95305b3ffb3cec85a8..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 372 zcmZ?wbhEHb6krfwSgOqc1m==Sp4z28y5;_cRl%mUq2~2bwk@&tZShVW$?n~0UVXI@ zZ0X+p8NL&;{3aHLP47!#uTGr5sEDI6V@Z4dijKlny=80rD%S02;+jykVN%V;sr8$u zHEx;Fylrmh&iUQDFHYfE(7R_*|K24N_bs1#aMjGi8|EM1y7csu!`07Eb^WIdDEC!0GwB`+5i9m diff --git a/pandora_doc/en/images/b_blue.png b/pandora_doc/en/images/b_blue.png new file mode 100644 index 0000000000000000000000000000000000000000..98a44fda202e83b63be4c3ddcb238cbf673fc9bd GIT binary patch literal 557 zcmeAS@N?(olHy`uVBq!ia0vp^0wB!63?wyl`GbMffdHQnS0HUJndGTm>Z4okZ&(#< zS{rI!A7$GTYu^^{)RFAoo#xe78^Mp*HM3gw^=jNv7l`t?=+$z@d^40P54b(WVb25PAq(^AM_btkZuZEW9% zh4zAi)sc|*gM!nOk@$my=aiK0oSV_DtJAQr@295Kx3wk6i--d?2{rsNA#{3Kq z`xO!KJ2LW5RMhL_q}#bU_uE^)H8owGIN^J9)8)w%e>68gpEBj$oY@!GuD-ls{rlz1 zu5RCUe&3$&>((7VeDKT0jjv9hdUN6Yhf5b<+_?VY`LqB3|L^OQ-3PQwp(MyJ7|6v3 z7-C|i-vZS#CV9KN$g}ba>;-Z-3p^r=fwTu0yPeFo12UXFT^vIsE+K^ zbLj-u8#j(dMowUrnDNv?Vgl=t6idmU0X$Pv9!+!*oFFFXx;1QqBSWY|hquK3!z;8I Z7(Uy}Ts~_g6kEzi&J=9@5s13kaBq{>H176W`x5r@ChUte*F)ZsD({rN27X z{_bD@XUdMha}WPp^Pd!;_>+Z^i@}~j2jmlwpBUK64$Lp$&=70)P->p?ONGHxY5CKv zwSH0=LKiajCae$3D!Cx!t#wT)lyjYx_W%F@ diff --git a/pandora_doc/en/images/b_green.png b/pandora_doc/en/images/b_green.png new file mode 100644 index 0000000000000000000000000000000000000000..9e36b27901b02111c5fc1301d916110b555fbd3c GIT binary patch literal 509 zcmeAS@N?(olHy`uVBq!ia0vp^0wB!63?wyl`GbMffdHQnS0F9Z&Mw`-RvW?Am%^^Q zRMcRpr2ca8MMWIut7J^qNSUvbvE86#y;F_Rs2hzv>qLYFhfMW9{$$^?#=9_&fLTzcv3!0ShXAd;$8wp(MyJm=t|j z)G{2Z-sl1}i!sUD-NoK6*`O52;VkfoEC$jZVC;4>+YZR+@^oPNn7B@7-(fBAdgYl_=4<7e)Z{-&u%-pGF#{59c9+&A5%_i^L{%XjrMvF8<|8d@)ZaTBUsS~L-`4iOxA#9kza33n z{~{v(#l-xLjs2I9@GmLpUsl%N?CgtEc>Wa>{3|K>S6BDHvGIR%^Z)kt|NZ^{r%wGh zZ{EKZE1n##{=a$a^HW{_i3W;4Ss1w(>=|@GJ^}fOfvxPo`~nUQv33uoY&#-EZ*ye5Pi?#p69RF=?|9gA?^Yh!$#Pu&C;$KY6-`LoH2?_s_lKy37{mst4IECk5LBYS0 zl7Dq|{~H_sH#h%pZ~x!l|9|S#fAi-3Te0HF;p+dJw?04B^`B_)fdA4%pdTDcg8YJs z)`VRl!=dVpEC@LQU;fhoDE&q0>z% zz&3 diff --git a/pandora_doc/en/images/b_white.png b/pandora_doc/en/images/b_white.png new file mode 100644 index 0000000000000000000000000000000000000000..e188dbdb6f310244af0fcb27f25c0626562eefaf GIT binary patch literal 555 zcmeAS@N?(olHy`uVBq!ia0vp^0wB!63?wyl`GbMffdHQnS0Ei7YA3byO`14a; z7tWl%e&y1w>(}nxzV-0_y~ht9JbnD=`O_yaoK7GYO`HB4)jYFU)zmVDnowWIez&u{gc`DK$@cW~T~GW${S^kmo% z)*GLjk6%b+T2WEu=dhQIgwfQpB8;kopu51$vV3m5Y>^IX>@8^4V zXSZheZ@RiHqWa9@lVuw+xqRoz8{JS_S1GA#yw1r0j*}jt1>e8$GB5-^XIGwZI<)|(gTd3)&t;uc GLK6VSeoT7+ literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/b_yellow.gif b/pandora_doc/en/images/b_yellow.gif deleted file mode 100644 index ff3e7557760898cada033b25cdebe866dedc207b..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 354 zcma*i%`1Ze90%~Y^>%iG?tnZ{^2kb^dw%|VgFawEw_v8yfNpd1t_PGoY} zM7AtDSZ!8hl(Zx%t+s}g9HdtOf-J1u=7KNx;khNm8C zDNRZzlFTP|X3S>wvTM9AYO}NMfLy&49@I|_3kz41Hcw{P7#eMJ4%9oQ(~czXY;Lud zXQV~tmS?10S=m_Q6A4Wgt3|D9;C+6*$!yZ;;|90eU@ W;Kbp`!J(9m1?ear37xy`)cp&Z*`$O3 diff --git a/pandora_doc/en/images/b_yellow.png b/pandora_doc/en/images/b_yellow.png new file mode 100644 index 0000000000000000000000000000000000000000..94fcec7922cca4db9fbfbe4d4558dc0db4badb4a GIT binary patch literal 515 zcmeAS@N?(olHy`uVBq!ia0vp^0wB!63?wyl`GbMffdHQnS0K&8z`)ADP#eM4m%_fN zh~rxX!;U7de?<%zr||rr&hUR8)BnY+|5vg8-^lQP1Ka;i4F9(<{NKv;e+R?=?cD$O zF#X@l^Zx+j|AP$w4zvD0#_<0*!~fF^PYzfAKO^w}Jj4I%49`z>{l6;u|2D(_dkp_? z%Kd-9@c%L6|0fLpAIScH#`ymk^Zyqt{~s&r-b29^+p$*t21Wy;o z5Q)pNeQ%{29RymJFVt94Bb>W$*_OnoOyB;!=eikawf|h@{Lg1(E=>Kf_|!r3_MJ-@ z>KQz3Lnf+aFtn|zndUXApY6%@-ye)DQv{h;raeDc^=C^L&*B_kO$Ts;aclj2rd6{ot RKL@&v!PC{xWt~$(696x97{~ws literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/cancel.gif b/pandora_doc/en/images/cancel.gif deleted file mode 100644 index 5fb77f777d857c5775248825273818652e1933d3..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 529 zcmZ?wbhEHb3>viHYC=N}2q-x6KEq_}-b_4u6Xe!4jGTv7UuWVg?0o}bda zUS$VeD#^T6n0BT-_hw=K`yBr>)V!C-u4Cs$$;M zC%qs-4FKaPkl@u`u&XUu<0bX4BH|8)pCmVUPghJ!%_(PH89! z@(cbyuz*riy{C&~2*>s074D2Y zGh);^E=wKy`l0aa>h<5Z225fvzRP4g_b>CCDx3|rG+CM znP;5Tb9;8`PgOzpnk`#ZDq0d_VnZ|S^2)@_IIjD|y14{(P41k?d?s{?u)x~&;_0ag pY{g%XnmF9z+1aykmn0_x!!aJ8s+A@xbwH;uc)I$ztaD0e0svszQ!dDjtoyM+=EHWi?K=*C*`c&^*P*w2wD0UJ|FK8q$evBR_nzFl=gi){r#>9i zKDuwykNv7Y4yx@xaQxtb6UPspKXUZav7={?9=mkx*yZELuADf2`P9iPr%qixd-D2^ zD~9LK-@16=`i*P%@7#WJ_x9rl_nzLr|NQ@;0gC@bor_WvOHxx5$}>wc6hbmm72G|2 z0~i#4vM_Qn)HCQX00Ahn7}!f2>gyf6>wTI!Iy*d@9J@NqJ1m;)`s+muy6mU%ILoAk)W~2B01P}>)&Kwi diff --git a/pandora_doc/en/images/config.png b/pandora_doc/en/images/config.png new file mode 100644 index 0000000000000000000000000000000000000000..17ebecec9fa4b5b1019f31847baec00818830811 GIT binary patch literal 816 zcmeAS@N?(olHy`uVBq!ia0vp^{2~AoLqQwvdqj`>&{HGoil6WxtTWW=5>CW#=mIEhDA#@{+P~tWs&XT zB|DzXSAMWa{q1~-A9MJB%n>-Uq;mO+t$UaCK3=ZAa^;@eD;?Ia+4+8@^oLb4YuE4n zu|ne8YRL!doxZP@{IOPY%ck8IHdKAwp!8#%)WwZ;KQ_pG*sivH$KfwKly>eq^mdQ- zot@=B_NW}$vuXFj$S%;^z6}N zmyR8~eEisz6UQ%~I(g;PsjFvCUjK2$@cj8(7cX4Daqa${+fVM^e*ECx)BE?I{~t79 zv(J?^z$j@b3GxdbU`H`nuzIHh-NKmU?e0?VvA^&ski%Kv5m^kRJ;2!QWVRiU(e3Ht z7{YPg_v}?Zra&H+3*FW_@3!sOy?KXqyvhD^yq?^?w@y~h|tsfzDE^ z3W+Fj&d<$F%`0JGsJKe(%4 zLE!4yt5@G$ZT@z(`QFv5_paUpf_KlZetUNI8<70=?Ay0*|G(V>690h+3Fv@q0NKUB z+M1xyr)0piLeul|#=W-{PWK4-_#`LTsC_mP=_`EklkGs`%76xgxvY^71$jg?CLUEy z-grVUE|no@VTSSa)8V!p4C_Q&S!L$2GYYXKU!Q%^hmW_~t%XO)!m7nqibsQkeL~fw pswOt2%H}ScHuI?x;(Co-9BER9h?Ook;OpT1B~5HX4?T79iA?ZArhB;`)&(0EAY5@ z2G6?1wtB&m>Hq(q&vS4;pHg|_W(wyP!5F@$F;CcUT=ZVB=;b%IGkPvvtLE@_6=ofl ziN721Yb6@wnXw5o4mMm6nf^8Ktnk%a7uW3CTA>?u>`HIjrH}m2yIpp4ca%+V xP1;|$<_E8}Wafm|GlFLs&tufRvW5RI2q{8%muoM!PC{xWt~$(696Z6pF{uv literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/data_m.gif b/pandora_doc/en/images/data_m.gif deleted file mode 100644 index a93c07a0e85a858013183a7fff9215dbd2343253..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 279 zcmZ?wbhEHb6krfwXpv?B0uBZS2?2pCYHD+)%(*&6V9lB}Th?p=g1uYzo;|zw>e(%4 zLE!4yt5?5WZN7K)>bxbHc@i{fkcBclgPB} zB9nJEjmA7m7FJC*k~|t5?0sbu%IevaN*g+wTPKT)&1hldc6~|%l2$O3%yA$?858H*^kUvv9&EC+jWnnhm72|+ZQGu@!6J~Keb~2*F%kd zPyXu8Z_^!<4BuogM67!t|FN zcfDl$#HpqAT{cf*zm=FT r$I~}Zw2J!e;*a5}XBsDr`N)z4*}Q$iB}Ea<8T literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/data_w.gif b/pandora_doc/en/images/data_w.gif deleted file mode 100644 index 5e41097732304d9cb4f73ce853aa62c96a57f0a9..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 282 zcmZ?wbhEHb6krfwXpvz60uBZS2?2pCYHD+)%(*&6V9lB}Th?p=g1uYzo;|zw>e(%4 zLE!4yt5@G$ZT@z(`QFv5_paUpf_KlZetUNI8<70=?Ay0*|G(V>690h+2`K&(buLOx zEJ;mKD9@0jjyu5R%EaS0C*FF&Hw-a diff --git a/pandora_doc/en/images/data_w.png b/pandora_doc/en/images/data_w.png new file mode 100644 index 0000000000000000000000000000000000000000..84e7724e7974fa9e6bf5039c1e1f88fd6a52fc58 GIT binary patch literal 376 zcmeAS@N?(olHy`uVBq!ia0vp^0wB!63?wyl`GbK}LV!<*E0E@3V2}_HxT2;uXUd$b zQv}wmS+ix$79iNWW$)Rud#|3|aux)xp1peY-PPuASDWu$y?XEJJs^1Z?CQ5?XTJf- zZ_mDc`}Y6aJs|NPh>(Co-9BER9h?Ook;OpT1B~5HX4?T7J)SO(ArhB;`x^NUDe$P|d=YM@w>f|>;QlECj8J3)S5g5pEaqG1i*=x_3I|u$*e80L`wQGmALbkYW z+UfbsOTNbLo4K>#UBXQvhrot5U$flxF-CEU-4_%VMNimKEZTGCAB)z)kNxXp`97DN zJE>UlP(m`<#rPEKkCS(wKlm$kK`m!t-9K0R&$-+yG^bn_0lG`ADkP%BIX^cyHLrw$ xq2gAto|mtVr*ELfd7YC1949?O3%-8=dMfBSyYht7sRckC44$rjF6*2UngF(PuPFck literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/dot_blue.gif b/pandora_doc/en/images/dot_blue.gif deleted file mode 100644 index bd04ea304593d3b6a72488cfc9d4920fb375832d..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 223 zcmZ?wbhEHbS7pt6@AjN&6CCEZUGX2 diff --git a/pandora_doc/en/images/dot_blue.png b/pandora_doc/en/images/dot_blue.png new file mode 100644 index 0000000000000000000000000000000000000000..cf4323374a46541ae18b2ff742db7f38af6e1085 GIT binary patch literal 386 zcmeAS@N?(olHy`uVBq!ia0vp^AT}2VGmzZ%#=aj&B?S0{xQZIIOBi=4+s@UpU!iNi zR>NVJlIv`QUc71E^{@BFxg@xxEo2U(LK_6T~KR8D{4T$&>6!|SW z|7CjC@2sqUd3oQOXFQ#}xZiiF1B#Zfaf$14G5FVm&Wk ppOfJp=gtRnob(7S`2K~Lfx)q#&34`T>z+XM44$rjF6*2UngFFUtQr6S literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/dot_down.gif b/pandora_doc/en/images/dot_down.gif deleted file mode 100644 index 1ac77f133c4cf0f1b9ba541b318f41860af86cce..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 172 zcmV;d08{@*Nk%w1VF~~W0E8a^|0gH=F){m2PUc-)`Bzr@SXld6S^QdB>tkZuZEW9% zh4zAi)sc|*gM!nOk@$my=aiK0oSV_DtJAQr@295Kx32mm|zzE)-c diff --git a/pandora_doc/en/images/dot_down.png b/pandora_doc/en/images/dot_down.png new file mode 100644 index 0000000000000000000000000000000000000000..fa10485103ddfee70fd950c2dbbba647ff17aa9c GIT binary patch literal 308 zcmeAS@N?(olHy`uVBq!ia0vp^AT}2VGmzZ%#=aj&B?S0{xc*mH|7~da+t2S=Y|PK_ zuwM}ozau06L`A($PP(0&bHBayTT|23i4(pzH(j1Q@kev>^C?r_&6$01?dr=L*1uoA z?CSPy=lAXTzHZ&|!w0`?-1zGBsW%tSf4Fq<#f|GPogTe~DWM4f{CJc8 literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/dot_green.gif b/pandora_doc/en/images/dot_green.gif deleted file mode 100644 index e3b94776e57b392da55b808b37a5466a407a2e08..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 200 zcmZ?wbhEHbogDOH4U00xEGiIC}Pst!n`L@6>sxr->hAG zdGf($TmFNA;!hSvE(Uo99R?r(*~!4_`rv!+l*EA97EFx+GhVXE$V^k{a%79y?%2(~ zSmnS3DZZ0Sk~CBlPIx>G(o_`dJE4+n$S1<@sk+#(kE7@0(%C{2mrN_;V6X-N3o}n2 diff --git a/pandora_doc/en/images/dot_green.png b/pandora_doc/en/images/dot_green.png new file mode 100644 index 0000000000000000000000000000000000000000..20ed4ac8a9b6074f440276ea8d3141720cb8c385 GIT binary patch literal 337 zcmeAS@N?(olHy`uVBq!ia0vp^AT}2VGmzZ%#=aj&B?S0{xLRk*+vO^H*6RAS8vAvc z2lSc-O*T!O;1ssjICi~d=q{tM{e}^T&7)43gq|~qIA@Z2!Y<*mZQK>R1<)%lcEg_0n@V2B7#k|8EW`Yli` zW0JSKi##i@z+NDSv%n*=7)X17vD?XPJ0K&@)5S4_-T-E(_(hM|M;f$T$#PQT8&dr7|2F<{5%yPIbGm# uEYF)~f6sis9w#(Of@$r9YvP%h^O=F~pNI9Ih3u=S z>b}4GyrKH+>i_@$A^8LW3IHDfEC2ui015yK000F=;P-8lVN9Di0)ar7=>{C!l^}{i z2AsD&3rM3RxR4kQNyTCyBp%3!1!E~87LEu-lQ9ky5Q#<8F^&q23Z|P9k))Y+2mm|O C&r^~B diff --git a/pandora_doc/en/images/dot_red.png b/pandora_doc/en/images/dot_red.png new file mode 100644 index 0000000000000000000000000000000000000000..3d2b3ca2d7babffa01a0bac857d3042e1f54973e GIT binary patch literal 337 zcmeAS@N?(olHy`uVBq!ia0vp^AT}2VGmzZ%#=aj&B?S0{xVFm6cPc8*G02IeN_;Ze!)O4KEMzY zBmEYrmNCiO-9?_2S70xY!&%@FSq!8-z}W3%wjGcW=jq}Y!f{>nEGJWw0T0UoR>LAO zFO`Klv;P0T^s7u;UyxfY)N`_wA8+bL@KxlDVWOT4e=Y?{k9 zwa)8jtth+v<88OU7KXjqDU<%O>u-0?QZf5t9d`RmjJvJ_ZDR0r^>bP0l+XkKU8a{x literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/dot_white.gif b/pandora_doc/en/images/dot_white.gif deleted file mode 100644 index 2632d652c9e4fd5c93d6f13a833cbbb0e155527b..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 196 zcmZ?wbhEHbs^Wx2$m+#)a`ts$|e{4YU zCkrDNgFJ%{0}z1hWMFlC@I7);qQ^7~rpAC7D_Ld4rz&(gvWcfzcC#&3SujC@*JDYD lhs6YbPS+qO7J0!_M=SzVmWn>^IB+5_SShHaiI0)N8UUZGa2Ego diff --git a/pandora_doc/en/images/dot_white.png b/pandora_doc/en/images/dot_white.png new file mode 100644 index 0000000000000000000000000000000000000000..3253384b9699de6ab2eb41827af8ad97b568e271 GIT binary patch literal 334 zcmeAS@N?(olHy`uVBq!ia0vp^AT}2VGmzZ%#=aj&B?S0{xE?yP^T@GXCr=$Xd+x}& z^T*C#IDYZc$xD|{U%zqj=B-P&ZePBA`|90$*Y7{L`QX8=hmY<&dVKfs<9kn@+<*T3 z(Tf+4U%z?r=FQ7@?_PcR^65V|u-NeI1E5_BB|(0{*yNGK7-C|i-vZS#CV9KN$g}ba z>;-Z-3p^r=fwTu0yPeFo12UpLT^vI=u8a11i!~eY9AVRVCO+9wEw1egE%) z|M{W)_~-xs|NsC0A^sCXa%Ev;Zy;lDZXi@>WgtgMO;7+K`2+z903QG>000003IGZK z00l+h_g&F(M3*=Mfnb>F1rXSTB+5YsSa&fCh@&K!kQxt4#d0tp7)XgFV<{yT4@qUC ZF%A?Eie#w2fd7kO4*fxSQuXMsm#F_88EW4Dvpc0fj)r;B3<$92)O++xiNJS+#UuKL)| zcv5Sd{`dV$zc3jWEbr2|`_SbwpHhjy-Kobi#hhlpK3-~B*1Dy0SF5pfio|tYm)*Qt zmxYq*yqN4i7vB2pyC!1)^W96j{&r_971K|&W&5%?@E5(b8f vTg7@_zCI_zJKQy;{an^LB{Ts5TvoW) literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/grafica_d.gif b/pandora_doc/en/images/grafica_d.gif deleted file mode 100644 index 1f6b0f51fba6a486e03ca46f90a7345aa00548dc..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 144 zcmZ?wbhEHb<&(&(%{EpIe)Mn$8}Tbf8wPYFhR##vsR%C@$qsg$3r0FZLW<5Wo<}!0dQ1 XVT%HL%cFN1DrVXZYs{)U85pbq`UO3- diff --git a/pandora_doc/en/images/grafica_d.png b/pandora_doc/en/images/grafica_d.png new file mode 100644 index 0000000000000000000000000000000000000000..c942efc70c31ca45509fd15de552cfe54982079c GIT binary patch literal 226 zcmeAS@N?(olHy`uVBq!ia0vp^{6H+g!VDy>D=f@`ltF+`h%1m55;gZqstzjdzUQd$ z%u(T<}A7D jWk8#!#Viqy1__1@Ta6sV+QhtpCNOxq`njxgN@xNAl&w>o literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/grafica_h.gif b/pandora_doc/en/images/grafica_h.gif deleted file mode 100644 index 26e0c6dc9f3bb26c88d338826d77cefd3809dbca..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 145 zcmZ?wbhEHbD=f@`ltF+`h%1m55;gZqstzjdzUQd$ z%u(TEOo0HcgK(*OVf diff --git a/pandora_doc/en/images/grafica_m.png b/pandora_doc/en/images/grafica_m.png new file mode 100644 index 0000000000000000000000000000000000000000..3014e298447c9b1792142a8db60de649f332515b GIT binary patch literal 232 zcmeAS@N?(olHy`uVBq!ia0vp^{6H+g!VDy>D=f@`ltF+`h%1m55;gZqstzjdzUQd$ z%u(TD=f@`ltF+`h%1m56*BiqstzjdzUQd$ z%u(TQIRoiM|cD8lZ-~A q8NP=X@?0&^IIJS$%f;fr!|;dMSm^VKd0Ieo7(8A5T-G@yGywqOIak{N literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/ok.gif b/pandora_doc/en/images/ok.gif deleted file mode 100644 index f33c30cf5baf8e680532969d6a71c90a27194377..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 295 zcmZ?wbhEHb<$ZZlSVjeGHkuI-P$!(P*>zX5LRjTY-Ch1~Q9H8JFrn8xY^izpQq!bOcA>j1%2ovxtqslD=|?zfB@tt z1~!)i^9wvgw7O2*Uphghtk--`OVDy$j diff --git a/pandora_doc/en/images/ok.png b/pandora_doc/en/images/ok.png new file mode 100644 index 0000000000000000000000000000000000000000..42054dea61a7bc0acbb3fe6a2f202d16db9b4678 GIT binary patch literal 460 zcmeAS@N?(olHy`uVBq!ia0vp^d>}RlGmu=zwB8p;9SHCVaaD8XRZ8SGi4-x9m#|2e zSE}T;%8_-=k+mvSb}f^1uh#SKQgiRu@SLa}*=d;2YaX`LJbbBX(k8pm-4$P{WKze4%#JJRJ$DOcU9akT zoVVm!^M5LV2k%ck1p39HB*-tALL(UtRc~|wn#Gvp?e1c4muyf9vL>2>S4={E+ znQaGTM0&b7hHzZ>J?kpe;2_|9v2kHxdAX(AyL#;vhpcAD=Zi9$NjI%jICqjQ`MN-I zv4=sP;$5HS)n6AqO0$dj@O*~cqO9JWD<3Ys`ED9ycSu)Q*8ZX85zV8;6-@CdD$f5H SR;2(fVeoYIb6Mw<&;$U`=KI9} literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/outof.gif b/pandora_doc/en/images/outof.gif deleted file mode 100644 index fcbd16237b03a06dfef4b1c8f9dca4e0f939f6e3..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 273 zcmZ?wbh9u|3}E1Ac+9}?|NnmmAZg>R6FBXEPR0Lom;OI{@qg>?{~?M0Tl@acT?$ly z40M3189;g&SdJN-@Lavu;`Q0(KN2+hQZnadXtAvF5NQh(cvdLqno;xf=54jG*UknP zSdKoNYMfEUS`*yg*i#bz%;jR>FSw#H}5Xh)i(@d;xasL6PIAr9kg%HspD+LiU;T4xOwaPt-JTs@7#a% Q_~GMcx1Ya!B*p!VDxEpNH-NQU(D&A+G=b{|7Sv+j#2)PWzuz z@&DYV|Ic3h-@5yMNaFw2zW;NV0u>;GQ=jkd1Zv(!0cHKIi?~jO;s1N_lMmwS{g7ReS+vJw}n-0FBs(a aa4~XhPPp{NsJ#a0QU*^~KbLh*2~7Z|xOA@o literal 0 HcmV?d00001 diff --git a/pandora_doc/en/images/setup.gif b/pandora_doc/en/images/setup.gif deleted file mode 100644 index 737ec852b425660d4d7bd964887a15dba80366d1..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 1475 zcmV;!1w8skNk%w1VITk-0O$Vz00IC21_=NW76=p`1Q;L%Bqtdh9u6QW04*{fASewe zFcC6TA3Z-BKteGyP%1n|IzTrbNLnOBc_vIwFGx`&NO2`lR!2!jF;HDQP){vYVJui) zH&jnf;cW!WPNq�Xa=Wf6GnoVW_5?KX#lin z53*|yba;Sme1fQNDUNkeoN_y{a1&;MinweZsB|o*bUChcC%la0v3rY!zkDIAfI@+Yka>)lkceC}? zgFn!I26>R6iI0V@hEiOexypbr(SIX_k&@Ye4}O)Ikdlv(l$V*1madRraGkX2%+y^Wcg>W2V}nxW!{8-|^t;)f;ahZ207*P)n&n3|V{ow~Y|UVWsp zqL`kTou6E@&5)p`WU$MWprMVVspydz;gT!jk3zDae0i+WprW7XlqSBNa+IjE>6AE_ zsIGso$#Jyar=+Qfu)d(Eu->3Ef3?T1sFlE^eyFOa;-EzMo*r(%;h3<_`I|cVpDU=a zxZbHxysw?Gvak50H>k70>Zek_u$ZN_$hohzue7%IrAGRz8~CO`thl-PtVFc9!MC}# z_^eBN(Cd=O+qb;Gzr3w~(DJar$HBb1`m<2B!^G0NrT4g5z{0=3#K!l%Rl&!-yvfSE z$k3kD=lQ^2$;iL@ziivYt-{R5@4%7w%1+74$ojy5(#*H}$7IRS#rex#&dkun(b3V& z%E-{z`OR(5(a!eKZ}HHA*3-n#)YsC~(b?0|-_*y~)!De=@A%Y>(%aV9+Sm8mgWlQL z*WBO9;^*Mp&iUYa;oI8Z+~NA)j^5zi`s9k?_CX>@2HRA^-&M@dak03rDV0SW;B04x9i001BW8vpj`rA1)yfFgrn5FsWj@d6n^W*RhL5Q#xiMu(F|q%c9D z%0OEmXrxd%B1%Ccc^u+{gJVZe4+Sz1(|3miI&sN%ty0wR-?0n`T>c?Va7@|S<&gAJuLzZKmZ6$?c$3=M4aLeKm0Tk2_B08 z!_6#BuyD*i*0iC87F&QJP(4?`Qx9_g+>^vN{Pc5<7(@&q#3I#H!^aAL#8b|Q_S{27 zIs#Quj6U}aVq;JMlQ7*=CP)p-Dr+V8I6|vEahW8ArTf4?Bt7Br?ZpmRy1k zJg2!+h7w2UphFhU81zdqu@-ldFYVZ)O*i7~lN>eF#Pbh3sr*9BFP}Wo+)4F7Vv97- zJOc(HyKK`e0uFyuYvBj0MayWO{?Dv;+a3ju zx!c$}nmZo1bVt~H>vO>O^cP>koW2S0^!2cYT(tAUA2}E727%i_lI&p@&O!sefc@YF z3ps|o;t~<%fe819!|kqI{R$NaLxy`s6`ErjwOeq@5f_Ou3-|P8HMb4P>LXpXmNylR0>B_^h2vC&8G;9!4V_u^r!;xhBv60F%+ms;#84%R`4vA|_!N|FFP zk(^0PEh0q4-Y%En075n?D?1ZUz7tl$yP2OOOgmIhJe^6V;BV6?WK0;Xi${P)(m3Qi z67QCeBEuL@Vg6Q_!^sVeq_;mK9`7d{&M7J$C0JyXlu?QcDb&(3${!pG3d3v~AbFt6 zUjIR*N%Os1DadGcXF*x{8xoLTUZo-(%%xYWNcQujy=fK0RkR#hd1)@aqk|fi&T6ct zF=+J4$R-(uSsTOcr827uSoh|N_RkbMs|rsyR;J*|K{j?10YoZw%w@+8$sjGBmbK8{nLii1I zZexR%<-u<1dQ%rFlq!Qp|y{?Qi$Q-k8+m!oYnOWMJLf$^b{v0=^FE#>IQ@Whle}1v`PjJh|=(sJ<&2)9yaOS&RMh?ie5aP&BES4S1&aOl8@wp2_2rE;g##U)X zywg=DlPvoQrz*3IeGw6tB6@j&);c6-Rn;$@eDIjaIq52`3O9!@dmZz3sh`e0WK~+t z9`K+j9!|);7hKNWkCp9lR<@ML4BW4eWZ!;ilbPM;?Bu>96LLxHNq#GsDOn#S zA4^({p)6|z5C^x0ZfL3R0t%eMy`C^~(%Ktf_h>wsBW8z}7|4q7wV2Ubh7JTT9dWq3 z5Kb{IiQApK+jq#Uz^GEd_q@5V%&QTMC4+?g=;%1Ob{B$s)22JB^cA?hb;^rZy(yy0 z1fF67s<$97FBovr9@w6F>&C2MXuz#>#;j^#Fn#Tpf?q#~>rjOBP3zUYbNPz9LV@9V z@_3RuEJQR3Rt7Ed%cEhSuBTv9?J!H^<5P@B^6*w6OA@ky`zL&G@Ij|qHY^WWGPW@w zJ>AMxsosH=EVL4CN%cXm_Yg`a!w8c*`=q^PK*({6yXY-c5fA_VNlu09cKh_=%HrLr zKLnwY8! z$@iF$DFtAF@`e7P$x+dEo2ExkfuMY>^85RY1%pW z_Up%TO}=tXe%6yy?53optZXUR*jKa>C_8)Ext-QiQf#NB#;ezX zlRMw*|Ns9CU;tzcX`uL%g^`QFoZ)$F7ZDSGQ=j9h-X=~yV5aG7q z77^fTNP)thBR7aAjnN8J1Oz%X z)<72lKOtVx1H?b%lTrAHlpi$MJaNuyaggzS+gEasu;BP7b diff --git a/pandora_doc/en/images/target.png b/pandora_doc/en/images/target.png new file mode 100644 index 0000000000000000000000000000000000000000..edc180d557e7768a1574a64472292f2ab075a79c GIT binary patch literal 734 zcmeAS@N?(olHy`uVBq!ia0vp^0wB!63?wyl`GXl47#jk7LR?pz+qdrGq16}mue*3~ z!^J~&+h=F5@5x@*Q@CM5!;U#kJLleh{aCKaSFXv=dUA^0l(dwUEd?9Uq z(|SsZ?UdB`l?@3i8xmJG6>RLCdUW-)qpNc_c5S$JVBWcn^UrPCcX-~WGd=X?GC{~zcPAOJFkG-#i2FC6F%hms(_UP>Ww zS@d^<#R4NW?sL_0x%_QqB_Az#8YY|WOUtaAY}rs@aAWanHvTjdQMcg4Uq;W{_5Zvn ee)s-u_&w3vI@!F+TW0~C&EVHtW>@ literal 0 HcmV?d00001 diff --git a/pandora_doc/en/pandora_chapter1.xml b/pandora_doc/en/pandora_chapter1.xml index 009cdae410..952ba6d53f 100644 --- a/pandora_doc/en/pandora_chapter1.xml +++ b/pandora_doc/en/pandora_chapter1.xml @@ -1,128 +1,134 @@ - Introduction - - What is Pandora? + Introduction + + What is Pandora? + + + Pandora is a monitoring tool that allows a system administrator + to visually analise the status and efficiency of Operating + Systems, Servers, Applications and Hardware Systems - such as + firewalls, proxies, databases, Web servers, tunnelling servers, + routers, switches, processes, services, remote access servers + and so on. All integrated into an open and distributed + architecture. + + + Pandora can be implemented over any operating system, with specific + agents for each platform. Pandora can also monitor any TCP/IP + hardware system, such as load balancers, routers, switches, printers + and so on. + + + + Pandora architecture is formed of four main components: + + + - Web Console: Pandora's user + interface. The user controls and operates the system with + it. Several Web consoles can be implemented in a single system. + The Web console is written in PHP, and rests on a database and a + Web server. It is compatible with any platforms - GNU/Linux, + Solaris, Win2000, AIX, etc. However, the official supported + platform is GNU/Linux. + + + + The console permits the user to control the status of the + agents, view statistical information, generate graphs and data + tables, keep a system incident control, as well as to generate + reports and change the alerts, agents, and user profile + settings. + + + + - Core Server: Pandora Core server is the + receptor of the data packages and generates the alerts - it is + the brain of the system. Several servers can work alongside for + larger systems. It has been developed in Perl and works over + any platform, although, the official platform is GNU/Linux. + + + + The core server accesses Pandora database, which is shared with + the Web server, and stores the processed data packages. The + server is executed under the name of "Demonio", and processes + the packages stored in its file system. The data is generated + by the system agents. Despite the server's low system resources + comsumption and simple installation and operation, the core + server is the most critical element of the system. The core + server receives and processes the produced data, and fires the + alerts and the events. + + + + - Central Database: At the moment the + system only supports MySQL. The central database keeps all the + information Pandora needs to work - agent data, settings, user + information, incidents, system settings, etc. The system can use + a MySQL cluster to store the information, or a high + disponibility solution for larger sytems. + + + + This database can work with any of the platform officially + supported by MySQL. Pandora can be implemented with MySQL + versions 3.0 and 4.0, although the latest is recommended. + + + + - Pandora Agents: They collect all the + system's data. They are executed in each local system, although + they can also collect remote information by intalling monitoring + sytems for the agent in several different machines - called + satellite agents. + - Pandora is a monitoring tool that allows a system administrator - to visually analise the status and efficiency of Operating - Systems, Servers, Applications and Hardware Systems - such as - firewalls, proxies, databases, Web servers, tunnelling servers, - routers, switches, processes, services, remote access servers and - so on. All integrated into an open and distributed architecture. - - - Pandora can be implemented over any operating system, with specific - agents for each platform. Pandora can also monitor any TCP/IP - hardware system, such as load balancers, routers, switches, printers - and so on. - - - - Pandora architecture is formed of four main components: - - - Web Console: - Pandora's user interface. The user controls and operates the system - with it. Several Web consoles can be implemented in a single system. - The Web console is written in PHP, and rests on a database and - a Web server. It is compatible with any platforms - GNU/Linux, - Solaris, Win2000, AIX, etc. However, the official supported platform - is GNU/Linux. - - - - The console permits the user to - control the status of the agents, view statistical information, - generate graphs and data tables, keep a system incident control, - as well as to generate reports and change the alerts, agents, - and user profile settings. - - - - Core Server: - The core server is the receptor of - the data packages and generates the alerts - it is the brain - of the system. Several servers can work alongside for larger systems. - It has been developed in Perl and works over any platform, although, - the official platform is GNU/Linux. - - - - The core server accesses Pandora - database, which is shared with the Web server, and stores the - processed data packages. The server is executed under the name of - "Demonio", and processes the packages stored in its file system. - The data is generated by the system agents. Despite the server's - low system resources comsumption and simple installation and - operation, the core server is the most critical element of the system. - The core server receives and processes the produced data, and fires - the alerts and the events. - - - - Central Database: - At the moment the system only supports MySQL. The central database - keeps all the information Pandora needs to work - agent data, - settings, user information, incidents, system settings, etc. The - system can use a MySQL cluster to store the information, or a high - disponibility solution for larger sytems. - - - This database can work with any of - the platform officially supported by MySQL. Pandora can be implemented - with MySQL versions 3.0 and 4.0, although the latest is recommended. - - - - Pandora Agents: They collect all the - system's data. They are executed in each local system, although - they can also collect remote information by intalling monitoring - sytems for the agent in several different machines - - called satellite agents. - - - - They have been developed to work under a specific platform, - making use of the specific tools of the used language: VBSCript/Windows - Scripting for Microsoft platforms (Win2000, WinXP y Win2003) and - ShellScripting for Unix - which includes GNU/Linux, Solaris, AIX, HP-UX - and BSD, as well as the Nokia's IPSO. Pandora agents can be developed - in virtually any language, given its simple API and being open source. - - - - Pandora Administration - - - The web console is the tool used to administrate - Pandora. It is written in PHP and doesn't need any - third party software to work, neither FLASH, JAVA, - nor ActiveX plug-ins. The Web console can be run - over any web browser supporting HTML and CSS (IE5+ - or Mozilla 4+). - - - - Pandora administration is divided in the following - main elements: - - - - Pandora users - - - Agents - - - Alerts - - - Incidents - - - Server configuration - - - Database maintenance - - - + + They have been developed to work under a specific platform, + making use of the specific tools of the used language: + VBSCript/Windows Scripting for Microsoft platforms (Win2000, + WinXP y Win2003) and ShellScripting for Unix - which includes + GNU/Linux, Solaris, AIX, HP-UX and BSD, as well as the Nokia's + IPSO. Pandora agents can be developed in virtually any language, + given its simple API and being open source. + + + + Pandora Administration + + The web console is the tool used to administrate + Pandora. It is written in PHP and doesn't need any + third party software to work, neither FLASH, JAVA, + nor ActiveX plug-ins. The Web console can be run + over any web browser supporting HTML and CSS (IE5+ + or Mozilla 4+). + + + + Pandora administration is divided in the following + main elements: + + + + Pandora users + + + Agents + + + Alerts + + + Incidents + + + Server configuration + + + Database maintenance + + + \ No newline at end of file diff --git a/pandora_doc/en/pandora_chapter2.xml b/pandora_doc/en/pandora_chapter2.xml index 62fc5f4f0c..3461333007 100644 --- a/pandora_doc/en/pandora_chapter2.xml +++ b/pandora_doc/en/pandora_chapter2.xml @@ -1,61 +1,50 @@ - - Users - The definition of a user is based on the user's daily - activity. One or more profiles can be assigned to a single - user + activity. One or more profiles can be assigned to a single user - A profile is a list of actions a user can or cannot perform - on a given group, e.g. "view incidents", "database - management", etc + A profile is a list of actions a user can or cannot perform on a + given group, e.g. "view incidents", "database management", etc Each user is given a number of groups of agents he/she has - permission to access, as well as the administrative profile - he/she will have in each group. Each user can belong to one - or more groups, with an assigned profile for each of - them. + permission to access, as well as the administrative profile he/she + will have in each group. Each user can belong to one or more + groups, with an assigned profile for each of them. - Agent belongs to a group and only one, sharing the group - with agents of similar characteristics. Groups also contain - incidents. + Agent belongs to a group and only one, sharing the group with + agents of similar characteristics. Groups also contain incidents. Summarizing: User profiles in Pandora define which users can - access Pandora as well as what each user can do. Groups - define elements in common among various users. Each user - could be in one or more groups at any one time. Each group - has user profiles which are defined and attached to it. A - profile is a list of things a user can do, such as view - incidents, manage database or other. + access Pandora as well as what each user can do. Groups define + elements in common among various users. Each user could be in one + or more groups at any one time. Each group has user profiles which + are defined and attached to it. A profile is a list of things a + user can do, such as view incidents, manage database or other. Profile manager - - Pandora's profile manager is used to assign specific - profiles to each user. A hierarchy of users is so created, - structured by the user's profile within the company. With - this system different security levels can be implemented: - read-only users, agent group coordinators or system - administrators. + Pandora's profile manager is used to assign specific profiles to + each user. A hierarchy of users is so created, structured by the + user's profile within the company. With this system different + security levels can be implemented: read-only users, agent group + coordinators or system administrators. A profile is created from the Profile Manager tool in the - Administration menu. There are five predefined - profiles: + Administration menu. There are five predefined profiles: @@ -76,7 +65,7 @@ - To create a new profile click on "Manage Profiles"> + To create a new profile click on "Manage Profiles" > "Create Profile" in the Administration Menu @@ -94,8 +83,10 @@ Manage incidents (IM) - View agents (AR). To view agents as well as the events - generated by them + + View agents (AR). To view agents as well as the events + generated by them + Edit agents (AW). To modify then agent's modules @@ -107,8 +98,10 @@ Manage users (UM). To modify users and their roles - Manage DB (DM). To modify the configuration and data - of the database (Global) + + Manage DB (DM). To modify the configuration and data of the + database (Global) + Manage alerts (LM). To define new alerts (Global) @@ -149,7 +142,7 @@ A user profile is deleted by clicking on the delete icon - on the right + on the right hand side of the profile. @@ -157,8 +150,8 @@ Deleting a user - A user is deleted by clicking on the delete icon on the right hand side + A user is deleted by clicking on the delete icon on the right hand side of the user. The list of users is accessed through the "Manage Users" option in the Administration menu. @@ -173,24 +166,25 @@ user usually reflects the user's activity. - Click on "View Users">"Statistics" in the Operation + Click on "View Users" > "Statistics" in the Operation menu to show this graph: - + + - Messages to users - - 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. - - - Messages to groups - - From "Messages">"Messages to groups" section in the - Operation menu you can send messages to groups of users. - The sent messages will not be stores. - - - - \ No newline at end of file + Messages to users + + 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. + + + Messages to groups + + From "Messages" > "Messages to groups" section in the + Operation menu you can send messages to groups of users. The + sent messages will not be stores. + + + + diff --git a/pandora_doc/en/pandora_chapter4.xml b/pandora_doc/en/pandora_chapter4.xml index 50d0ff8c0b..d9bd5e1b84 100644 --- a/pandora_doc/en/pandora_chapter4.xml +++ b/pandora_doc/en/pandora_chapter4.xml @@ -1,267 +1,286 @@ - Incident management + Incident management + + + 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 + + + + 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. + + + + 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. + + + + 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. + + + - - 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 - - - - 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. - - - - 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. - - - - 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. - - - - - - The filters that can be applied are: - - - - - 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 - - - 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: - - - ID: ID of the incident. - Status: The incident status is represented by the following - icons: - - Active incident - Active incident - with comments - Rejected incident - Closed incident - Expired incident - - Incident name: Name given to the incident - Priority: The incident assigned priority is represented - by the following icons: - - - - - Very high priority - - - - High priority - - - - Medium priority - - - - Low priority - - - - Informative priority - - - - Maintenance priority - - 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 - for the last time. - 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. - 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 - by its owner, or by a user with management privileges over the group - the incidents belong to. - - Adding an incident - - The creation of incidents is performed by clicking on - "Manage Incidents" > "New incident", in the Operation menu - - - - The "Create Incident" form will come up, containing the necessary - fields to define the incident. The process is completed by clicking - on the "Create" button. - - - Incident follow up - - All the open incidents can be followed up. The tool is reached by - clicking on the "Manage Incidents" option, in the Operation menu. - - The indicent is selected by clicking on its name in the - "Incident name" column. - - The screen coming up shows us the configuration variables of - the incident, its comments and attached files. - - The first part of the screen contains the Incident configuration. - - - - From this form the following values can be updated: - - - Incident name - - - Incident owner - - - Incident status - - - Incident source - - - Group the indicent will belong to - - - Indicent priority - - - The indicent is updated by clicking on the "Update incident" button. - - Adding comments to an incident - - Comments about the incident can added clicking on "Add note". - This will open up a screen with a text box in it. - - - - - The comment is written in this box. - The Comment will appear in the "Notes attached to incident" - section after the button "Add" is pressed. - - - - - Only users with writting privilieges can add a comment, - and only the owners of the incident or of the notes can delete them. - - - - Attaching files to an incident - - Sometimes it is necessary to link an incident with an image, - a configuration file, or any kind of file. - - - The files are attached in the "Attach file" section. - Here the file can be searched for in the local machine and - attached when the "Upload" button is pressed. - - - Only a user with writing privileges can attach a file, - and only the owner of the incident or of the file can delete it. - - - - - The incident follow up screen shows all the files attached - to the incident in the "Attached files" section of the screen. - - - - - - 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 first - section of this chapter, or by making a query using the - "Manage Incidents">"Searh Incident" tool, in the Operation menu. - - - - Any text string included as a sub-string in the - incident can be searched for using this tool. This search engine looks for the - string in the Incident title as well as in the text contained by the incident. - The search engine will not search neither the Comments added to the agent nor - the attached files. The search can be performed in addition to group, priority - or status filters. - - - Statistics - - The incident statisticts are shown in the "Manage Incidents">"Statistics" - option of the Operation menu. They can be of five different types: - - - - Incident status - - - Incident priority - - - Users with the incident opened - - - Incidents by group - - - Incident source - - - - - - - + + The filters that can be applied are: + + + + + 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 + + + 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: + + + + ID: ID of the incident. + + + Status: The incident status is represented by + the following icons: + + + Active incident + Active incident + with comments + Rejected incident + Closed incident + Expired incident + + Incident name: Name given to the incident + + Priority: The incident assigned priority is + represented by the following icons: + + + + + + Very high priority + + + + High priority + + + + Medium priority + + + + Low priority + + + + Informative priority + + + + Maintenance priority + + + 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 for the last time. + + + 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. 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 by its owner, or by a + user with management privileges over the group the incidents + belong to. + + + Adding an incident + + The creation of incidents is performed by clicking on + "Manage Incidents" > "New incident", in the Operation menu + + + + + + The "Create Incident" form will come up, containing the necessary + fields to define the incident. The process is completed by clicking + on the "Create" button. + + + + Incident follow up + + + All the open incidents can be followed up. The tool is reached by + clicking on the "Manage Incidents" option, in the Operation menu. + + + + The indicent is selected by clicking on its name in the + "Incident name" column. + + + + The screen coming up shows us the configuration variables of + the incident, its comments and attached files. + + + + The first part of the screen contains the Incident configuration + + + + + From this form the following values can be updated: + + + Incident name + + + Incident owner + + + Incident status + + + Incident source + + + Group the indicent will belong to + + + Indicent priority + + + + The indicent is updated by clicking on the "Update incident" button. + + + Adding comments to an incident + Comments about the incident can added clicking on "Add note". + This will open up a screen with a text box in it. + + + The comment is written in this box. + The Comment will appear in the "Notes attached to incident" + section after the button "Add" is pressed. + + + Only users with writting privilieges can add a comment, + and only the owners of the incident or of the notes can delete them. + + + + Attaching files to an incident + Sometimes it is necessary to link an incident with an image, + a configuration file, or any kind of file. + + + The files are attached in the "Attach file" section. + Here the file can be searched for in the local machine and + attached when the "Upload" button is pressed. + + + Only a user with writing privileges can attach a file, + and only the owner of the incident or of the file can delete it. + + + The incident follow up screen shows all the files attached + to the incident in the "Attached files" section of the screen. + + + + + 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 first + section of this chapter, or by making a query using the "Manage + Incidents">"Searh Incident" tool, in the Operation menu. + + + + Any text string included as a sub-string in the incident can be + searched for using this tool. This search engine looks for the + string in the Incident title as well as in the text contained by + the incident. The search engine will not search neither the + Comments added to the agent nor the attached files. The search + can be performed in addition to group, priority or status + filters. + + + + Statistics + + The incident statisticts are shown in the "Manage + Incidents">"Statistics" option of the Operation menu. They + can be of five different types: + + + + Incident status + + + Incident priority + + + Users with the incident opened + + + Incidents by group + + + Incident source + + + + + + \ No newline at end of file diff --git a/pandora_doc/en/pandora_chapter5.xml b/pandora_doc/en/pandora_chapter5.xml index 904adf3258..f20e636057 100644 --- a/pandora_doc/en/pandora_chapter5.xml +++ b/pandora_doc/en/pandora_chapter5.xml @@ -2,66 +2,107 @@ Events + + An event in Pandora is any unusual change happend in an + agent. + + + An event is registered when an agent is down or starts up, + when a monitor fails or changes its status, or when an alarm + is sent. + - An event in Pandora is any unusual change happend in an agent. + + An event is usually preceded by an issue with the system + being monitored. A validation and deletion system has been + created to avoid leaving unanalised issues, so they can be + easily validated or deleted if the problem can be ignored or + it's been already solved. + - An event is registered when an agent is down or starts up, when a - monitor fails or changes its status, or when an alarm is sent. - - An event is usually preceded by an issue with - the system being monitored. A validation and deletion system has been created - to avoid leaving unanalised issues, so they can be easily validated or deleted - if the problem can be ignored or it's been already solved. - - The events appear ordered chronologically as they enter the system, - and can be viewed by clicking the "View Events" option in the Operation menu. - The newer events are placed at the top of the table. + + The events appear ordered chronologically as they enter the + system, and can be viewed by clicking the "View Events" + option in the Operation menu. The newer events are placed + at the top of the table. + - The event information list shows the data in the following columns: + + The event information list shows the data in the following + columns: - Status: The event status is represented by the icon below: - 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. - + + Status: The event status is represented + by the icon below: + + 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 - 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. + + 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. + - Statistics - - Three different kinds of graphical statistic representation can be - choosen from the "View Events">"Statistics" option in the Operation - menu: - - - - Total number of events divided by revised and not revised - - - - - Total events divided by the users who validated the events - - - - - Total events divided by the group the agent raising the event belongs to - - - - + Statistics + + + Three different kinds of graphical statistic + representation can be choosen from the "View + Events">"Statistics" option in the Operation menu: + + + + + + Total number of events divided by revised and not + revised + + + + + + Total events divided by the users who validated the + events + + + + + + Total events divided by the group the agent raising + the event belongs to + + + + \ No newline at end of file diff --git a/pandora_doc/en/pandora_chapter6.xml b/pandora_doc/en/pandora_chapter6.xml index bebe03e0ec..866f4be7b2 100644 --- a/pandora_doc/en/pandora_chapter6.xml +++ b/pandora_doc/en/pandora_chapter6.xml @@ -1,40 +1,63 @@ - System audit - - The Pandora's system audit shows all the actions performed by each user, as well as the failed logins. - - 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 audit Logs can be found in the System Audit option of the Administration menu, ordered chronologicly. - - Filters can be applied to the Logs displayed to show only those of interest for the user, selected by the action the Log produces. - - The selectable actions are those actions stored in the Data Base at that time. - - - - 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 - - - Statistics - - 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 - number of entries in the audit log for each one: the more active the user is the higher the number of entries. - - The graph will also show entries of invalid users, i.e., those entries generated by failed attemps to log in. - - - + System audit + + + The Pandora's system audit shows all the actions performed by each + user, as well as the failed logins. + + + + 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 audit Logs can be found in the System Audit option of the + Administration menu, ordered chronologicly. + + + + Filters can be applied to the Logs displayed to show only those of + interest for the user, selected by the action the Log produces. + + + + The selectable actions are those actions stored in the Data Base + at that time. + + + + + 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 + + + Statistics + + + 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 number of entries in the audit log for + each one: the more active the user is the higher the number of + entries. + + + + The graph will also show entries of invalid users, i.e., those + entries generated by failed attemps to log in. + + + + \ No newline at end of file diff --git a/pandora_doc/en/pandora_chapter7.xml b/pandora_doc/en/pandora_chapter7.xml index c6a7af93c9..b5c313e9bd 100644 --- a/pandora_doc/en/pandora_chapter7.xml +++ b/pandora_doc/en/pandora_chapter7.xml @@ -1,16 +1,12 @@ - - 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 "Pandora Servers" in the Operation menu you can see a list - of the 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 "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/en/pandora_chapter8.xml b/pandora_doc/en/pandora_chapter8.xml index 9cc0e847cb..a3cba29708 100644 --- a/pandora_doc/en/pandora_chapter8.xml +++ b/pandora_doc/en/pandora_chapter8.xml @@ -1,224 +1,226 @@ - Database Maintenance + Database Maintenance + + + The core of Pandora's system is its Database. All the data + collected by the monitored machines is stored in this data base, + from the administrator's data, to the events, incidents and audit + data generated in the system at any time. + - - The core of Pandora's system is its Database. All the data - collected by the monitored machines is stored in this data base, - from the administrator's data, to the events, incidents and audit - data generated in the system at any time. - - - - It is obvious that the efficiency and reliability of this - module is vital for the correct functioning of Pandora. - A regular data base maintainance is needed. To do so the data base - managers can use standard MySQL commands. Maintaining Pandora database - in good condition is critital for Pandora to work properly. - - - 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. - - - - 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. - - - - - DB Information - - 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: - - - - - Number of modules configured for each of the agents. - - - 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. - - - - - - - - These graphs can be also viewed from - "View Agents">"Statistics" in the Operation menu. - - - Manual purge of the Datadase - - 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. - - - Agent's data purge - - Debuging selected data from a module - - - The option of purging selected data from a module is used - to eliminate those out of range entries, whatever the reason - - agent failure, out of range values, testing, DB errors, etc. - Eliminating erroneous, incorrect or unnecessary data makes - the graphical representation more acuarate and shows the data - without peaks or unreal scales. - - - - 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. - - - - - The purge settings are: agent, module, minimum and maximum - data range. Any parameter out of this minimum/maximum range - will be deleted. - - - For example, in a module registering the number of processes, - if we are only interested in values between 0 and 100, any values - above that number will be usually produced by errors, noise - or abnormal circumstances. If we set to range between 0 and 100 - all those values below and above - such as -1, 100 or 100000 - - will be permanently deleted from the database. - - - - Purging all the agent's data - - - All the out of range data received by an agent can be deleted - from the "DB Maintainance">"Database Purge" option in the - Administration menu. - - - - The data is deleted by the following parameters from - the "Delete data" screen: - - - - - Purge all data - - - Purge data over 90 days - - - Purge data over 30 days - - - Purge data over 14 days - - - Purge data over 7 days - - - Purge data over 3 days - - - Purge data over 1 day - - - - - - - - Purging system data - - Audit data purge - - - All the audit data generated by the system can be deleted from - "DB Maintenance">"Database Audit", in the Administration menu - - - - The data to be deleted is selected by setting the following - parameters in the "Delete Data" screen - - - - - Purge audit data over 90 days - - - Purge audit data over 30 days - - - Purge audit data over 14 days - - - Purge audit data over 7 days - - - Purge audit data over 3 days - - - Purge audit data over 1 day - - - Purge all audit data - - - - - - - Event data purge - - - All the event data generated by the system can be deleted from - "DB Maintenance">"Database Event", in the Administration menu - - - - The data to be deleted is selected by setting the following - parameters in the "Delete Data" screen - - - - - Purge event data over 90 days - - - Purge event data over 30 days - - - Purge event data over 14 days - - - Purge event data over 7 days - - - Purge event data over 3 days - - - Purge event data over 1 day - - - Purge all event data - - - - - - + + It is obvious that the efficiency and reliability of this + module is vital for the correct functioning of Pandora. + A regular data base maintainance is needed. To do so the data base + managers can use standard MySQL commands. Maintaining Pandora database + in good condition is critital for Pandora to work properly. + + + + 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. + + + + 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. + + + + + DB Information + + + 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: + + + + + Number of modules configured for each of the agents. + + + 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. + + + + + + + + These graphs can be also viewed from + "View Agents">"Statistics" in the Operation menu. + + + Manual purge of the Datadase + + 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. + + + Agent's data purge + + Debuging selected data from a module + + + The option of purging selected data from a module is used + to eliminate those out of range entries, whatever the reason + - agent failure, out of range values, testing, DB errors, etc. + Eliminating erroneous, incorrect or unnecessary data makes + the graphical representation more acuarate and shows the data + without peaks or unreal scales. + + + + 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. + + + + + The purge settings are: agent, module, minimum and maximum + data range. Any parameter out of this minimum/maximum range + will be deleted. + + + For example, in a module registering the number of processes, + if we are only interested in values between 0 and 100, any values + above that number will be usually produced by errors, noise + or abnormal circumstances. If we set to range between 0 and 100 + all those values below and above - such as -1, 100 or 100000 - + will be permanently deleted from the database. + + + + Purging all the agent's data + + + All the out of range data received by an agent can be deleted + from the "DB Maintainance">"Database Purge" option in the + Administration menu. + + + + The data is deleted by the following parameters from + the "Delete data" screen: + + + + + Purge all data + + + Purge data over 90 days + + + Purge data over 30 days + + + Purge data over 14 days + + + Purge data over 7 days + + + Purge data over 3 days + + + Purge data over 1 day + + + + + + + + Purging system data + + Audit data purge + + + All the audit data generated by the system can be deleted from + "DB Maintenance">"Database Audit", in the Administration menu + + + + The data to be deleted is selected by setting the following + parameters in the "Delete Data" screen + + + + + Purge audit data over 90 days + + + Purge audit data over 30 days + + + Purge audit data over 14 days + + + Purge audit data over 7 days + + + Purge audit data over 3 days + + + Purge audit data over 1 day + + + Purge all audit data + + + + + + + Event data purge + + + All the event data generated by the system can be deleted from + "DB Maintenance">"Database Event", in the Administration menu + + + + The data to be deleted is selected by setting the following + parameters in the "Delete Data" screen + + + + + Purge event data over 90 days + + + Purge event data over 30 days + + + Purge event data over 14 days + + + Purge event data over 7 days + + + Purge event data over 3 days + + + Purge event data over 1 day + + + Purge all event data + + + + + + \ No newline at end of file diff --git a/pandora_doc/en/pandora_chapter9.xml b/pandora_doc/en/pandora_chapter9.xml index 28f74752bd..200ee910cb 100644 --- a/pandora_doc/en/pandora_chapter9.xml +++ b/pandora_doc/en/pandora_chapter9.xml @@ -1,62 +1,63 @@ - Pandora Configuration - - All the configurable parameters in Pandora can be set in the - "Pandora Setup" section, in the Administration menu. - - - - 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 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 - 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 - 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 - represented graphically in large time intervals. - - - Links - - Links to different Internet or private network links can be - configured in Pandora. These could be search engines, applications or - company Intranets. - - The links configured in Pandora can be edited through the - "Pandora Setup">"Links" option in the Administration menu. - - - - A new link is created by clicking on "Create". - The link can be then edited: - - - + Pandora Configuration + + All the configurable parameters in Pandora can be set in the + "Pandora Setup" section, in the Administration menu. + + + + 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 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 + 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 + 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 + represented graphically in large time intervals. + + + Links + + Links to different Internet or private network links can be + configured in Pandora. These could be search engines, applications or + company Intranets. + + The links configured in Pandora can be edited through the + "Pandora Setup">"Links" option in the Administration menu. + + + + A new link is created by clicking on "Create". + The link can be then edited: + + + \ No newline at end of file diff --git a/pandora_doc/en/pandora_userguide.xml b/pandora_doc/en/pandora_userguide.xml index b124e4b90d..4fa7e34256 100644 --- a/pandora_doc/en/pandora_userguide.xml +++ b/pandora_doc/en/pandora_userguide.xml @@ -69,5 +69,4 @@ &include_pandora_chapter9; &include_fdl; &include_gpl; - diff --git a/pandora_doc/en/schemas.xml b/pandora_doc/en/schemas.xml index 896e2cf610..0455da351d 100644 --- a/pandora_doc/en/schemas.xml +++ b/pandora_doc/en/schemas.xml @@ -1,5 +1,6 @@ +