{"id":42237,"date":"2019-03-18T00:00:00","date_gmt":"2019-03-17T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/netxms-kak-sistema-monitoringa-dlya-lenivyh-i-nemnogo-sravneniya-s-zabbix"},"modified":"2020-02-18T13:45:04","modified_gmt":"2020-02-18T10:45:04","slug":"netxms-kak-sistema-monitoringa-dlya-lenivyh-i-nemnogo-sravneniya-s-zabbix","status":"publish","type":"post","link":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/netxms-kak-sistema-monitoringa-dlya-lenivyh-i-nemnogo-sravneniya-s-zabbix","title":{"rendered":"NetXMS jako monitorovac\u00ed syst\u00e9m pro lenochy\u2026 a trochu srovn\u00e1n\u00ed se Zabbixem","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

\"NetXMS
\n<\/p>\n

0. \u00davod<\/h3>\n

\nNa Habr\u00e9 jsem nena\u0161el \u017e\u00e1dn\u00fd \u010dl\u00e1nek o NetXMS, i kdy\u017e jsem hledal. A pr\u00e1v\u011b z tohoto d\u016fvodu jsem se rozhodl napsat toto d\u00edlo, abych v\u011bnoval pozornost tomuto syst\u00e9mu.<\/p>\n

Je to jak tutori\u00e1l, tak n\u00e1vod a povrchov\u00fd p\u0159ehled mo\u017enost\u00ed syst\u00e9mu.<\/p>\n

Tento \u010dl\u00e1nek obsahuje povrchovou anal\u00fdzu a popis mo\u017enost\u00ed syst\u00e9mu. Do hloubky jsem se do mo\u017enost\u00ed nezat\u00e1p\u011bl z n\u011bkolika d\u016fvod\u016f. A pops\u00e1n\u00ed ve\u0161ker\u00e9 funk\u010dnosti by zabralo rozhodn\u011b v\u00edce ne\u017e jeden \u010dl\u00e1nek.<\/p>\n

Jeliko\u017e jsem v\u00edce m\u00e9n\u011b pracoval jen se Zabbixem, v \u010dl\u00e1nku bude tato syst\u00e9m \u010dasto zmi\u0148ov\u00e1n pro srovn\u00e1n\u00ed s t\u00e9matem. Nav\u00edc se tak n\u011bjak ust\u00e1lilo, \u017ee se v\u0161echno porovn\u00e1v\u00e1 s n\u011b\u010d\u00edm b\u011b\u017en\u011b uzn\u00e1van\u00fdm.<\/p>\n

1. Co a pro\u010d?<\/h3>\n

\nMonitorovac\u00ed syst\u00e9m, jak je vid\u011bt z definice, je syst\u00e9m, kter\u00fd umo\u017e\u0148uje kdykoli z\u00edskat aktu\u00e1ln\u00ed informace o n\u011bjak\u00e9m uzlu s\u00ed\u0165ov\u00e9m za\u0159\u00edzen\u00edm routerem nebo napsat pot\u0159ebn\u00e9.<\/p>\n

Pro\u010d je to pot\u0159eba \u2013 to je tak\u00e9 o\u010dividn\u00e9. Abychom byli informov\u00e1ni o tom, co se d\u011bje.<\/p>\n

\u010casto m\u016f\u017ee monitorovac\u00ed syst\u00e9m poskytnout velmi vy\u010derp\u00e1vaj\u00edc\u00ed informace o stavu jak infrastruktury jako celku, tak jednotliv\u00fdch jej\u00edch \u010d\u00e1st\u00ed. Nav\u00edc, pokud nastav\u00edte upozorn\u011bn\u00ed (a bez toho nem\u00e1 \u017e\u00e1dn\u00fd monitoring cenu), pak m\u00e1me na v\u00fdstupu v\u00e1\u017en\u00fd n\u00e1stroj, kter\u00fd n\u00e1m umo\u017e\u0148uje nejen v\u010das reagovat na ji\u017e vznikl\u00e9 havarijn\u00ed situace, ale v mnoha p\u0159\u00edpadech tak\u00e9 tyto hav\u00e1rie p\u0159edej\u00edt.
\n<\/a><\/noindex><\/p>\n

2. Pro\u010d NetXMS?<\/h3>\n

\nTrochu offtopic pro ty, kdo maj\u00ed r\u00e1di hodn\u011b p\u00edsemn\u00e9ho obsahu.<\/b>Kdy\u017e jsem byl mlad\u00fd a nezku\u0161en\u00fd... Tak obvykle za\u010d\u00ednaj\u00ed v\u0161echny poh\u00e1dky?.. Kdy\u017e jsem byl maximalista, studoval jsem ot\u00e1zku monitorov\u00e1n\u00ed infrastruktury a v\u00fdsledkem t\u011bchto \"v\u00fdzkum\u016f\" bylo zji\u0161t\u011bn\u00ed, \u017ee lep\u0161\u00ed ne\u017e Zabbix nic nen\u00ed. A v t\u00e9 dob\u011b se mi skute\u010dn\u011b l\u00edbil, proto\u017ee um\u00ed hodn\u011b, m\u016f\u017ee mnoho a jeho funkce lze roz\u0161\u00ed\u0159it vlastn\u00edm skripty, tak\u017ee se d\u00e1 \u0159\u00edct, \u017ee m\u016f\u017ee vlastn\u011b v\u0161echno, kdy\u017e m\u00e1te spr\u00e1vn\u00e9 ruce. Ale Zabbix je pom\u011brn\u011b slo\u017eit\u00fd n\u00e1stroj. Abych se s n\u00edm v\u00edce \u010di m\u00e9n\u011b vyznal, trvalo mi to t\u00e9m\u011b\u0159 dva t\u00fddny. A to byla jen f\u00e1ze zaveden\u00ed. Pot\u00e9 jsem str\u00e1vil dal\u0161\u00ed p\u00e1r t\u00fddn\u016f nastavov\u00e1n\u00edm monitorov\u00e1n\u00ed v\u0161eho, co jsem tehdy pot\u0159eboval. A jak s jeho pomoc\u00ed sledovat stav port\u016f na routerech, to jsem si p\u0159e\u010detl, vyd\u011bsil jsem se a rozhodl se, \u017ee to vlastn\u011b ani moc nepot\u0159ebuji... Ne, tam je to opravdu d\u011bsiv\u00e9 pro nep\u0159ipravenou mysl hned po institutu...<\/p>\n

A tak po n\u011bkolika letech, kdy\u017e jsem vyzr\u00e1l a zest\u00e1rl, jsem se rozhodl, \u017ee nastal \u010das osv\u011b\u017eit si znalosti o monitorovac\u00edch syst\u00e9mech. A kone\u010dn\u011b ud\u011blat norm\u00e1ln\u00ed, stabiln\u00ed monitorov\u00e1n\u00ed s\u00edt\u011b, proto\u017ee tento probl\u00e9m se stal aktu\u00e1ln\u00edm v souvislosti s r\u016fstem segment\u016f, p\u0159ipojen\u00edm pobo\u010dky a dal\u0161\u00edmi drobnostmi. V\u0161echno te\u010de, v\u0161echno se m\u011bn\u00ed. A za\u010dal jsem testovat r\u016fzn\u00e9 n\u00e1stroje. Nainstaloval jsem tento syst\u00e9m, vyzkou\u0161el ho, pak ten. A ve v\u0161ech n\u011b\u010deho chyb\u011blo, v\u0161ude n\u011bco nevyhovovalo. Bu\u010f rozhran\u00ed bylo nepohodln\u00e9, nebo se to nedalo nastavit bez pr\u00e1ce, nebo je\u0161t\u011b n\u011bco. A pak mi padl do oka NetXMS. Mimochodem: tam, kde jsem se s Zabbixem vyzn\u00e1val dva t\u00fddny, s NetXMS to \u0161lo b\u011bhem p\u00e1r hodin. Mo\u017en\u00e1 to byla zku\u0161enost s prac\u00ed se Zabbixem, nebo mo\u017en\u00e1 za to mohl samotn\u00fd NetXMS... t\u011b\u017eko \u0159\u00edct.<\/p>\n

NetXMS se uk\u00e1zala jako pom\u011brn\u011b jednoduch\u00fd syst\u00e9m k instalaci a nastaven\u00ed. M\u00e1 verze serveru a administra\u010dn\u00ed konzole jak pro Windows, tak pro Linux, gener\u00e1tory graf\u016f, vestav\u011bn\u00fd \"prohl\u00ed\u017ee\u010d\", kter\u00fd umo\u017e\u0148uje, aby se z administr\u00e1torsk\u00e9 konzole p\u0159ipojil k t\u011bm sam\u00fdm router\u016fm pomoc\u00ed http\/https protokol\u016f, a rozhran\u00ed je intuitivn\u011b srozumiteln\u00e9, a tak\u00e9 agent pro jak\u00fdkoliv opera\u010dn\u00ed syst\u00e9m. Jin\u00fdmi slovy, tento syst\u00e9m se uk\u00e1zal jako jednoduch\u00fd a pohodln\u00fd. Na prvn\u00ed pohled.<\/p>\n

Dokumentace je, mimochodem, na 8 z 10. Hlavn\u00ed v\u011bci jsou v n\u00ed uvedeny, ale abyste se dostali do detail\u016f, mus\u00edte trochu pohledat.<\/p>\n

Hlavn\u00ed v\u00fdhody uveden\u00e9 v\u00fdvoj\u00e1\u0159em<\/b>Hlubok\u00e9 monitorov\u00e1n\u00ed s\u00edt\u011b<\/b>
\nAutomatick\u00e9 detekce, vizualizace a vyhled\u00e1v\u00e1n\u00ed p\u0159ipojen\u00fdch komponent na \u00farovni 2 a 3
\nPln\u00e1 podpora SNMPv3
\nAktivn\u00ed detekce pomoc\u00ed skenovac\u00edch \u201esond\u201c
\nPasivn\u00ed detekce na z\u00e1klad\u011b informac\u00ed od sledovan\u00fdch za\u0159\u00edzen\u00ed \u2014 ARP a sm\u011brovac\u00edch tabulek, rozhran\u00ed
\nMonitorov\u00e1n\u00ed aplikac\u00ed a server\u016f<\/b>
\nV\u0161echny hlavn\u00ed metriky, kter\u00e9 o\u010dek\u00e1v\u00e1te: procesor, souborov\u00e9 syst\u00e9my, vstup-v\u00fdstup, pam\u011b\u0165, provoz
\nJMX most pro monitorov\u00e1n\u00ed Java aplikac\u00ed
\nRoz\u0161\u00ed\u0159en\u00ed pro konkr\u00e9tn\u00ed aplikace: Oracle, MySQL, PostgreSQL, MongoDB, DB2, Tuxedo a mnoh\u00e9 dal\u0161\u00ed
\nAPI pro integraci vlastn\u00edch aplikac\u00ed
\nUr\u010deno pro velk\u00e9 s\u00edt\u011b<\/b>
\nJeden server m\u016f\u017ee sledovat stovky metrik na tis\u00edc\u00edch za\u0159\u00edzen\u00ed
\nPln\u00e1 podpora distribuovan\u00e9ho monitorov\u00e1n\u00ed a horizont\u00e1ln\u00edho \u0161k\u00e1lov\u00e1n\u00ed
\nMonitorov\u00e1n\u00ed p\u0159ekr\u00fdvaj\u00edc\u00edch se IP pods\u00edt\u00ed
\nFlexibiln\u00ed kontrola p\u0159\u00edstupu pro oper\u00e1tory a z\u00e1kazn\u00edky<\/p>\n

3. Pono\u0159\u00edme se hloub\u011bji<\/h3>\n

\nJak nainstalovat syst\u00e9m \u2014 existuje cel\u00fd n\u00e1vod<\/a><\/noindex> administr\u00e1tora, dostupn\u00fd na webov\u00fdch str\u00e1nk\u00e1ch v\u00fdvoj\u00e1\u0159e<\/a><\/noindex>, a nen\u00ed na tom nic slo\u017eit\u00e9ho, tak\u017ee se na tom d\u00e1le nezastav\u00edm. Nejt\u011b\u017e\u0161\u00ed na instalaci je p\u0159ipojen\u00ed syst\u00e9mu k datab\u00e1zi\u2026 Zde bude rozd\u00edl pouze ve v\u00fdb\u011bru DBMS a opera\u010dn\u00edho syst\u00e9mu serveru. Zvolil jsem Windows (d\u00e1le-d\u00e1le-zadat \u00fadaje-hotovo) a MSSQL, proto\u017ee jsem ho ji\u017e m\u011bl.<\/p>\n

3.1. Aktivujeme automatick\u00e9 objevov\u00e1n\u00ed<\/h3>\n

\nAutomatick\u00e9 objevov\u00e1n\u00ed uzl\u016f s\u00edt\u011b lze zapnout p\u0159i instalaci. Pokud to z n\u011bjak\u00e9ho d\u016fvodu nebylo provedeno, lze ho v\u017edy zapnout v \u201eConfiguration-Network Discovery\u201c<\/i> nebo kliknut\u00edm na ikonu se stejn\u00fdm n\u00e1zvem. V pracovn\u00edm prostoru se objev\u00ed vlastnosti objevov\u00e1n\u00ed. Je t\u0159eba ho zapnout p\u0159epnut\u00edm do pasivn\u00edho nebo aktivn\u00edho re\u017eimu a ozna\u010dit dal\u0161\u00ed vlastnosti, jako jsou dotazovan\u00e9 pods\u00edt\u011b. Tak\u00e9 zde lze nastavit filtry, a to jak voleb, tak i dolad\u011bn\u00ed vestav\u011bn\u00fdch v syst\u00e9mu, ale i naps\u00e1n\u00ed vlastn\u00edch skript\u016f. Up\u0159\u00edmn\u011b \u0159eknu \u2014 filtry jsem nepot\u0159eboval. Ale nastaven\u00ed vypad\u00e1 docela p\u0159\u00e1telsky a srozumiteln\u011b.<\/p>\n

Zde lze tak\u00e9 uv\u00e9st v\u00fdchoz\u00ed SNMP community a jeho p\u0159ihla\u0161ovac\u00ed \u00fadaje (\u010dti autorizaci).<\/p>\n

3.2. P\u0159id\u00e1v\u00e1n\u00ed uzl\u016f<\/h3>\n

\nP\u0159i zapnut\u00e9m automatick\u00e9m detekov\u00e1n\u00ed budou koncov\u00e9 uzly (PC, tisk\u00e1rny) automaticky p\u0159id\u00e1ny a rozd\u011bleny do pods\u00edt\u00ed. S aktivn\u00edm s\u00ed\u0165ov\u00fdm za\u0159\u00edzen\u00edm je to o n\u011bco slo\u017eit\u011bj\u0161\u00ed.<\/p>\n

Nejprve je pot\u0159eba zapnout na s\u00ed\u0165ov\u00e9m za\u0159\u00edzen\u00ed SNMP a nastavit komunitu. Pokud ve vlastnostech automatick\u00e9ho objevov\u00e1n\u00ed uzl\u016f s\u00edt\u011b nebyla zm\u011bn\u011bna v\u00fdchoz\u00ed hodnota pro SNMP komunitu, syst\u00e9m pou\u017e\u00edv\u00e1 ve\u0159ejnou komunitu, p\u0159i\u010dem\u017e toto nastaven\u00ed lze zm\u011bnit pro ka\u017ed\u00fd uzel ve vlastnostech p\u0159idan\u00e9ho uzlu (node).<\/p>\n

Pro pohodl\u00ed lze za\u0159\u00edzen\u00ed seskupit podle jak\u00e9hokoli vhodn\u00e9ho principu, k tomu je mo\u017en\u00e9 ve strom\u011b vytv\u00e1\u0159et kontejnery ve v\u011btvi Slu\u017eby infrastruktury a p\u0159i\u0159azovat k nim uzly z Celkov\u00e9 s\u00edt\u011b.<\/p>\n

Po zapnut\u00ed a nastaven\u00ed SNMP na sm\u011brova\u010d\u00edch a p\u0159id\u00e1n\u00ed do seznamu sledovan\u00fdch za\u0159\u00edzen\u00ed se syst\u00e9m s nimi s\u00e1m spoj\u00ed, zjist\u00ed, o jak\u00e9 za\u0159\u00edzen\u00ed se jedn\u00e1, aplikuje \u0161ablony, za\u010dne sb\u011br dat a zobraz\u00ed p\u0159edn\u00ed panel pro ka\u017ed\u00fd sm\u011brova\u010d. S\u00e1m. Z krabice. Kdy\u017e jsem nastavoval Zabbix, mohl jsem o n\u011b\u010dem takov\u00e9m jen sn\u00edt.<\/p>\n

\"NetXMS
\n
\nV\u0161echna sv\u00e1 s\u00ed\u0165ov\u00e1 za\u0159\u00edzen\u00ed jsem p\u0159id\u00e1val ru\u010dn\u011b, proto\u017ee se pro n\u011bjak\u00fd d\u016fvod sama neobjevila. Tady je to jednoduch\u00e9. Vytvo\u0159\u00edme kontejner v Slu\u017eb\u00e1ch infrastruktury s libovoln\u00fdm vhodn\u00fdm n\u00e1zvem (nap\u0159\u00edklad switche), a PKM-vytvo\u0159it-uzel<\/i>, uv\u00e9st zobrazen\u00e9 jm\u00e9no uzlu, jeho IP adresu a je lep\u0161\u00ed za\u0161krtnout \"vypnout pou\u017e\u00edv\u00e1n\u00ed agenta NetXMS\", proto\u017ee jej stejn\u011b nen\u00ed mo\u017en\u00e9 nainstalovat na s\u00ed\u0165ov\u00e9 za\u0159\u00edzen\u00ed a zbyte\u010dn\u00e9 bal\u00ed\u010dky nejsou pot\u0159eba.<\/p>\n

Vestav\u011bn\u00fd prohl\u00ed\u017ee\u010d. M\u016f\u017eete jednodu\u0161e kliknout prav\u00fdm tla\u010d\u00edtkem my\u0161i na pot\u0159ebn\u00fd sm\u011brova\u010d a otev\u0159\u00edt webov\u00e9 rozhran\u00ed za\u0159\u00edzen\u00ed. To mi p\u0159ipadalo pohodln\u011bj\u0161\u00ed, ne\u017e ka\u017ed\u00fd \u010das hledat svou pozn\u00e1mku a hledat pot\u0159ebnou IP. Pravda, prohl\u00ed\u017ee\u010d nen\u00ed nic moc.<\/p>\n

3.3. Vytvo\u0159en\u00ed mapy s\u00edt\u011b<\/h3>\n

\nNejprve je pot\u0159eba vytvo\u0159it mapu s\u00edt\u011b jako objekt. Jak obvykle - ve v\u011btvi Mapa s\u00edt\u00ed prav\u00fdm tla\u010d\u00edtkem my\u0161i, vytvo\u0159it, vybrat typ mapy, nastavit parametry<\/i>, a syst\u00e9m to pak ud\u011bl\u00e1 s\u00e1m.<\/p>\n

Typy map jsou n\u00e1sleduj\u00edc\u00ed:<\/p>\n

    \n
  1. Vlastn\u00ed<\/b>. Toto je mapa ur\u010den\u00e1 k manu\u00e1ln\u00edmu vytvo\u0159en\u00ed, podle p\u0159\u00e1n\u00ed u\u017eivatele.<\/li>\n
  2. Topologie vrstvy 2<\/b>. Toto je mapa, kter\u00e1 umo\u017e\u0148uje automaticky ud\u011blat v\u0161e za u\u017eivatele, op\u00edraj\u00edc\u00ed se o 2. \u00farove\u0148 modelu OSI (v podstat\u011b vytv\u00e1\u0159\u00ed mapu na z\u00e1klad\u011b mac adres za\u0159\u00edzen\u00ed). <\/li>\n
  3. Topologie IP<\/b>, tak\u00e9 vrstva 3<\/b>. To sam\u00e9, co v p\u0159\u00edpad\u011b vrstvy 2<\/b>, pouze mapa se vytv\u00e1\u0159\u00ed na z\u00e1klad\u011b 3. \u00farovn\u011b modelu OSI (IP adresy).<\/li>\n<\/ol>\n

    \nP\u0159i v\u00fdb\u011bru ru\u010dn\u00edho sestavov\u00e1n\u00ed mapy je pot\u0159eba p\u0159etahovat uzly ze stromu na mapovou vrstvu, spojovat je atd. Obvykl\u00e9 kreslen\u00ed. <\/p>\n

    Ve dvou jin\u00fdch p\u0159\u00edpadech je t\u0159eba vybrat referen\u010dn\u00ed bod, od kter\u00e9ho syst\u00e9m za\u010dne mapu vytv\u00e1\u0159et. Nap\u0159\u00edklad uzel n\u011bjak\u00e9ho sm\u011brova\u010de. Syst\u00e9m \u010dte z n\u011bj data o p\u0159ipojen\u00fdch za\u0159\u00edzen\u00edch a portech, ke kter\u00fdm jsou p\u0159ipojena, pot\u00e9 \u010dte data z n\u00e1sleduj\u00edc\u00edho sm\u011brova\u010de, porovn\u00e1v\u00e1 to a tak d\u00e1le. Po anal\u00fdze v\u0161ech za\u0159\u00edzen\u00ed syst\u00e9m NetXMS s\u00e1m vykresl\u00ed vazby mezi za\u0159\u00edzen\u00edmi s\u00edt\u011b s uveden\u00edm port\u016f, kam co je p\u0159ipojeno. Lze tak\u00e9 ur\u010dit, aby syst\u00e9m um\u00edstil na mapu i koncov\u00e1 za\u0159\u00edzen\u00ed (tisk\u00e1rny, PC, servery), jednodu\u0161e kliknut\u00edm na p\u0159\u00edslu\u0161nou polo\u017eku v vlastnostech mapy.PKM \u2014 vlastnosti \u2014 vlastnosti mapy.<\/i>Tak\u00e9 v t\u00e9to polo\u017ece lze p\u0159i p\u0159\u00e1n\u00ed nebo pot\u0159eb\u011b nastavit \u00abpolom\u011br detekce\u00bb.<\/p>\n

    Mal\u00e1 doporu\u010den\u00ed. Zapn\u011bte vlastnost Always fit layout to screen, aby p\u0159i ka\u017ed\u00e9 aktualizaci mapy s\u00edt\u011b nebylo t\u0159eba posouvat pracovn\u00ed prostor a pracovat se zoomem.<\/p>\n

    \"NetXMS
    \n
    \nP\u0159i distribuovan\u00e9 topologii s\u00edt\u011b je mo\u017en\u00e9 um\u00edstit objekty na mapu ter\u00e9nu. Tak\u00e9 lze jako pozad\u00ed pou\u017e\u00edt nap\u0159\u00edklad fotografii racku s vybaven\u00edm v serverovn\u011b a na n\u011bj p\u0159ekr\u00fdt pot\u0159ebn\u00e9 objekty. T\u00edmto zp\u016fsobem lze rychle ur\u010dit stav jak\u00e9hokoli za\u0159\u00edzen\u00ed v racku. Podle m\u00e9ho n\u00e1zoru je to velmi u\u017eite\u010dn\u00e1 v\u011bc v p\u0159\u00edpad\u011b pot\u0159eby p\u0159edat z\u00e1le\u017eitosti n\u00e1stupci nebo nov\u00e9mu kolegovi vysv\u011btlit stav v\u011bc\u00ed. P\u0159ehledn\u00e9, pohodln\u00e9, samoz\u0159ejm\u00e9.<\/p>\n

    3.4. Agenti<\/h3>\n

    \nAgenti existuj\u00ed jak pro Windows, tak pro Linux. Princip fungov\u00e1n\u00ed je stejn\u00fd jako u agent\u016f Zabbix: nainstaluj\u00ed se na stroj, ze kter\u00e9ho je t\u0159eba z\u00edsk\u00e1vat metriky, a p\u0159en\u00e1\u0161ej\u00ed data na monitorovac\u00ed server. Agenta je mo\u017en\u00e9 nainstalovat jak p\u0159ed p\u0159id\u00e1n\u00edm uzlu do syst\u00e9mu, tak i po. Po z\u0159\u00edzen\u00ed agenta na uzlu za\u010dne syst\u00e9m po n\u011bjak\u00e9 dob\u011b p\u0159ij\u00edmat data od n\u011bj, p\u0159i\u010dem\u017e pou\u017eije standardn\u00ed \u0161ablonu. Sledovan\u00e9 parametry lze p\u0159id\u00e1vat jak pro jeden uzel, tak p\u0159ipojit k n\u011bmu jednu nebo v\u00edce p\u0159eddefinovan\u00fdch \u0161ablon. Doporu\u010duje se samoz\u0159ejm\u011b pracovat se \u0161ablonami, proto\u017ee toto nastaven\u00ed je flexibiln\u011bj\u0161\u00ed.<\/p>\n

    Seznam sledovan\u00fdch parametr\u016f pro agenty je dost rozs\u00e1hl\u00fd. Kompletn\u00ed seznam lze zobrazit v Wiki NetXMS<\/a><\/noindex><\/p>\n

    Jakmile syst\u00e9m zjist\u00ed, \u017ee agent funguje na uzlu, okam\u017eit\u011b p\u0159i\u0159ad\u00ed tento uzel k n\u011bkter\u00e9 z v\u00fdchoz\u00edch \u0161ablon \u2014 Windows, Linux, HP-UX, Generic UNIX, AIX<\/b>, podle opera\u010dn\u00edho syst\u00e9mu uzlu.<\/p>\n

    Standardn\u00ed \u0161ablona pro Windows hosty:<\/p>\n

    \"NetXMS
    \n
    \nP\u0159id\u00e1n\u00ed parametru pro sledov\u00e1n\u00ed konkr\u00e9tn\u00ed uzlu lze prov\u00e9st klepnut\u00edm na \u201ePrav\u00e9 tla\u010d\u00edtko my\u0161i - Parametr sb\u011bru dat<\/i>\u201e, d\u00e1le \u201ePrav\u00e9 tla\u010d\u00edtko v pracovn\u00edm prostoru \u2014 Nov\u00fd parametr<\/i>\u201e a vybr\u00e1n\u00edm po\u017eadovan\u00e9ho ze seznamu. Zde je mo\u017en\u00e9 tak\u00e9 nastavit spou\u0161t\u011b\u010de pro sledovan\u00fd parametr.<\/p>\n

    D\u016fle\u017eit\u00e9 je, \u017ee agenty, stejn\u011b jako u Zabbixu, um\u00ed spou\u0161t\u011bt u\u017eivatelsk\u00e9 skripty.<\/p>\n

    Jak nainstalovat?<\/b>Tohle je offtopic, proto\u017ee ka\u017ed\u00fd\u2026 hmmm\u2026 jak chce.<\/p>\n

    Ot\u00e1zka je, zda roz\u0161i\u0159ovat agenty pouze na servery nebo na v\u0161echna za\u0159\u00edzen\u00ed v s\u00edti? Pokud na servery a je jich m\u00e1lo \u2014 nejjednodu\u0161\u0161\u00ed je to ud\u011blat ru\u010dn\u011b. Pokud jich je hodn\u011b \u2014 dom\u00e9nov\u00e9 politiky, KIX, PoSh. Cokoli. Agenti maj\u00ed kl\u00ed\u010d \/SILENT, kter\u00fd umo\u017e\u0148uje \u201evysadit\u201c ho pr\u016fhledn\u011b pro u\u017eivatele (pokud mluv\u00edme o roz\u0161\u00ed\u0159en\u00ed na v\u0161echna za\u0159\u00edzen\u00ed v s\u00edti). Up\u0159ednost\u0148uji skripty, proto\u017ee lze nastavit podm\u00ednku a vytvo\u0159it jak\u00fdsi flag, na rozd\u00edl od politik, kter\u00e9 instaluj\u00ed program poka\u017ed\u00e9, kdy\u017e se PC zapne. Tak\u017ee nap\u00ed\u0161eme skript v s\u00e9rii \u201ezkontrolovat existenci souboru-flag, pokud ne \u2014 spustit instal\u00e1tor s kl\u00ed\u010dem \/SILENT a po \u00fasp\u011b\u0161n\u00e9 instalaci vytvo\u0159it soubor-flag\u201c. Zisk.<\/p>\n

    3.5. Spou\u0161t\u011b\u010de<\/h3>\n

    \nSpou\u0161t\u011b\u010de lze nastavit na reakci na ur\u010dit\u00e9 ud\u00e1losti v shrom\u00e1\u017ed\u011bn\u00fdch datech. Nap\u0159\u00edklad p\u0159ekro\u010den\u00ed ur\u010dit\u00e9 hodnoty ping-pong k routeru. Zp\u016fsob upozorn\u011bn\u00ed pro ka\u017ed\u00fd spou\u0161t\u011b\u010d se tak\u00e9 nastavuje (pro n\u011bkter\u00e9 sta\u010d\u00ed ikona v konzoli, jin\u00e9 okam\u017eit\u011b pos\u00edlaj\u00ed upozorn\u011bn\u00ed kamkoli). Reakce na ud\u00e1lost se vyb\u00edr\u00e1 z p\u0159ednastaven\u00fdch v konfiguraci akce.<\/p>\n

    Pro vytvo\u0159en\u00ed spou\u0161t\u011b\u010de: p\u0159ej\u00edt do konfigurace sb\u011bru dat uzlu nebo \u0161ablony, dvojit\u00fdm kliknut\u00edm na zaj\u00edmav\u00fd parametr (jestli\u017ee neexistuje, je t\u0159eba ho nejprve vytvo\u0159it), a v jeho vlastnostech p\u0159ej\u00edt na kartu Prahy, kliknout na tla\u010d\u00edtko p\u0159idat.<\/i><\/p>\n

    \"NetXMS
    \n
    \n\u201eFunkce<\/b>\u201e \u2014 jakou nebo jak\u00e9 hodnoty br\u00e1t pro v\u00fdpo\u010det podm\u00ednek. M\u016f\u017ee nab\u00fdvat n\u00e1sleduj\u00edc\u00ed hodnoty (po\u010det pou\u017e\u00edvan\u00fdch pro kontrolu hodnot je uveden v poli Samples):
    \n \u2014 Posledn\u00ed hodnoty: posledn\u00ed\/posledn\u00ed z\u00edskan\u00e1 hodnota\/hodnoty
    \n \u2014 Pr\u016fm\u011brn\u00e1 hodnota: pr\u016fm\u011brn\u00e1 hodnota z posledn\u00edch
    \n \u2014 Pr\u016fm\u011brn\u00e9 odchylky: pr\u016fm\u011brn\u00e9 odchylky
    \n \u2014 Rozd\u00edl od p\u0159edchoz\u00ed hodnoty: rozd\u00edl od p\u0159edchoz\u00ed hodnoty
    \n \u2014 Chyba p\u0159i shroma\u017e\u010fov\u00e1n\u00ed dat: chyba p\u0159i z\u00edsk\u00e1v\u00e1n\u00ed dat
    \n \u2014 Sou\u010det hodnot: sou\u010det hodnot
    \n \u2014 Skript: hodnota z\u00edskan\u00e1 v d\u016fsledku pr\u00e1ce u\u017eivatelsk\u00e9ho skriptu<\/p>\n

    \u201eOperace<\/b>\u201e \u2014 podm\u00ednka, kter\u00e1 spou\u0161t\u00ed spou\u0161t\u011b\u010d. M\u016f\u017ee p\u0159ij\u00edmat hodnoty (hodnota je uvedena v odpov\u00eddaj\u00edc\u00edm poli Value):
    \n \u2014 <: men\u0161\u00ed ne\u017e: men\u0161\u00ed ne\u017e
    \n \u2014 <=: men\u0161\u00ed nebo rovno: men\u0161\u00ed nebo rovno
    \n \u2014 == rovn\u00e1 se: rovno
    \n \u2014 >=: v\u011bt\u0161\u00ed nebo rovno: v\u011bt\u0161\u00ed nebo rovno
    \n \u2014 >: v\u011bt\u0161\u00ed ne\u017e: v\u011bt\u0161\u00ed ne\u017e
    \n \u2014 !=: nen\u00ed rovno: nen\u00ed rovno
    \n \u2014 like: p\u0159ibl\u00ed\u017eeno k
    \n \u2014 not like: nep\u0159ibl\u00ed\u017eeno k
    \nCo se t\u00fd\u010de dvou posledn\u00edch parametr\u016f, nejsem si jist\u00fd, jak funguj\u00ed. Proto ani nebudu h\u00e1dat, jak\u00e9 hranice v nich jsou zapu\u0161t\u011bny.<\/p>\n

    Jednodu\u0161e \u0159e\u010deno, v\u0161echno jako v Zabbixu, jen nen\u00ed t\u0159eba ru\u010dn\u011b zapisovat vzorce, b\u00e1t se chyby nebo p\u0159eklepu. Pro obnoven\u00ed spou\u0161t\u011b\u010de (deactivation event) syst\u00e9m automaticky vlo\u017e\u00ed hodnotu. (V Zabbixu zase je t\u0159eba ps\u00e1t a neopakovat se).<\/p>\n

    3.6. \u0160ablony<\/h3>\n

    \nPrav\u00fdm tla\u010d\u00edtkem my\u0161i - vytvo\u0159it \u0161ablonu, zadat n\u00e1zev \u0161ablony. Prav\u00fdm tla\u010d\u00edtkem my\u0161i - Konfigurace shroma\u017e\u010fov\u00e1n\u00ed dat.<\/i><\/p>\n

    Trochu teorie<\/b>Shroma\u017e\u010fovan\u00e9 informace mohou poch\u00e1zet z n\u011bkolika zdroj\u016f. M\u016f\u017ee to b\u00fdt agent NetXMS<\/b>, pracuj\u00edc\u00ed na stroji, m\u016f\u017ee b\u00fdt \u201ejednoduch\u00fd dotaz<\/b>\u201e nebo \u201eIntern\u00ed<\/b>\u201e, pos\u00edlan\u00fd samotn\u00fdm serverem (nap\u0159\u00edklad stejn\u00fd ping), \u201eSNMP<\/b>\u201e, \u201ekontroln\u00ed bod SNMP<\/b>\u201e, \u201ePush<\/b>\u201e, \u201eWindows Performance Counters<\/b>\u201e, \u201eSM-CLP<\/b>\u201e, nebo u\u017eivatelsky definovan\u00fd \u201eskript<\/b>\u201e. U ka\u017ed\u00e9ho typu informace lze vybrat typ, kter\u00fd syst\u00e9m o\u010dek\u00e1v\u00e1 p\u0159i p\u0159\u00edjmu. Nap\u0159\u00edklad ping vr\u00e1t\u00ed cel\u00e9 \u010d\u00edslo (integer), mno\u017estv\u00ed voln\u00e9ho m\u00edsta na disku v bajtech bude tak\u00e9 whole number, zat\u00edmco teplota u\u017e bude necel\u00e9 \u010d\u00edslo, tedy real).<\/p>\n

    Pro shroma\u017e\u010fov\u00e1n\u00ed informac\u00ed p\u0159es SNMP m\u00e1 NetXMS obrovsk\u00fd seznam p\u0159eddefinovan\u00fdch parametr\u016f, to znamen\u00e1, \u017ee nen\u00ed t\u0159eba uv\u00e1d\u011bt konkr\u00e9tn\u00ed OID, ale lze jej naj\u00edt ve stromu MIB, co\u017e je ve skute\u010dnosti dost problematick\u00e9\u2026 Ale. Nakonec mus\u00edte zkoumat dokumentaci v\u00fdrobce a hledat IOD hodnoty pro ka\u017ed\u00e9 za\u0159\u00edzen\u00ed samostatn\u011b. M\u016f\u017eete str\u00e1vit spoustu \u010dasu nastaven\u00edm \u010dten\u00ed informac\u00ed z za\u0159\u00edzen\u00ed, nar\u00e1\u017eej\u00edc na hl\u00e1\u0161en\u00ed syst\u00e9mu \u201eUNSUPPORTED\u201c<\/i>, a nakonec se uk\u00e1\u017ee, \u017ee toto konkr\u00e9tn\u00ed za\u0159\u00edzen\u00ed prost\u011b neum\u00ed poskytnout po\u017eadovan\u00e9 informace. Zb\u00fdv\u00e1 jen pro\u010d\u00edst manu\u00e1ly a doufat.<\/p>\n

    Nap\u0159\u00edklad pro shroma\u017e\u010fov\u00e1n\u00ed informac\u00ed o \u010dase odezvy uzlu (ping) je pot\u0159eba p\u0159idat nov\u00fd parametr (PKM-nov\u00fd parametr<\/i>), v poli Origin vybrat Internal, kliknout na tla\u010d\u00edtko Select a zvolit Ping Time. Je tam vyhled\u00e1v\u00e1n\u00ed, o kter\u00e9m jsem v Zabbixu jen snil. Tak\u00e9 m\u00e1 smysl zm\u011bnit interval dotazov\u00e1n\u00ed uzlu (v\u00fdchoz\u00ed je 60 sekund, tak\u017ee pokud router p\u0159estane odpov\u00eddat t\u011bsn\u011b po tom, co byl dotazov\u00e1n monitorovac\u00edm syst\u00e9mem, uplyne t\u00e9m\u011b\u0159 cel\u00e1 minuta, ne\u017e syst\u00e9m zjist\u00ed, \u017ee se n\u011bco d\u011bje, a spust\u00ed alarm).<\/p>\n

    Seznam Internal dat, kter\u00e1 lze zpracov\u00e1vat:<\/p>\n

    \"NetXMS
    \n
    \nJakmile byly do \u0161ablony p\u0159id\u00e1ny v\u0161echny pot\u0159ebn\u00e9 nastaven\u00ed, je t\u0159eba kliknout na PKM-aplikovat<\/i> a vybrat v\u0161echny uzly, ke kter\u00fdm by m\u011bla b\u00fdt tato \u0161ablona aplikov\u00e1na (ctrl-lev\u00e9 tla\u010d\u00edtko my\u0161i<\/i>). A to je v\u0161e. Pot\u00e9 se v hierarchii pod \u0161ablonou objev\u00ed v\u011btev, jej\u00edm\u017e rozbalen\u00edm je mo\u017en\u00e9 vid\u011bt v\u0161echny uzly, na kter\u00e9 byla tato \u0161ablona aplikov\u00e1na.<\/p>\n

    P\u0159i odpojen\u00ed uzlu od \u0161ablony shrom\u00e1\u017e\u010fovan\u00e9 \u00fadaje p\u0159est\u00e1vaj\u00ed b\u00fdt shroma\u017e\u010fov\u00e1ny, aby bylo mo\u017en\u00e9 zru\u0161it jejich shroma\u017e\u010fov\u00e1n\u00ed, je nutn\u00e9 pro ka\u017ed\u00fd uzel vstoupit do konfigurace shroma\u017e\u010fov\u00e1n\u00ed dat a v\u0161e ru\u010dn\u011b odstranit, nebo nejprve odstranit parametry ze \u0161ablony a a\u017e pot\u00e9 odstra\u0148ovat uzly. Nev\u00edm, pro\u010d je to ud\u011bl\u00e1no t\u00edmto zp\u016fsobem, ale podle m\u00e9ho n\u00e1zoru je to velice zvl\u00e1\u0161tn\u00ed. Ale... jak to je.<\/p>\n

    Ve \u0161ablon\u011b lze vybrat po\u017eadovan\u00e1 shrom\u00e1\u017ed\u011bn\u00e1 data a zkop\u00edrovat je do jin\u00e9 \u0161ablony. Hromadn\u011b. A nen\u00ed pot\u0159eba kop\u00edrovat z jedn\u00e9 \u0161ablony do druh\u00e9 ru\u010dn\u011b\u2026 U\u017e za\u010d\u00edn\u00e1m nen\u00e1vid\u011bt Zabbix.<\/p>\n

    3.7. Dashboards<\/h3>\n

    \nJak podivn\u00e9, ale NetXMS Wiki k tomu obsahuje pouze jeden odkaz na youtube: Vytv\u00e1\u0159en\u00ed dashboardu<\/a><\/noindex>, neexistuje ani seznam a popis prvk\u016f, kter\u00e9 lze na dashboard p\u0159idat. Principi\u00e1ln\u011b je to tam st\u00e1le intuitivn\u00ed. \u0160t\u00edtek<\/b> \u2014 to je prost\u011b\u2026 no\u2026 \u0161t\u00edtek\u2026 Ani nev\u00edm, jak to p\u0159elo\u017eit. Zkr\u00e1tka, pole s n\u00e1pisem, slou\u017e\u00ed k ozna\u010den\u00ed a odd\u011blen\u00ed prvk\u016f, proto\u017ee samy prvky n\u00e1zvy neobsahuj\u00ed. \u010c\u00e1rov\u00fd graf<\/b> \u2014 to je \u010d\u00e1rov\u00fd graf. Sloupcov\u00fd graf<\/b> \u2014 to je diagram. Alarm Viewer<\/b> \u2014 seznam upozorn\u011bn\u00ed pro vybran\u00fd\/\u00e9 uzel\/y. Zkr\u00e1tka, n\u00e1zvy mluv\u00ed samy za sebe. <\/p>\n

    D\u00e1le je t\u0159eba otev\u0159\u00edt vlastnosti dashboardu a nastavit zobrazen\u00ed. Zaj\u00edm\u00e1 n\u00e1s karta Prvky dashboardu. Po\u010det sloupc\u016f \u2014 to je po\u010det sloupc\u016f, prvk\u016f, kter\u00e9 budou um\u00edst\u011bny horizont\u00e1ln\u011b. Ka\u017ed\u00fd objekt m\u00e1 sv\u00e9 vlastnosti a doporu\u010dil bych zru\u0161it za\u0161krtnut\u00ed polo\u017eky Layout-Grab excessive vertical space, abychom minimalizovali velikost ka\u017ed\u00e9ho prvku.<\/p>\n

    \"NetXMS
    \n<\/p>\n

    3.8. Konfigurace akc\u00ed<\/h3>\n

    \n(Configuration-Actions Configuration)<\/i>
    \nVe skute\u010dnosti jsou to akce v reakci na spu\u0161t\u011bn\u00ed spou\u0161t\u011b\u010d\u016f.<\/p>\n

    \"NetXMS
    \n
    \nNetXMS dok\u00e1\u017ee pos\u00edlat e-mail, sms, xmpp zpr\u00e1vu v reakci na aktivaci spou\u0161t\u011b\u010de. Tady je to trivi\u00e1ln\u00ed \u2014 sta\u010d\u00ed vyplnit pot\u0159ebn\u00e1 pole.<\/p>\n

    Tak\u00e9 lze:<\/p>\n

    \u2014 P\u0159en\u00e9st upozorn\u011bn\u00ed na jin\u00fd server NetXMS
    \n \u2014 Proveden\u00ed p\u0159\u00edkazu na serveru administrace NetXMS
    \n \u2014 Proveden\u00ed p\u0159\u00edkazu na uzlu pomoc\u00ed agenta NetXMS
    \n \u2014 Proveden\u00ed skriptu NXSL (NSXL \u2014 to je vlastn\u00ed     programovac\u00ed jazyk NetXMS<\/a><\/noindex>)<\/p>\n

    Po vytvo\u0159en\u00ed akce je mo\u017en\u00e9 nastavit zpo\u017ed\u011bn\u00ed proveden\u00ed a tak\u00e9 aplikovat makro pro vykon\u00e1n\u00ed. Zpo\u017ed\u011bn\u00ed je pot\u0159ebn\u00e9, aby se oper\u00e1tor zbyte\u010dn\u011b neobt\u011b\u017eoval, pokud se probl\u00e9m vy\u0159e\u0161\u00ed s\u00e1m (nap\u0159\u00edklad doba odpov\u011bdi na ping byla del\u0161\u00ed ne\u017e stanoven\u00e1 hodnota, ale p\u0159i dal\u0161\u00ed kontrole se m\u016f\u017ee vr\u00e1tit k norm\u00e1lu, tak pro\u010d obt\u011b\u017eovat s takov\u00fdmi mali\u010dkostmi?).<\/p>\n

    3.9. Ov\u011b\u0159en\u00ed pr\u00e1v p\u0159\u00edstupu<\/h3>\n

    \nPro ka\u017ed\u00fd objekt lze nastavit sv\u00e1 pr\u00e1va p\u0159\u00edstupu. Pro ka\u017ed\u00fd objekt uvnit\u0159 jin\u00e9ho objektu lze tak\u00e9 nastavit pr\u00e1va p\u0159\u00edstupu. To umo\u017e\u0148uje velmi flexibiln\u011b rozd\u011blit povinnosti a mo\u017enosti monitorov\u00e1n\u00ed pro r\u016fzn\u00e9 skupiny u\u017eivatel\u016f. To je v\u0161echno, co jsem cht\u011bl \u0159\u00edct.<\/p>\n

    4. Z\u00e1v\u011br<\/h3>\n

    \nCht\u011bl bych zpochybnit n\u00e1zev sv\u00e9ho vlastn\u00edho \u010dl\u00e1nku. NetXMS nen\u00ed pro lenochy. V\u00fdvoj\u00e1\u0159i pouze ned\u016fraznili funk\u010dnost, jako to d\u011blaj\u00ed n\u011bkte\u0159\u00ed, ale krom\u011b toho se postarali o u\u017eivatelsk\u00e9 rozhran\u00ed.<\/p>\n

    \u0158ekn\u011bme to takhle. Pou\u017e\u00edval jsem Zabbix a NetXMS. Tak\u017ee jednodu\u0161e nap\u00ed\u0161u sv\u00e9 pocity z obou t\u011bchto syst\u00e9m\u016f.<\/p>\n

    Tak tedy.<\/p>\n

    NetXMS se mi jev\u00ed jako velmi u\u017eivatelsky p\u0159\u00edv\u011btiv\u00fd syst\u00e9m. No... pro administr\u00e1tora... ano, pro administr\u00e1tora. M\u00e1 to, \u010demu se \u0159\u00edk\u00e1 intuitivn\u00ed rozhran\u00ed, a to je skv\u011bl\u00e9. Nen\u00ed t\u0159eba ps\u00e1t vlastn\u00ed v\u00fdpo\u010dty, \u010d\u00edst spoustu dokumentace, abyste zapnuli kontrolu ping\u016f p\u0159ed switchem nebo n\u011bjakou jinou z\u00e1kladn\u00ed v\u011bc. Ale. V Zabbixu je tato z\u00e1kladn\u00ed v\u011bc velmi podobn\u00e1 n\u011b\u010demu skute\u010dn\u011b slo\u017eit\u00e9mu, tak\u017ee kdy\u017e to zvl\u00e1dnete, ud\u011bl\u00e1te stejn\u011b snadno i v\u0161echno ostatn\u00ed. V NetXMS jsou n\u00e1pov\u011bdy, v\u011bt\u0161inu parametr\u016f lze naj\u00edt v rozhran\u00ed, vybrat my\u0161\u00ed a nastavit. V Zabbixu mus\u00edte zjistit, zda syst\u00e9m um\u00ed to \u010di ono, a pokud ano, tak jak se to p\u00ed\u0161e a jak\u00e9 parametry to vrac\u00ed. Zabbix vyhr\u00e1v\u00e1 v komunit\u011b a v mno\u017estv\u00ed \u0161ablon pro v\u0161echny p\u0159\u00edpady... pokud se v t\u00e9to hromad\u011b odpadu poda\u0159\u00ed naj\u00edt to, co pot\u0159ebujete... Na druhou stranu m\u00e1 NetXMS tak\u00e9 spoustu p\u0159\u00edznivc\u016f a dodatk\u016f, kter\u00e9 vytvo\u0159ili. A samotn\u00fd syst\u00e9m z krabice um\u00ed monitorovat nejobl\u00edben\u011bj\u0161\u00ed aplikace, o \u010dem\u017e je zm\u00ednka na hlavn\u00ed str\u00e1nce projektu.<\/p>\n

    Hlavn\u00ed v\u00fdhodou NetXMS oproti Zabbix pro m\u011b byla mo\u017enost spustit skript na probl\u00e9mov\u00e9m uzlu jako reakci na aktivaci spou\u0161t\u011b\u010de. Teplota CPU vzrostla nad pr\u00e1h \u2013 sama vypne hostitele. A pak u\u017e se budeme zab\u00fdvat t\u00edm, v \u010dem je probl\u00e9m. Mo\u017en\u00e1, \u017ee v Zabbixu je tak\u00e9 takov\u00e1 v\u011bc, ale j\u00e1 jsem to nedok\u00e1zal naj\u00edt. Stejn\u011b jako monitorov\u00e1n\u00ed port\u016f na sm\u011brova\u010d\u00edch. A tady se to prost\u011b... No, jako prost\u011b... Mus\u00edte se nau\u010dit skriptovac\u00ed jazyk, a to je v\u0161e...<\/p>\n

    Pr\u00e1va p\u0159\u00edstupu v NetXMS umo\u017e\u0148uj\u00ed velmi flexibiln\u011b rozd\u011blovat mo\u017enosti r\u016fzn\u00fdch u\u017eivatel\u016f syst\u00e9mu. Ale abyste to v\u0161echno nastavili, mus\u00edte se opravdu n\u011bco nau\u010dit.<\/p>\n

    Celkov\u011b jsou syst\u00e9my dost podobn\u00e9 a jejich mo\u017enosti se na prvn\u00ed pohled zdaj\u00ed minim\u00e1ln\u011b srovnateln\u00e9. I kdy\u017e je c\u00edtit, \u017ee Zabbix m\u016f\u017ee v\u00edce, ale tyto mo\u017enosti le\u017e\u00ed hluboko pod povrchem a pro oby\u010dejn\u00e9ho administr\u00e1tora jsou \"v\u0161e v jednom\" nedosa\u017eiteln\u00e9. NetXMS se mi v\u0161ak jev\u00ed jako jednoduch\u00fd, srozumiteln\u00fd, p\u0159\u00edv\u011btiv\u00fd a p\u0159\u00edjemn\u00fd.<\/p>\n

    Zabbix m\u00e1 vynikaj\u00edc\u00ed dokumentaci, wiki, n\u00e1vody, F.A.Q., nejlep\u0161\u00ed praxe a tak\u00e9 r\u016fzn\u00e9 f\u00f3ra atd., kde lze naj\u00edt odpov\u011bdi t\u00e9m\u011b\u0159 na v\u0161echny ot\u00e1zky. A pokud ne, m\u016f\u017eete se zeptat sami.<\/p>\n

    Shrnut\u00ed, cht\u011bl bych doporu\u010dit NetXMS pro lidi, kte\u0159\u00ed pr\u00e1v\u011b za\u010d\u00ednaj\u00ed, nebo pro ty, kte\u0159\u00ed nepot\u0159ebuj\u00ed hluboce pronikat do monitorov\u00e1n\u00ed v\u0161eho a v\u0161ude. Jsem p\u0159esv\u011bd\u010den, \u017ee pokud se do toho pono\u0159\u00edte hloub\u011bji, m\u016f\u017eete v n\u011bm nastavit velmi podrobn\u00e9 sledov\u00e1n\u00ed.<\/p>\n

    Ale p\u0159esto vid\u00edm hlavn\u00ed v\u00fdhodu v opravdu p\u0159\u00edjemn\u00e9m rozhran\u00ed a jednoduchosti nastaven\u00ed.<\/p>\n

    5. Pou\u017eit\u00e9 materi\u00e1ly<\/h3>\n

    \nyoutube kan\u00e1l Tomas Kirnak<\/a><\/noindex>
    \n    NetXMS Wiki<\/a><\/noindex>
    \n    Google vyhled\u00e1v\u00e1n\u00ed<\/a><\/noindex><\/p>\n

    Zdroj: habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

    0. \u0418\u043d\u0442\u0440\u043e \u042f \u043d\u0435 \u043d\u0430\u0448\u0435\u043b \u043d\u0430 \u0425\u0430\u0431\u0440\u0435 \u043d\u0438 \u043e\u0434\u043d\u043e\u0439 \u0441\u0442\u0430\u0442\u044c\u0438 \u043f\u043e NetXMS, \u0445\u043e\u0442\u044f \u043e\u0447\u0435\u043d\u044c \u0438\u0441\u043a\u0430\u043b. \u0418 \u0442\u043e\u043b\u044c\u043a\u043e \u043f\u043e \u044d\u0442\u043e\u0439 \u043f\u0440\u0438\u0447\u0438\u043d\u0435 \u0440\u0435\u0448\u0438\u043b \u043d\u0430\u043f\u0438\u0441\u0430\u0442\u044c \u0441\u0438\u0435 \u0442\u0432\u043e\u0440\u0435\u043d\u0438\u0435, \u0434\u0430\u0431\u044b \u0443\u0434\u0435\u043b\u0438\u0442\u044c \u0432\u043d\u0438\u043c\u0430\u043d\u0438\u0435 \u0434\u0430\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u0435. \u042d\u0442\u043e \u0438 tutorial, \u0438 how to, \u0438 \u043f\u043e\u0432\u0435\u0440\u0445\u043d\u043e\u0441\u0442\u043d\u044b\u0439 \u043e\u0431\u0437\u043e\u0440 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0435\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b. \u0414\u0430\u043d\u043d\u0430\u044f \u0441\u0442\u0430\u0442\u044c\u044f \u0441\u043e\u0434\u0435\u0440\u0436\u0438\u0442 \u043f\u043e\u0432\u0435\u0440\u0445\u043d\u043e\u0441\u0442\u043d\u044b\u0439 \u0430\u043d\u0430\u043b\u0438\u0437 \u0438 \u043e\u043f\u0438\u0441\u0430\u043d\u0438\u0435 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0435\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u044b. \u0413\u043b\u0443\u0431\u043e\u043a\u043e \u0432 \u0432\u043e\u0437\u043c\u043e\u0436\u043d\u043e\u0441\u0442\u0438 \u044f \u043d\u0435 \u0437\u0430\u043a\u0430\u043f\u044b\u0432\u0430\u043b\u0441\u044f […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-42237","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\n","aioseo_head_json":{"title":"\ud83e\udd47NetXMS jako monitorovac\u00ed syst\u00e9m pro l\u00edn\u00e9\u2026 a trochu srovn\u00e1n\u00ed se Zabbix | ProHoster","description":"0.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/netxms-kak-sistema-monitoringa-dlya-lenivyh-i-nemnogo-sravneniya-s-zabbix","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47NetXMS \u043a\u0430\u043a \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433\u0430 \u0434\u043b\u044f \u043b\u0435\u043d\u0438\u0432\u044b\u0445\u2026 \u0438 \u043d\u0435\u043c\u043d\u043e\u0433\u043e \u0441\u0440\u0430\u0432\u043d\u0435\u043d\u0438\u044f \u0441 Zabbix | ProHoster","og:description":"0.","og:url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/netxms-kak-sistema-monitoringa-dlya-lenivyh-i-nemnogo-sravneniya-s-zabbix","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2019-03-17T21:00:00+00:00","article:modified_time":"2020-02-18T10:45:04+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"42237","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":"2026-01-22 07:44:19","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 00:03:36","updated":"2026-01-22 07:44:19","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/42237","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=42237"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/42237\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=42237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=42237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=42237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}