{"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\/sq\/blog\/administrirovanie\/netxms-kak-sistema-monitoringa-dlya-lenivyh-i-nemnogo-sravneniya-s-zabbix","title":{"rendered":"NetXMS si nj\u00eb sistem monitorimi p\u00ebr t\u00eb lenjt\u00eb\u2026 dhe pak krahasim me Zabbix","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

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

0. Intro<\/h3>\n

\nNuk e kam gjetur asnj\u00eb artikull mbi NetXMS n\u00eb Habr, megjith\u00ebse kam k\u00ebrkuar shum\u00eb. Dhe p\u00ebr k\u00ebt\u00eb arsye vendosa t\u00eb shkruaj k\u00ebt\u00eb krijes\u00eb, p\u00ebr t\u00eb t\u00ebrhequr v\u00ebmendjen ndaj k\u00ebtij sistemi.<\/p>\n

Ky \u00ebsht\u00eb nj\u00eb tutorial, si dhe nj\u00eb udh\u00ebzues, dhe nj\u00eb p\u00ebrmbledhje e mund\u00ebsive t\u00eb sistemit.<\/p>\n

Ky artikull p\u00ebrmban nj\u00eb analiz\u00eb sip\u00ebrfaq\u00ebsore dhe p\u00ebrshkrim t\u00eb mund\u00ebsive t\u00eb sistemit. Ndon\u00ebse nuk kam thelluar n\u00eb mund\u00ebsi p\u00ebr disa arsye. Dhe p\u00ebrshkrimi i t\u00ebr\u00eb funksionalitetit do t\u00eb k\u00ebrkonte m\u00eb shum\u00eb se nj\u00eb artikull.<\/p>\n

\u0422\u0430\u043a \u043a\u0430\u043a \u0431\u043e\u043b\u0435\u0435-\u043c\u0435\u043d\u0435\u0435 \u044f \u0440\u0430\u0431\u043e\u0442\u0430\u043b \u0442\u043e\u043b\u044c\u043a\u043e \u0441 Zabbix’\u043e\u043c \u2014 \u0432 \u0441\u0442\u0430\u0442\u044c\u0435 \u0431\u0443\u0434\u0435\u0442 \u0447\u0430\u0441\u0442\u043e \u0443\u043f\u043e\u043c\u0438\u043d\u0430\u0442\u044c\u0441\u044f \u0438\u043c\u0435\u043d\u043d\u043e \u044d\u0442\u0430 \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0434\u043b\u044f \u0441\u0440\u0430\u0432\u043d\u0435\u043d\u0438\u044f \u0441 \u0441\u0430\u0431\u0436\u0435\u043c. \u041a \u0442\u043e\u043c\u0443 \u0436\u0435 \u043a\u0430\u043a-\u0442\u043e \u0442\u0430\u043a \u043f\u043e\u0432\u0435\u043b\u043e\u0441\u044c, \u0447\u0442\u043e \u0432\u0441\u0435 \u0441\u0440\u0430\u0432\u043d\u0438\u0432\u0430\u0435\u0442\u0441\u044f \u0441 \u0447\u0435\u043c-\u0442\u043e \u043e\u0431\u0449\u0435\u043f\u0440\u0438\u0437\u043d\u0430\u043d\u043d\u044b\u043c.<\/p>\n

1. \u00c7far\u00eb dhe p\u00ebrse?<\/h3>\n

\nSistemi i monitorimit, si\u00e7 e tregon definicioni, \u00ebsht\u00eb nj\u00eb sistem q\u00eb lejon t\u00eb merrni informacion t\u00eb sakt\u00eb n\u00eb \u00e7do moment mbi nj\u00eb nyje, rrjetin, makinat, marshallat ose t\u00eb shkruani at\u00eb q\u00eb nevojitet.<\/p>\n

Pse \u00ebsht\u00eb kjo e nevojshme \u00ebsht\u00eb gjithashtu e qart\u00eb. P\u00ebr t\u00eb qen\u00eb n\u00eb dijeni t\u00eb asaj q\u00eb po ndodh.<\/p>\n

Shpesh, sistemi i monitorimit mund t\u00eb jap\u00eb informacione shum\u00eb t\u00eb plota mbi gjendjen e infrastruktur\u00ebs n\u00eb t\u00ebr\u00ebsi dhe t\u00eb pjes\u00ebve t\u00eb saj t\u00eb ve\u00e7anta. P\u00ebr m\u00eb tep\u00ebr, n\u00ebse konfigurohen paralajm\u00ebrimet (ndryshe \u00e7do monitorim nuk ka vler\u00eb), at\u00ebher\u00eb ne p\u00ebrfitojm\u00eb nj\u00eb instrument t\u00eb fuqish\u00ebm, i cili lejon jo vet\u00ebm reagimin e menj\u00ebhersh\u00ebm ndaj situatave emergjente q\u00eb kan\u00eb ndodhur, por n\u00eb shumic\u00ebn e rasteve, jep mund\u00ebsin\u00eb p\u00ebr t'i parandaluar ato.
\n<\/a><\/noindex><\/p>\n

2. Pse NetXMS?<\/h3>\n

\nPak offtopic p\u00ebr ata q\u00eb p\u00eblqejn\u00eb shum\u00eb shkronja<\/b>Kur kur ka qen\u00eb i ri dhe i pa p\u00ebrvoj\u00eb\u2026 A nuk fillojn\u00eb t\u00eb gjitha p\u00ebrrallat k\u00ebshtu? Nj\u00eb fjal\u00eb, kur isha maksimalist, studioja \u00e7\u00ebshtjen e monitorimit t\u00eb infrastruktur\u00ebs, dhe rezultati i atyre \"hetimeve\" ishte p\u00ebrfundimi se nuk ka asgj\u00eb m\u00eb t\u00eb mir\u00eb se Zabbix. Dhe n\u00eb at\u00eb koh\u00eb m\u00eb p\u00eblqente v\u00ebrtet, pasi kishte shum\u00eb mund\u00ebsi, shum\u00eb funksionalitete, dhe mund ta zgjerosh funksionalitetin me skripte t\u00eb shkruara vet\u00eb, k\u00ebshtu q\u00eb mund t\u00eb thuash se mund t\u00eb b\u00ebnte gjith\u00e7ka, n\u00ebse duar kishin vendin e duhur. Por Zabbix \u00ebsht\u00eb nj\u00eb mjet mjaft i komplikuar. P\u00ebr ta kuptuar, m\u00eb mori pothuajse dy jav\u00eb. Dhe kjo ishte vet\u00ebm faza e implementimit. Pastaj, disa jav\u00eb t\u00eb tjera p\u00ebr t\u00eb konfiguruar monitorimin e gjith\u00e7kaje q\u00eb m\u00eb nevojitej at\u00ebher\u00eb. Si t\u00eb shihja gjendjen e porteve n\u00eb routera, lexova, frik\u00ebsova dhe vendosa se nuk ishte aq e nevojshme p\u00ebr mua\u2026 Jo, atje \u00ebsht\u00eb v\u00ebrtet e frikshme p\u00ebr mendjen e pap\u00ebrgatitur menj\u00ebher\u00eb pas institutave...<\/p>\n

Dhe k\u00ebshtu, pas disa vjet\u00ebsh, duke u rritur dhe b\u00ebr\u00eb m\u00eb i pjekur, vendosa se ishte koha p\u00ebr t\u00eb rikuperuar njohurit\u00eb mbi sistemet e monitorimit. Dhe p\u00ebrfundimisht t\u00eb b\u00ebj nj\u00eb monitorim normal, stabil t\u00eb rrjetit, pasi ky problem ishte b\u00ebr\u00eb \u0430\u043a\u0442\u0443\u0430\u043b\u0435\u043d me rritjen e segmenteve, lidhjen e deg\u00ebs dhe gj\u00ebrave t\u00eb tjera t\u00eb vogla. T\u00eb gjitha l\u00ebvizin, gjith\u00e7ka ndryshon. Fillova t\u00eb testoj t\u00eb gjitha llojet e mjeteve. Nj\u00eb sistem e instaloj, e provoi, pastaj nj\u00eb tjet\u00ebr. Diku mungon di\u00e7ka, diku nuk m\u00eb p\u00eblqen gj\u00eb. Ose nd\u00ebrfaqja \u00ebsht\u00eb e pak\u00ebndshme, ose \u00ebsht\u00eb e v\u00ebshtir\u00eb t\u00eb konfigurosh, ose di\u00e7ka tjet\u00ebr. Dhe m\u00eb doli para NetXMS. N\u00eb fakt: atje ku me Zabbix u merrem dy jav\u00eb, me NetXMS gjith\u00e7ka shkoi p\u00ebr disa or\u00eb. Ndoshta ndikohet p\u00ebrvoja me Zabbix, ose ndoshta \u00ebsht\u00eb \u00e7\u00ebshtje e vet\u00eb NetXMS\u2026 e v\u00ebshtir\u00eb t\u00eb thuash.<\/p>\n

NetXMS doli t\u00eb ishte mjaft e thjesht\u00eb n\u00eb instalim dhe konfigurim. Ajo ka versione serveri dhe konsol\u00eb administrimi si p\u00ebr Windows ashtu edhe p\u00ebr Linux, nd\u00ebrtimin e grafik\u00ebve, nj\u00eb \"shkak\" t\u00eb integruar, i cili lejon nga brenda konsol\u00ebs s\u00eb administrat\u00ebs t\u00eb lidhet me ato same routera p\u00ebrmes protokolleve httphttps, dhe nj\u00eb nd\u00ebrfaqe intuitivisht e kuptueshme, si dhe nj\u00eb agjent p\u00ebr \u00e7do OS. N\u00eb nj\u00eb fjal\u00eb, ky sistem doli t\u00eb ishte i thjesht\u00eb dhe i p\u00ebrshtatsh\u00ebm. N\u00eb shikim t\u00eb par\u00eb.<\/p>\n

Dokumentacioni i tyre, p\u00ebr t\u00eb th\u00ebn\u00eb di\u00e7ka, \u00ebsht\u00eb 8 nga 10. Gj\u00ebrat kryesore jan\u00eb t\u00eb specifikuara aty, por p\u00ebr t\u00eb kuptuar nuancat, duhet t\u00eb p\u00ebrlesh.<\/p>\n

Pikat kryesore nga zhvilluesi<\/b>Monitorimi i thell\u00eb i rrjetit<\/b>
\nZbulimi automatik, vizualizimi dhe k\u00ebrkimi i komponent\u00ebve t\u00eb lidhur n\u00eb nivelin 2 dhe 3
\nP\u00ebrkrahje e plot\u00eb p\u00ebr SNMPv3
\nZbulimi aktiv p\u00ebrmes \u2018sondave\u2019 skanuese
\nZbulimi pasiv bazuar n\u00eb informacionin nga pajisjet e kontrolluara \u2014 ARP dhe tabelat e rrug\u00ebve, interface-et
\nMonitorimi i aplikacioneve dhe server\u00ebve<\/b>
\nT\u00eb gjitha metrikat kryesore q\u00eb prisni: procesori, sistemet e skedarit, hyrje-dalje, memoria, trafiku
\nUra JMX p\u00ebr monitorimin e aplikacioneve Java
\nZgjerime p\u00ebr aplikacione specifike: Oracle, MySQL, PostgreSQL, MongoDB, DB2, Tuxedo dhe shum\u00eb t\u00eb tjera
\nAPI integrimi p\u00ebr aplikacionet e veta
\nDestinuar p\u00ebr rrjete t\u00eb m\u00ebdha<\/b>
\nNj\u00eb server mund t\u00eb monitoroj\u00eb qindra metrika n\u00eb mij\u00ebra pajisje
\nP\u00ebrkrahje e plot\u00eb p\u00ebr monitorimin e shp\u00ebrndar\u00eb dhe shkall\u00ebzimin horizontal
\nMonitorimi i subneteve IP q\u00eb p\u00ebrputhen
\nKontroll t\u00eb fleksib\u00ebl t\u00eb aksesit p\u00ebr operator\u00ebt dhe klient\u00ebt<\/p>\n

3. Thellohemi<\/h3>\n

\nSi t\u00eb instaloni sistemin \u2014 ka nj\u00eb t\u00ebr\u00eb manual<\/a><\/noindex> t\u00eb administratorit, t\u00eb disponuesh\u00ebm n\u00eb faqen e zhvilluesit<\/a><\/noindex>, dhe nuk ka asgj\u00eb t\u00eb komplikuar n\u00eb k\u00ebt\u00eb, k\u00ebshtu q\u00eb nuk do t\u00eb ndalem k\u00ebtu. E vetmja gj\u00eb e v\u00ebshtir\u00eb n\u00eb instalim \u00ebsht\u00eb lidhja e sistemit me baz\u00ebn e t\u00eb dh\u00ebnave\u2026 K\u00ebtu ndryshimi do t\u00eb jet\u00eb vet\u00ebm n\u00eb p\u00ebrzgjedhjen e DBMS dhe OS-s\u00eb s\u00eb serverit. Un\u00eb zgjodha Windows (pastaj \u2013 futur t\u00eb dh\u00ebnat \u2013 gati) dhe MSSQL, pasi ajo tashm\u00eb ishte e instaluar.<\/p>\n

3.1. Aktivizoni zbulimin automatik<\/h3>\n

\nZbulimi automatik i nyjeve t\u00eb rrjetit mund t\u00eb aktivizohet gjat\u00eb instalimit. N\u00ebse p\u00ebr ndonj\u00eb arsye nuk \u00ebsht\u00eb b\u00ebr\u00eb, gjithmon\u00eb mund ta aktivizoni n\u00eb \u00abConfiguration-Network Discovery\u00bb<\/i> ose duke klikuar mbi ikon\u00ebn me t\u00eb nj\u00ebjtin em\u00ebr. N\u00eb zon\u00ebn e pun\u00ebs do t\u00eb shfaqen vetit\u00eb e zbulimit. Duhet ta aktivizoni duke e kaluar n\u00eb modin pasiv ose aktiv, dhe t\u00eb p\u00ebrcaktoni vetit\u00eb e tjera, si p\u00ebr shembull subnetet e p\u00ebrshtatura p\u00ebr pyetje. K\u00ebtu gjithashtu mund t\u00eb krijoni filtrat, ku mund t\u00eb zgjidhni dhe t\u00eb p\u00ebrshtatni ato t\u00eb integruara n\u00eb sistem, ose t\u00eb shkruani skenar\u00ebt tuaj t\u00eb vet. T\u00eb them t\u00eb drejtat \u2014 un\u00eb nuk kisha nevoj\u00eb p\u00ebr filtrat. Por konfigurimi duket mjaft miq\u00ebsor dhe i qart\u00eb.<\/p>\n

Gjithashtu k\u00ebtu mund t\u00eb p\u00ebrcaktoni komunitetin SNMP si parazgjedhje dhe kredencialet e tij (lexo autorizimin).<\/p>\n

3.2. Shtimi i nyjeve<\/h3>\n

\nMe ndihm\u00ebn e aktivizimit t\u00eb vet\u00eb-zbulimit, skajet (PC, printer\u00eb) do t\u00eb shtohen dhe shp\u00ebrndahen n\u00eb n\u00ebnrrjeta automatikisht. Me pajisjet e aktivizuara, gj\u00ebrat jan\u00eb pak m\u00eb t\u00eb komplikuara.<\/p>\n

Duhet t\u00eb filloni me aktivizimin e SNMP n\u00eb pajisjet e rrjetit dhe t\u00eb konfiguroni community. N\u00ebse vlera e paracaktuar p\u00ebr community SNMP n\u00eb pron\u00ebsit\u00eb e zbulimit t\u00eb nodave nuk \u00ebsht\u00eb ndryshuar, sistemi do t\u00eb p\u00ebrdor\u00eb community-n\u00eb public, dhe ky cil\u00ebsim mund t\u00eb ndryshohet p\u00ebr secil\u00ebn nod\u00eb n\u00eb pron\u00ebsit\u00eb e nod\u00ebs s\u00eb shtuar.<\/p>\n

P\u00ebr leht\u00ebsi, mund t\u00eb grumbulloni pajisjet sipas \u00e7do parimi t\u00eb p\u00ebrshtatsh\u00ebm, p\u00ebr k\u00ebt\u00eb, n\u00eb struktur\u00ebn e Infrastruktur\u00ebs Sh\u00ebrbimeve, mund t\u00eb krijoni konteiner\u00eb dhe t'i lidhni atyre nodet nga Rrjeti i Plot\u00eb.<\/p>\n

Pas aktivizimit dhe konfigurimit t\u00eb SNMP n\u00eb routerat dhe shtimit t\u00eb tyre n\u00eb list\u00ebn e pajisjeve t\u00eb monitoruara, sistemi do t\u00eb komunikoj\u00eb automatikisht me to, do t'i anketoj\u00eb, do t\u00eb identifikoj\u00eb se \u00e7far\u00eb pajisjesh jan\u00eb, do t\u00eb aplikoj\u00eb shabllonet, do t\u00eb filloj\u00eb mbledhjen e t\u00eb dh\u00ebnave dhe do t\u00eb tregoj\u00eb panelin e p\u00ebrparm\u00eb p\u00ebr \u00e7do router. Vet\u00eb. Nga kutia. Kur konfigurja ime p\u00ebr Zabbix \u00ebsht\u00eb b\u00ebr\u00eb, p\u00ebr nj\u00eb di\u00e7ka t\u00eb till\u00eb kam mundur vet\u00ebm t\u00eb \u00ebnd\u00ebrroj.<\/p>\n

\"NetXMS
\n
\nUn\u00eb kam shtuar t\u00eb gjitha pajisjet e mia rrjet\u00ebrisht manualisht, pasi q\u00eb ato nuk u zbuluan p\u00ebr ndonj\u00eb arsye. K\u00ebtu gjith\u00e7ka \u00ebsht\u00eb e thjesht\u00eb. Krijoni nj\u00eb konteiner n\u00eb Infrastruktur\u00ebn e Sh\u00ebrbimeve me \u00e7do em\u00ebr t\u00eb p\u00ebrshtatsh\u00ebm (p\u00ebr shembull switches), dhe Klikoni me t\u00eb djatht\u00ebn p\u00ebr t\u00eb krijuar nj\u00eb nod\u00eb<\/i>, tregoni emrin e duksh\u00ebm t\u00eb nod\u00ebs, adres\u00ebn e saj IP dhe \u00ebsht\u00eb m\u00eb mir\u00eb t\u00eb vendosni shenj\u00ebn n\u00eb \"\u00e7aktivizoni p\u00ebrdorimin e agentit NetXMS\", pasi q\u00eb s\u00ebrish nuk mund t\u00eb instaloni at\u00eb n\u00eb pajisjet e rrjetit, dhe paketat e tep\u00ebrta jan\u00eb t\u00eb panevojshme.<\/p>\n

Bashk\u00ebngjit\u00ebsi i integruar. Mund t\u00eb klikoni me t\u00eb djatht\u00ebn n\u00eb routerin e d\u00ebshiruar dhe t\u00eb hapni nd\u00ebrfaqen web t\u00eb pajisjes. M\u00eb duket m\u00eb e leht\u00eb se sa \u00e7do her\u00eb t\u00eb shkoj n\u00eb sh\u00ebnimet e mia dhe t\u00eb k\u00ebrkoj adres\u00ebn IP t\u00eb nevojshme. Megjithat\u00eb, shfletuesi \u00ebsht\u00eb mjaft i dob\u00ebt.<\/p>\n

3.3. Nd\u00ebrtimi i hart\u00ebs s\u00eb rrjetit<\/h3>\n

\nS\u00eb pari, duhet t\u00eb krijoni nj\u00eb hart\u00eb rrjeti si objekt. Si zakonisht \u2014 N\u00eb deg\u00ebn Hartat e Rrjetit klikoni me t\u00eb djatht\u00ebn, krijoni, zgjidhni llojin e hart\u00ebs, caktoni parametrat<\/i>, dhe sistemi do ta b\u00ebj\u00eb t\u00eb gjith\u00eb pun\u00ebn vet\u00eb.<\/p>\n

Llojet e hartave jan\u00eb si vijon:<\/p>\n

    \n
  1. Custom<\/b>. Kjo \u00ebsht\u00eb nj\u00eb hart\u00eb e destinuar p\u00ebr formimin manual, sipas d\u00ebshir\u00ebs s\u00eb p\u00ebrdoruesit.<\/li>\n
  2. Topologjia Layer 2<\/b>. Kjo \u00ebsht\u00eb nj\u00eb hart\u00eb q\u00eb lejon q\u00eb sistemi t\u00eb b\u00ebj\u00eb automatikisht gjith\u00e7ka p\u00ebr p\u00ebrdoruesin, duke u bazuar n\u00eb nivelin 2 t\u00eb modelit OSI (n\u00eb thelb, nd\u00ebrtimi i hart\u00ebs i bazuar n\u00eb adresat MAC t\u00eb pajisjeve). <\/li>\n
  3. Topologjia IP<\/b>, gjithashtu e njohur si Layer 3<\/b>. E nj\u00ebjta gj\u00eb si n\u00eb rastin e Layer 2<\/b>, vet\u00ebm q\u00eb harta nd\u00ebrtohet n\u00eb baz\u00eb t\u00eb nivelit 3 t\u00eb modelit OSI (adresat IP).<\/li>\n<\/ol>\n

    \nKur zgjedhja e hart\u00ebs manuale, duhet t\u00eb t\u00ebrheq\u00ebsh nodet nga druri n\u00eb layerin e hart\u00ebs, t'i lidh\u00ebsh ato etj. Nj\u00eb skicim i zakonsh\u00ebm. <\/p>\n

    N\u00eb dy rastet e tjera, duhet t\u00eb zgjidhni nj\u00eb pik\u00eb reference, nga e cila sistemi do t\u00eb filloj\u00eb t\u00eb nd\u00ebrtoj\u00eb hart\u00ebn. P\u00ebr shembull, nj\u00eb nod\u00eb t\u00eb ndonj\u00eb routeri. Sistemi lexon t\u00eb dh\u00ebnat nga ai p\u00ebr pajisjet e lidhura dhe portet ku ato jan\u00eb t\u00eb lidhura, pastaj lexon t\u00eb dh\u00ebnat nga routeri tjet\u00ebr, p\u00ebrputh ditarin, dhe k\u00ebshtu me radh\u00eb. Pas analiz\u00ebs s\u00eb t\u00eb gjitha pajisjeve, NetXMS vet\u00eb do t\u00eb vizatoj\u00eb lidhjet midis pajisjeve n\u00eb rrjet duke treguar portet, ku \u00e7far\u00eb \u00ebsht\u00eb e lidhur. Po ashtu, mund t\u00eb specifikoni q\u00eb sistemi t\u00eb vendos\u00eb n\u00eb hart\u00eb edhe pajisjet p\u00ebrfundimtare (printer\u00eb, PC, servera), duke klikuar thjesht n\u00eb pik\u00ebn p\u00ebrkat\u00ebse n\u00eb pronat e hart\u00ebs (PKM \u2014 pronat \u2014 pronat e hart\u00ebs<\/i>). Po ashtu n\u00eb k\u00ebt\u00eb pik\u00eb mund t\u00eb caktoni \"rrezen e zbulimit\" n\u00ebse d\u00ebshironi apo \u00ebsht\u00eb e nevojshme.<\/p>\n

    Nj\u00eb rekomandim t\u00eb vog\u00ebl. Aktivizoni pron\u00ebn Always fit layout to screen, n\u00eb m\u00ebnyr\u00eb q\u00eb \u00e7do her\u00eb q\u00eb p\u00ebrdit\u00ebsoni hart\u00ebn e rrjetit, t\u00eb mos keni nevoj\u00eb t\u00eb rrokullisni hap\u00ebsir\u00ebn e pun\u00ebs dhe t\u00eb punoni me zoom.<\/p>\n

    \"NetXMS
    \n
    \nN\u00eb nj\u00eb topologji t\u00eb shp\u00ebrndar\u00eb t\u00eb rrjetit, mund t\u00eb vendosni objekte mbi hart\u00ebn e territorit. Po ashtu, mund t\u00eb p\u00ebrdorni nj\u00eb foto t\u00eb rafteve me pajisje n\u00eb server\u00eb si sfond, duke vendosur mbi t\u00eb objektet e nevojshme. K\u00ebshtu mund t\u00eb p\u00ebrcaktoni shpejt statusin e \u00e7do pajisjeje n\u00eb raft. N\u00eb mendimin tim, kjo \u00ebsht\u00eb nj\u00eb gj\u00eb tep\u00ebr e dobishme n\u00eb rastin kur duhet t\u00eb transferoni pun\u00ebt te nj\u00eb pasardh\u00ebs ose t\u2019i shpjegoni nj\u00eb kollegu t\u00eb sapoardhur situat\u00ebn. E qart\u00eb, e p\u00ebrshtatshme, vet\u00ebkuptueshme.<\/p>\n

    3.4. Agjent\u00ebt<\/h3>\n

    \nAgjent\u00ebt ekzistojn\u00eb p\u00ebr Windows ashtu si p\u00ebr Linux. Parimi i funksionimit \u00ebsht\u00eb i nj\u00ebjt\u00eb me agjent\u00ebt e Zabbix t\u00eb nj\u00ebjt\u00eb: instalohet n\u00eb makin\u00ebn nga e cila duhet t\u00eb merren metrikat dhe transmeton t\u00eb dh\u00ebnat n\u00eb serverin e monitorimit. Agjentit mund t'i instalohet si para shtimit t\u00eb nod\u00ebs n\u00eb sistem ashtu edhe pas saj. Pas shfaqjes s\u00eb agjentit n\u00eb nod\u00eb, sistemi pas nj\u00eb kohe do t\u00eb filloj\u00eb t\u00eb pranoj\u00eb t\u00eb dh\u00ebna prej tij, duke aplikuar nj\u00eb \u015fablon standard. Mund t\u00eb shtoni parametrat e monitoruar si p\u00ebr nj\u00eb nod\u00eb, ashtu edhe duke i lidhur asaj nj\u00eb ose m\u00eb shum\u00eb \u015fablone t\u00eb paracaktuara. Sigurisht, rekomandohet t\u00eb punoni me \u015fablonet, pasi kjo konfigurim \u00ebsht\u00eb m\u00eb fleksibile.<\/p>\n

    Lista e parametrave t\u00eb ndjekjes p\u00ebr agjent\u00ebt \u00ebsht\u00eb mjaft e gjer\u00eb. Mund ta shikoni list\u00ebn e plot\u00eb n\u00eb Wiki NetXMS<\/a><\/noindex><\/p>\n

    Sapo sistemi t\u00eb p\u00ebrcaktoj\u00eb se n\u00eb nod ndodhet nj\u00eb agjent, ai menj\u00ebher\u00eb do t\u00eb lidh\u00eb k\u00ebt\u00eb nod me nj\u00ebrin nga shabllonet standarde \u2014 Windows, Linux, HP-UX, Generic UNIX, AIX<\/b>, n\u00eb var\u00ebsi t\u00eb sistemit operativ t\u00eb nodit.<\/p>\n

    Shablloni standard p\u00ebr hostet Windows:<\/p>\n

    \"NetXMS
    \n
    \n\u0414\u043e\u0431\u0430\u0432\u0438\u0442\u044c \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440 \u0434\u043b\u044f \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u043d\u0438\u044f \u043a\u043e\u043d\u043a\u0440\u0435\u0442\u043d\u043e\u0439 \u043d\u043e\u0434\u0435 \u043c\u043e\u0436\u043d\u043e \u0449\u0435\u043b\u043a\u043d\u0443\u0432 «Klikim t\u00eb djatht\u00ebn - Parametri i mbledhjes s\u00eb t\u00eb dh\u00ebnave<\/i>«, \u0434\u0430\u043b\u0435\u0435 «Klikim t\u00eb djatht\u00ebn n\u00eb hap\u00ebsir\u00ebn e pun\u00ebs \u2014 Parametri i ri<\/i>«, \u0438 \u0432\u044b\u0431\u0440\u0430\u0442\u044c \u043d\u0443\u0436\u043d\u043e\u0435 \u0438\u0437 \u0441\u043f\u0438\u0441\u043a\u0430. \u0422\u0443\u0442 \u0436\u0435 \u043c\u043e\u0436\u043d\u043e \u043d\u0430\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u0438 \u0442\u0440\u0438\u0433\u0433\u0435\u0440\u044b \u0434\u043b\u044f \u043e\u0442\u0441\u043b\u0435\u0436\u0438\u0432\u0430\u0435\u043c\u043e\u0433\u043e \u043f\u0430\u0440\u0430\u043c\u0435\u0442\u0440\u0430.<\/p>\n

    \u00cbsht\u00eb e r\u00ebnd\u00ebsishme q\u00eb agjent\u00ebt, ashtu si tek Zabbix, din\u00eb t\u00eb ekzekutojn\u00eb skripte t\u00eb p\u00ebrdoruesve.<\/p>\n

    Si t\u00eb instaloni?<\/b>Kjo \u00ebsht\u00eb jasht\u00eb tem\u00ebs, pasi \u00e7do... hmmm... si d\u00ebshiron.<\/p>\n

    K\u00ebtu \u00e7\u00ebshtja \u00ebsht\u00eb \u2014 a duhet t\u00eb shp\u00ebrndahen agjent\u00ebt vet\u00ebm n\u00eb server\u00eb, apo n\u00eb t\u00eb gjitha makinat e rrjetit? N\u00ebse jan\u00eb server\u00eb dhe ata jan\u00eb pak \u2014 m\u00eb s\u00eb lehti me dor\u00eb. N\u00ebse shum\u00eb \u2014 politikat e domain-it, KIX, PoSh. \u00c7far\u00ebdo q\u00eb t\u00eb jet\u00eb. Agjent\u00ebt kan\u00eb \u00e7el\u00ebsin \/SILENT, q\u00eb lejon \"injektimin\" e tij n\u00eb m\u00ebnyr\u00eb transparente p\u00ebr p\u00ebrdoruesin (n\u00ebse flasim p\u00ebr shp\u00ebrndarjen n\u00eb t\u00eb gjitha makinat e rrjetit). Un\u00eb preferoj skripte, pasi mund t\u00eb vendos\u00ebsh nj\u00eb kusht dhe t\u00eb krijosh nj\u00eb lloj flag-u, ndryshe nga politikat q\u00eb do t\u00eb instalojn\u00eb programin \u00e7do her\u00eb kur t\u00eb ndizet kompjuteri. Pra, shkruajm\u00eb nj\u00eb skript nga seria \"kontrollo pranin\u00eb e skedarit-flagu, n\u00ebse nuk \u00ebsht\u00eb atje \u2014 ekzekuto instaluesin me \u00e7el\u00ebsin \/SILENT dhe pas instalimit t\u00eb suksessh\u00ebm krijo skedarin-flagu\". Fitim.<\/p>\n

    3.5. Triggere<\/h3>\n

    \nTriggere mund t\u00eb konfigurohen p\u00ebr t\u00eb reaguar ndaj ngjarjeve t\u00eb caktuara n\u00eb t\u00eb dh\u00ebnat e mbledhura. P\u00ebr shembull, kalimi i nj\u00eb vlere t\u00eb caktuar ping-pong deri te routeri. Gjithashtu, p\u00ebr \u00e7do trigger konfigurohet m\u00ebnyra e njoftimit (p\u00ebr disa mjafton ikona n\u00eb konsol\u00eb, nd\u00ebrsa disa menj\u00ebher\u00eb d\u00ebrgojn\u00eb njoftime ku t\u00eb mundshme). Reagimi ndaj ngjarjes zgjidhet nga ato t\u00eb parap\u00ebrcaktuara n\u00eb Konfigurimin e Veprimit.<\/p>\n

    P\u00ebr t\u00eb krijuar nj\u00eb trigger: hyni n\u00eb Konfigurimin e Mbledhjes s\u00eb t\u00eb Dh\u00ebnave t\u00eb nodit ose shabllonit, dy her\u00eb klikoni mbi parametrin q\u00eb ju intereson (n\u00ebse nuk ka, duhet ta krijoni s\u00eb pari), dhe n\u00eb pron\u00ebsi kaloni n\u00eb tabin Thresholds, klikoni butonin shto.<\/i><\/p>\n

    \"NetXMS
    \n
    \n«Funksioni<\/b>» \u2014 \u043a\u0430\u043a\u043e\u0435 \u0438\u043b\u0438 \u043a\u0430\u043a\u0438\u0435 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u044f \u0431\u0440\u0430\u0442\u044c \u0434\u043b\u044f \u0432\u044b\u0447\u0438\u0441\u043b\u0435\u043d\u0438\u044f \u0443\u0441\u043b\u043e\u0432\u0438\u044f. \u041c\u043e\u0436\u0435\u0442 \u043f\u0440\u0438\u043d\u0438\u043c\u0430\u0442\u044c \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0438\u0435 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u044f (\u043a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u043e \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c\u044b\u0445 \u0434\u043b\u044f \u043f\u0440\u043e\u0432\u0435\u0440\u043a\u0438 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0439 \u0443\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u0432 \u043f\u043e\u043b\u0435 Samples):
    \n \u2014 Vlera e fundit t\u00eb pyetur: vlera\/ vlerat e fundit t\u00eb marra
    \n \u2014 Vlera mesatare: mesatarja e vlerave t\u00eb fundit
    \n \u2014 Shkalla e mesme e devijimit: devijimi mesatar
    \n \u2014 Diferenca me vler\u00ebn e m\u00ebparshme: ndryshimi me vler\u00ebn e m\u00ebparshme
    \n \u2014 Gabimi i mbledhjes s\u00eb t\u00eb dh\u00ebnave: gabimi n\u00eb marrjen e t\u00eb dh\u00ebnave
    \n \u2014 Shuma e vlerave: shuma e vlerave
    \n \u2014 Skripti: vlera e marr\u00eb si rezultat i pun\u00ebs s\u00eb skriptit t\u00eb p\u00ebrdoruesit<\/p>\n

    «Operacioni<\/b>» \u2014 \u0443\u0441\u043b\u043e\u0432\u0438\u0435 \u0441\u0440\u0430\u0431\u0430\u0442\u044b\u0432\u0430\u043d\u0438\u044f \u0442\u0440\u0438\u0433\u0433\u0435\u0440\u0430. \u041c\u043e\u0436\u0435\u0442 \u043f\u0440\u0438\u043d\u0438\u043c\u0430\u0442\u044c \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u044f (\u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 \u0443\u043a\u0430\u0437\u044b\u0432\u0430\u0435\u0442\u0441\u044f \u0432 \u0441\u043e\u043e\u0442\u0432\u0435\u0442\u0441\u0442\u0432\u0443\u044e\u0449\u0435\u043c \u043f\u043e\u043b\u0435 Value):
    \n \u2014 <: m\u00eb pak se: m\u00eb pak se
    \n \u2014 <=: m\u00eb pak se ose baras me: m\u00eb pak ose nj\u00ebsoj
    \n \u2014 == baras me: ekvivalent me
    \n \u2014 >=: m\u00eb shum\u00eb se ose baras me: m\u00eb shum\u00eb ose nj\u00ebsoj
    \n \u2014 >: m\u00eb shum\u00eb se: m\u00eb shum\u00eb se
    \n \u2014 !=: jo baras me: jo ekvivalent me
    \n \u2014 si: af\u00ebrsisht i barabart\u00eb me
    \n \u2014 jo si: jo af\u00ebrsisht i barabart\u00eb me
    \nP\u00ebr dy parametrat e fundit nuk kam siguri se si funksionojn\u00eb. Prandaj nuk do t\u00eb supozoj se \u00e7far\u00eb kufijsh jan\u00eb t\u00eb integruar n\u00eb to.<\/p>\n

    Pra, gjith\u00e7ka si n\u00eb Zabbix, vet\u00ebm se nuk \u00ebsht\u00eb e nevojshme t\u00eb shkruash formulat me dor\u00eb, duke u frik\u00ebsuar nga gabimet ose shkrimi i gabuar. P\u00ebr t\u00eb rikthyer trigger-in (ngjarja e \u00e7aktivizimit), sistemi do t\u00eb vendos\u00eb vler\u00ebn vet\u00eb. (N\u00eb Zabbix p\u00ebrs\u00ebri duhet t\u00eb shtyp\u00ebsh dhe t\u00eb mos gabosh).<\/p>\n

    3.6. \u015eablon\u00ebt<\/h3>\n

    \nKliko me t\u00eb djatht\u00ebn - krijo nj\u00eb \u015fablon, fut emrin e \u015fablonit. Kliko me t\u00eb djatht\u00ebn - Konfigurimi i M\u00ebrritjes s\u00eb t\u00eb Dh\u00ebnave.<\/i><\/p>\n

    Pak teori<\/b>Informacioni i mbledhur mund t\u00eb vij\u00eb nga disa burime. Kjo mund t\u00eb jet\u00eb agjenti NetXMS<\/b>, \u0440\u0430\u0431\u043e\u0442\u0430\u044e\u0449\u0438\u0439 \u043d\u0430 \u043c\u0430\u0448\u0438\u043d\u0435, \u043c\u043e\u0436\u0435\u0442 \u0431\u044b\u0442\u044c «k\u00ebrkes\u00eb e thjesht\u00eb<\/b>» \u0438\u043b\u0438 «Internal<\/b>«, \u043e\u0442\u043f\u0440\u0430\u0432\u043b\u044f\u0435\u043c\u044b\u0439 \u0441\u0430\u043c\u0438\u043c \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u043c (\u043d\u0430\u043f\u0440\u0438\u043c\u0435\u0440 \u0442\u043e\u0442 \u0436\u0435 ping), «SNMP<\/b>«, «check point SNMP<\/b>«, «Shtytje<\/b>«, «Windows Performance Counters<\/b>«, «SM-CLP<\/b>«, \u0438\u043b\u0438 \u0436\u0435 \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u0441\u043a\u0438\u0439 «skript<\/b>«. \u0423 \u043a\u0430\u0436\u0434\u043e\u0433\u043e \u0442\u0438\u043f\u0430 \u0438\u043d\u0444\u043e\u0440\u043c\u0430\u0446\u0438\u0438 \u043c\u043e\u0436\u043d\u043e \u0432\u044b\u0431\u0440\u0430\u0442\u044c \u0442\u0438\u043f, \u043a\u043e\u0442\u043e\u0440\u044b\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u0430 \u0431\u0443\u0434\u0435\u0442 \u043e\u0436\u0438\u0434\u0430\u0442\u044c \u043f\u0440\u0438 \u043f\u043e\u043b\u0443\u0447\u0435\u043d\u0438\u0438. \u041d\u0430\u043f\u0440\u0438\u043c\u0435\u0440, ping \u0431\u0443\u0434\u0435\u0442 \u0432\u043e\u0437\u0432\u0440\u0430\u0449\u0430\u0442\u044c \u0446\u0435\u043b\u043e\u0447\u0438\u0441\u043b\u0435\u043d\u043d\u043e\u0435 \u0437\u043d\u0430\u0447\u0435\u043d\u0438\u0435 (integer), \u043a\u043e\u043b\u0438\u0447\u0435\u0441\u0442\u0432\u043e \u0441\u0432\u043e\u0431\u043e\u0434\u043d\u043e\u0433\u043e \u0434\u0438\u0441\u043a\u043e\u0432\u043e\u0433\u043e \u043f\u0440\u043e\u0441\u0442\u0440\u0430\u043d\u0441\u0442\u0432\u0430 \u0432 \u0431\u0430\u0439\u0442\u0430\u0445 \u0442\u0430\u043a \u0436\u0435 \u0431\u0443\u0434\u0435\u0442 integer, \u0430 \u0432\u043e\u0442 \u0442\u0430 \u0436\u0435 \u0442\u0435\u043c\u043f\u0435\u0440\u0430\u0442\u0443\u0440\u0430 \u0431\u0443\u0434\u0435\u0442 \u0443\u0436\u0435 \u043d\u0435 \u0446\u0435\u043b\u043e\u0447\u0438\u0441\u043b\u0435\u043d\u043d\u044b\u043c, \u0442\u043e \u0435\u0441\u0442\u044c real).<\/p>\n

    P\u00ebr t\u00eb mbledhur informacion p\u00ebrmes SNMP n\u00eb NetXMS ka nj\u00eb list\u00eb t\u00eb madhe parametrash t\u00eb paracaktuar, pra nuk \u00ebsht\u00eb e nevojshme t\u00eb shkruash OID t\u00eb ve\u00e7ant\u00eb, por mund ta gjesh at\u00eb n\u00eb pem\u00ebn MIB, e cila \u00ebsht\u00eb mjaft problematike n\u00eb t\u00eb v\u00ebrtet\u00eb... Por. N\u00eb fund do t\u00eb duhet t\u00eb k\u00ebrkosh n\u00eb dokumentacionin e prodhuesit dhe t\u00eb k\u00ebrkosh vlerat IOD p\u00ebr \u00e7do pajisje ve\u00e7mas. Mund t\u00eb humbas\u00ebsh shum\u00eb koh\u00eb n\u00eb konfigurimin e marrjes s\u00eb informacionit nga pajisjet, duke u takuar me mesazhin e sistemit \"UNSUPPORTED\"<\/i>, kur n\u00eb fund rezulton se kjo pajisje specifike thjesht nuk \u00ebsht\u00eb n\u00eb gjendje t\u00eb ofroj\u00eb informacionin e k\u00ebrkuar. K\u00ebtu ka vet\u00ebm t\u00eb lexosh manualet dhe t\u00eb shpresosh.<\/p>\n

    P\u00ebr shembull, p\u00ebr t\u00eb mbledhur informacion rreth koh\u00ebs s\u00eb p\u00ebrgjigjes s\u00eb nodit (ping), duhet t\u00eb shtoni nj\u00eb paramet\u00ebr t\u00eb ri (Klikim t\u00eb djatht\u00eb-paramet\u00ebr i ri<\/i>), n\u00eb fush\u00ebn Origin zgjidhni Internal, klikoni butonin Zgjidh, dhe zgjidhni Koh\u00ebn e Ping. Aty ka nj\u00eb k\u00ebrkim, p\u00ebr t\u00eb cilin un\u00eb kam \u00ebnd\u00ebrruar n\u00eb Zabbix. Ka gjithashtu kuptim t\u00eb ndryshohet periudha e sondazhit t\u00eb nodit (me default 60 sekonda, do t\u00eb thot\u00eb q\u00eb n\u00ebse ruter-i ndalon s\u00eb p\u00ebrgjigjuri menj\u00ebher\u00eb pas sondazhit nga sistemi i monitorimit, do t\u00eb kaloj\u00eb gati nj\u00eb minut\u00eb para se sistemi t\u00eb kuptoj\u00eb se ka ndodhur ndonj\u00eb problem dhe t\u00eb l\u00ebshoj\u00eb alarm).<\/p>\n

    Lista e t\u00eb dh\u00ebnave Internal q\u00eb mund t\u00eb p\u00ebrpunohen:<\/p>\n

    \"NetXMS
    \n
    \nPas shtimit t\u00eb t\u00eb gjitha cil\u00ebsimeve t\u00eb nevojshme n\u00eb template, duhet t\u00eb klikoni Klikim t\u00eb djatht\u00eb-apliko<\/i> dhe t\u00eb zgjidhni t\u00eb gjith\u00eb nodet, t\u00eb cil\u00ebve ky template duhet t\u00eb aplikohet (ctrl+Klikim t\u00eb majt\u00eb<\/i>). Dhe mbaroi. Pas k\u00ebsaj n\u00eb deg\u00ebn n\u00ebn template do t\u00eb shfaqet nj\u00eb deg\u00eb, duke e hapur t\u00eb cil\u00ebn, mund t\u00eb shihni t\u00eb gjitha nodet, t\u00eb cil\u00ebve ky template i \u00ebsht\u00eb aplikuar.<\/p>\n

    Kur nodet shk\u00ebputen nga template, t\u00eb dh\u00ebnat e mbledhura nuk ndalojn\u00eb s\u00eb mbledhuri, p\u00ebr t\u00eb anuluar mbledhjen e tyre duhet t\u00eb hyhet n\u00eb Konfigurimin e Mbledhjes s\u00eb T\u00eb Dh\u00ebnave p\u00ebr secil\u00ebn nod\u00eb dhe t\u00eb hiqen manualisht t\u00eb gjitha, ose fillimisht t\u00eb hiqen parametrat nga template dhe pastaj t\u00eb hiqen nodet. Nuk e di pse \u00ebsht\u00eb b\u00ebr\u00eb k\u00ebshtu, por n\u00eb mendimin tim, kjo \u00ebsht\u00eb nj\u00eb gj\u00eb shum\u00eb e \u00e7uditshme. Por\u2026 Si\u00e7 \u00ebsht\u00eb.<\/p>\n

    N\u00eb template mund t\u00eb zgjidhni t\u00eb dh\u00ebnat q\u00eb duhen mbledhur dhe ti kopjoni ato n\u00eb nj\u00eb template tjet\u00ebr. Masivisht. Dhe nuk ka nevoj\u00eb t\u00eb kopjoni nga nj\u00eb template n\u00eb tjetrin me dor\u00eb\u2026 Filloj t\u00eb urrej Zabbix..<\/p>\n

    3.7. Pantallona<\/h3>\n

    \nSikurse \u00e7udit\u00ebrisht, NetXMS Wiki p\u00ebr k\u00ebt\u00eb \u00e7\u00ebshtje p\u00ebrmban vet\u00ebm nj\u00eb lidhje n\u00eb youtube: Krijimi i nj\u00eb Pantallone<\/a><\/noindex>, nuk ka asnj\u00eb list\u00eb dhe p\u00ebrshkrim elementesh q\u00eb mund t\u00eb shtohen n\u00eb Pantallon\u00eb. N\u00eb p\u00ebrfundim, gjith\u00e7ka \u00ebsht\u00eb po aq intuitive. Etiketa<\/b> \u2014 \u00ebsht\u00eb thjesht\u2026 mir\u00eb\u2026 etiketa\u2026 Nuk e di si ta p\u00ebrkthej. N\u00eb fjal\u00eb, nj\u00eb fush\u00eb me mbishkrim, p\u00ebrdoret p\u00ebr t\u00eb identifikuar dhe ndar\u00eb element\u00ebt, pasi vet\u00eb element\u00ebt nuk p\u00ebrmbajn\u00eb emra. Grafiku i Linjave<\/b> \u2014 \u00ebsht\u00eb nj\u00eb grafik linear. Grafiku me Bar<\/b> \u2014 \u00ebsht\u00eb nj\u00eb diagram. Shikuesi i Alarmit<\/b> \u2014 lista e paralajm\u00ebrimeve p\u00ebr nodin\/nodet e zgjedhur. N\u00eb fjal\u00eb, emrat flasin p\u00ebr vetveten. <\/p>\n

    Pastaj duhet t\u00eb hapni pronat e panelit dhe t\u00eb konfiguroni pamjet. Na intereson skeda Elementet e Panelit. Numri i kolonave \u2014 \u00ebsht\u00eb numri i kolonave, elementeve, q\u00eb do t\u00eb vendosen horizontalisht. \u00c7do objekt ka pronat e tij, dhe do t'ju rekomandoja t\u00eb hiqni k\u00ebshtu shenj\u00ebn nga pika Layout-Grab excessive vertical space, p\u00ebr t\u00eb minimizuar madh\u00ebsin\u00eb e \u00e7do elementi.<\/p>\n

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

    3.8. Konfigurimi i Veprimeve<\/h3>\n

    \n(Konfigurimi - Konfigurimi i Veprimeve)<\/i>
    \nN\u00eb esenc\u00eb, k\u00ebto jan\u00eb veprime n\u00eb p\u00ebrgjigje t\u00eb aktivizimit t\u00eb triggereve.<\/p>\n

    \"NetXMS
    \n
    \nNetXMS di t\u00eb d\u00ebrgoj\u00eb e-mail, sms, mesazhe xmpp, n\u00eb p\u00ebrgjigje t\u00eb aktivizimit t\u00eb nj\u00eb triggere. K\u00ebtu \u00ebsht\u00eb e thjesht\u00eb \u2014 thjesht plot\u00ebsoni fushat e nevojshme.<\/p>\n

    Gjithashtu mund t\u00eb:<\/p>\n

    \u2014 D\u00ebrgoni njoftimin n\u00eb nj\u00eb server tjet\u00ebr NetXMS
    \n \u2014 Ekzekutoni nj\u00eb komand\u00eb n\u00eb serverin e administrat\u00ebs NetXMS
    \n \u2014 Ekzekutoni nj\u00eb komand\u00eb n\u00eb nyjen me ndihm\u00ebn e agjentit NetXMS
    \n \u2014 Ekzekutoni nj\u00eb skript NXSL (NSXL \u00ebsht\u00eb gjuha e     programimit skriptor t\u00eb NetXMS)<\/a><\/noindex>)<\/p>\n

    Pas krijimit t\u00eb veprimit, mund t'i konfiguroni koh\u00ebn e vones\u00ebs s\u00eb ekzekutimit, si dhe t\u00eb aplikoni nj\u00eb makro p\u00ebr ekzekutim. Koha e vones\u00ebs \u00ebsht\u00eb p\u00ebr t\u00eb mos shqet\u00ebsuar operatorin n\u00eb rast se problemi zgjidhet vetvetiu (p\u00ebr shembull, koha e p\u00ebrgjigjes n\u00eb k\u00ebrkes\u00ebn ping ishte m\u00eb e madhe se vlera e caktuar, por gjat\u00eb kontrollit t\u00eb ardhsh\u00ebm mund t\u00eb kthehet n\u00eb normalitet, k\u00ebshtu q\u00eb pse t\u00eb shqet\u00ebsohemi p\u00ebr gj\u00ebra t\u00eb tilla?).<\/p>\n

    3.9. Kufizimi i t\u00eb drejtave t\u00eb aksesit<\/h3>\n

    \nP\u00ebr \u00e7do objekt mund t\u00eb konfigurohen t\u00eb drejtat e tij t\u00eb aksesit. Edhe p\u00ebr \u00e7do objekt brenda nj\u00eb objekti tjet\u00ebr mund t\u00eb konfigurohen t\u00eb drejtat e aksesit. Kjo lejon shp\u00ebrndarjen shum\u00eb fleksib\u00ebl t\u00eb detyrave dhe mund\u00ebsive t\u00eb monitorimit p\u00ebr grupe t\u00eb ndryshme p\u00ebrdoruesish. Kjo \u00ebsht\u00eb gjith\u00e7ka q\u00eb doja t\u00eb thoja.<\/p>\n

    4. P\u00ebrfundim<\/h3>\n

    \nDua t\u00eb hedh posht\u00eb titullin e artikullit tim. NetXMS nuk \u00ebsht\u00eb p\u00ebr ata q\u00eb jan\u00eb lenes. Thjesht zhvilluesit nuk kan\u00eb theksuar funksionalitetin, si\u00e7 b\u00ebnin disa, por, p\u00ebrve\u00e7 t\u00eb gjithave, u kujdes\u00ebn edhe p\u00ebr nd\u00ebrfaqen.<\/p>\n

    \u0414\u0430\u0432\u0430\u0439\u0442\u0435 \u0442\u0430\u043a. \u042f \u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043b\u0441\u044f Zabbix’\u043e\u043c \u0438 NetXMS. \u041f\u043e \u044d\u0442\u043e\u043c\u0443 \u043f\u0440\u043e\u0441\u0442\u043e \u043d\u0430\u043f\u0438\u0448\u0443 \u0441\u0432\u043e\u0438 \u043e\u0449\u0443\u0449\u0435\u043d\u0438\u044f \u043e\u0442 \u0434\u0432\u0443\u0445 \u044d\u0442\u0438\u0445 \u0441\u0438\u0441\u0442\u0435\u043c.<\/p>\n

    K\u00ebshtu.<\/p>\n

    NetXMS m\u00eb duket nj\u00eb sistem shum\u00eb miq\u00ebsor p\u00ebr p\u00ebrdoruesit. Po\u2026 p\u00ebr administratorin\u2026 po, p\u00ebr administratorin. Ajo ka at\u00eb q\u00eb quhet nj\u00eb nd\u00ebrfaqe intuitivisht e qart\u00eb, dhe kjo \u00ebsht\u00eb super. Nuk ka nevoj\u00eb t\u00eb shkruani formulat tuaja, t\u00eb lexoni shum\u00eb dokumentacion shoq\u00ebrues p\u00ebr t\u00eb aktivizuar kontrollin e pingjeve deri te switch-i ose ndonj\u00eb gj\u00eb tjet\u00ebr t\u00eb thjesht\u00eb. Por. N\u00eb Zabbix kjo gj\u00eb e thjesht\u00eb nuk ndryshon shum\u00eb nga di\u00e7ka q\u00eb \u00ebsht\u00eb v\u00ebrtet e komplikuar, pra, n\u00ebse e keni m\u00ebsuar k\u00ebt\u00eb \u2014 at\u00ebher\u00eb do t\u00eb b\u00ebni t\u00eb gjitha gj\u00ebrat e tjera nj\u00ebsoj. N\u00eb NetXMS, ka sugjerime, shumica e parametrave mund t\u00eb gjenden n\u00eb nd\u00ebrfaqe, t\u00eb zgjidhen me miun dhe t\u00eb konfigurohen. N\u00eb Zabbix duhet t\u00eb m\u00ebsoni, a mundet sistemi t\u00eb b\u00ebj\u00eb k\u00ebt\u00eb dhe at\u00eb, dhe n\u00ebse po \u2014 at\u00ebher\u00eb si shkruhet dhe cil\u00ebt parametra kthehen. Zabbix fiton n\u00eb komunitet dhe tonelata t\u00eb shablloneve p\u00ebr \u00e7do rast\u2026 n\u00ebse n\u00eb k\u00ebt\u00eb mal plehrash do t\u00eb mund t\u00eb gjeni at\u00eb q\u00eb ju nevojitet\u2026 Nga ana tjet\u00ebr, NetXMS gjithashtu ka nj\u00eb grup t\u00eb madh mb\u00ebshtet\u00ebsish dhe shtesash t\u00eb krijuara p\u00ebr k\u00ebt\u00eb sistem. Po ashtu, sistemi ka aft\u00ebsi p\u00ebr t\u00eb monitoruar aplikacionet m\u00eb t\u00eb njohura direkt nga kuti, p\u00ebr t\u00eb cilat \u00ebsht\u00eb njoftuar n\u00eb faqen kryesore t\u00eb projektit.<\/p>\n

    Avantazhi kryesor i NetXMS p\u00ebrball\u00eb Zabbix p\u00ebr mua ishte mund\u00ebsia p\u00ebr t\u00eb nxjerr\u00eb nj\u00eb skenar n\u00eb nyj\u00ebn problematike si p\u00ebrgjigje ndaj aktivizimit t\u00eb trigger-it. N\u00ebse temperatura e CPU-s\u00eb rritet mbi kufirin \u2014 ajo do ta fik\u00eb hostin vet\u00eb. Pastaj do t\u00eb kuptojm\u00eb se \u00e7far\u00eb ka ndodhur. Ndoshta n\u00eb Zabbix ka nj\u00eb gj\u00eb t\u00eb till\u00eb gjithashtu, por nuk kam mundur. Po ashtu si dhe p\u00ebr monitorimin e porteve n\u00eb router-a. E k\u00ebtu b\u00ebhet automatikisht\u2026 Epo, si automatikisht\u2026 Duhet t\u00eb m\u00ebsoni gjuh\u00ebn e skriptimit, dhe gjith\u00e7ka\u2026<\/p>\n

    T\u00eb drejtat e aksesit n\u00eb NetXMS lejojn\u00eb t\u00eb ndahen me shum\u00eb fleksibilitet mund\u00ebsit\u00eb e p\u00ebrdoruesve t\u00eb ndrysh\u00ebm t\u00eb sistemit. Por p\u00ebr t\u00eb konfiguruar gjith\u00e7ka, duhet t\u00eb punoni v\u00ebrtet.<\/p>\n

    N\u00eb p\u00ebrgjith\u00ebsi, sistemet jan\u00eb mjaft t\u00eb ngjashme, dhe mund\u00ebsit\u00eb e tyre, n\u00eb shikim t\u00eb par\u00eb, duken t\u00eb pakt\u00ebn t\u00eb krahasueshme. Megjithat\u00eb, ndjehet se Zabbix mund t\u00eb b\u00ebj\u00eb m\u00eb shum\u00eb, por k\u00ebto mund\u00ebsi jan\u00eb t\u00eb fshehura thell\u00eb n\u00ebn kapak dhe p\u00ebr nj\u00eb administrator t\u00eb zakonsh\u00ebm, \u00abgjith\u00e7ka n\u00eb nj\u00eb\u00bb \u00ebsht\u00eb e pap\u00ebrballueshme. NetXMS duket e thjesht\u00eb dhe e kuptueshme, miq\u00ebsore dhe e k\u00ebndshme.<\/p>\n

    Zabbix ka dokumentacion t\u00eb shk\u00eblqyer, wiki, si t\u00eb b\u00ebni, pyetje t\u00eb shpeshta, praktikat m\u00eb t\u00eb mira, si dhe forume t\u00eb ndryshme, etj., ku mund t\u00eb gjeni p\u00ebrgjigje p\u00ebr pothuajse t\u00eb gjitha pyetjet. Dhe n\u00ebse ka di\u00e7ka \u2014 mund t\u00eb b\u00ebni pyetje tuajat.<\/p>\n

    P\u00ebrmbledhje, do t\u00eb rekomandoja NetXMS p\u00ebr ata q\u00eb sapo po fillojn\u00eb ose p\u00ebr ata q\u00eb nuk kan\u00eb nevoj\u00eb t\u00eb thellohen shum\u00eb n\u00eb monitorimin e gjith\u00e7kaje. Jam i sigurt se n\u00ebse merresh me t\u00eb m\u00eb thell\u00eb, mund t\u00eb arrish v\u00ebzhgime mjaft t\u00eb avancuara.<\/p>\n

    Por megjithat\u00eb, avantazhi kryesor q\u00eb shoh \u00ebsht\u00eb pik\u00ebrisht nd\u00ebrfaqja shum\u00eb miq\u00ebsore dhe leht\u00ebsia e konfigurimit.<\/p>\n

    5. Materialet e p\u00ebrdorura<\/h3>\n

    \nkanali youtube Tomas Kirnak<\/a><\/noindex>
    \n    Wiki NetXMS<\/a><\/noindex>
    \n    K\u00ebrkimi n\u00eb Google<\/a><\/noindex><\/p>\n

    Burimi: 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\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 si nj\u00eb sistem monitorimi p\u00ebr ata q\u00eb jan\u00eb t\u00eb len\u00eb\u2026 dhe pak krahasim me Zabbix | ProHoster","description":"0.","canonical_url":"https:\/\/prohoster.info\/sq\/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":"sq_AL","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\/sq\/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\/sq\/wp-json\/wp\/v2\/posts\/42237","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/comments?post=42237"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/42237\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=42237"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=42237"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=42237"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}