{"id":33660,"date":"2019-10-31T21:53:59","date_gmt":"2019-10-31T18:53:59","guid":{"rendered":"https:\/\/prohoster.info\/blog\/campusinsight-ot-monitoringa-infrastruktury-k-analizu-polzovatelskogo-opyta\/"},"modified":"2019-10-31T21:53:59","modified_gmt":"2019-10-31T18:53:59","slug":"campusinsight-ot-monitoringa-infrastruktury-k-analizu-polzovatelskogo-opyta","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/campusinsight-ot-monitoringa-infrastruktury-k-analizu-polzovatelskogo-opyta","title":{"rendered":"CampusInsight: nga monitorimi i infrastruktur\u00ebs n\u00eb analiz\u00ebn e p\u00ebrvoj\u00ebs s\u00eb p\u00ebrdoruesit","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

Cil\u00ebsia e rrjetit pa kabllor tashm\u00eb p\u00ebrfshihet si standard n\u00eb konceptin e nivelit t\u00eb sh\u00ebrbimit. Dhe n\u00ebse d\u00ebshiron t\u00eb p\u00ebrmbush\u00ebsh k\u00ebrkesat e larta t\u00eb klient\u00ebve, duhen jo vet\u00ebm t\u00eb zgjidhen shpejt problemet q\u00eb lindin n\u00eb rrjet, por gjithashtu t\u00eb parashikohet q\u00eb do t\u00eb ket\u00eb nj\u00eb num\u00ebr t\u00eb madh t\u00eb tyre.<\/p>\n

Si ta b\u00ebjm\u00eb k\u00ebt\u00eb? Vet\u00ebm duke ndjekur at\u00eb q\u00eb \u00ebsht\u00eb v\u00ebrtet e r\u00ebnd\u00ebsishme n\u00eb k\u00ebt\u00eb kontekst \u2014 nd\u00ebrveprimi i p\u00ebrdoruesit me rrjetin pa kabllo.<\/p>\n

\"CampusInsight:
\n<\/a><\/noindex>
\nNgarkesat n\u00eb rrjet vazhdojn\u00eb t\u00eb rriten, dhe kjo ndikon ve\u00e7an\u00ebrisht n\u00eb segmentet pa kabllo \u2014 t\u00eb pakt\u00ebn p\u00ebr shkak t\u00eb hapjes s\u00eb nd\u00ebrfaqeve t\u00eb tyre. Me rritjen e numrit t\u00eb pajisjeve dhe shpejt\u00ebsive t\u00eb transmetimit t\u00eb t\u00eb dh\u00ebnave, problemet shumohen n\u00eb disa nivele. N\u00eb nivelin fizik \u2014 shumica e emetuesve t\u00eb sinjaleve radio ndikojn\u00eb nj\u00ebri-tjetrin, edhe n\u00ebse funksionojn\u00eb n\u00eb disa pjes\u00eb t\u00eb fqinjit t\u00eb spekt\u00ebr frekuencash. N\u00eb nivelin logjik \u2014 numri i madh i pajisjeve t\u00eb lidhura fillon t\u00eb konkurroj\u00eb p\u00ebr t\u00eb filluar transmetimin n\u00eb frekuenc\u00ebn e zgjedhur, duke e rritur vones\u00ebn e dor\u00ebzimit t\u00eb paketimeve p\u00ebr secilin p\u00ebrdorues.\u00a0<\/p>\n

E nj\u00ebkohshme me k\u00ebt\u00eb rriten edhe pritjet e \u00e7do klienti nga p\u00ebrdorimi i rrjetit. Ngarkimi i nj\u00eb faqe n\u00eb shfletues p\u00ebr 5 sekonda, q\u00eb para 20 vjet\u00ebsh dukej si \"kulmi i teknologjis\u00eb\", nuk \u00e7uditet m\u00eb ask\u00ebnd. Klient\u00ebt duan lidhje HD video pa ndalje t\u00eb imazhit.<\/p>\n

Pjes\u00ebrisht, jan\u00eb versionet e reja t\u00eb standardeve t\u00eb transmetimit pa kabllo ato q\u00eb lejojn\u00eb zgjidhjen e k\u00ebsaj \u00e7\u00ebshtjeje, duke p\u00ebrdorur m\u00eb efektivisht spekt\u00ebr frekuencash. \u00c7do version i ardhsh\u00ebm i Wi-Fi<\/a><\/noindex> \u00ebsht\u00eb i orientuar drejt krijimit t\u00eb rrjetesh gjithnj\u00eb e m\u00eb t\u00eb ngarkuara. Por n\u00eb nj\u00eb rrjet masiv, ku funksionojn\u00eb jo nj\u00eb, por disa dhjet\u00ebra pik\u00eb qasjeje, nuk do t\u00eb mund t\u00eb thuash \u00e7\u00ebshtjet te standardi i ardhsh\u00ebm (p\u00ebr m\u00eb tep\u00ebr pajisjet punojn\u00eb n\u00eb m\u00ebnyr\u00eb t\u00eb prapambetur, sapo takojn\u00eb nj\u00eb pajisje m\u00eb t\u00eb vjet\u00ebr). Po ashtu, nuk \u00ebsht\u00eb e mundur t\u00eb vazhdohet me mjete t\u00eb vjetra monitorimi \u2014 ambienti rrjetor po komplikon vazhdimisht.<\/p>\n

Pse monitorimi tradicional tashm\u00eb nuk funksionon<\/h2>\n

\nNj\u00eb klishe klasike, e cila ende ndjek administratoret e t\u00eb gjitha rrjeteve, p\u00ebrfshir\u00eb ato pa kabllo, \u00ebsht\u00eb puna ekskluzivisht sipas k\u00ebrkesave. Nj\u00eb 'alarm' \u00ebsht\u00eb aktivizuar \u2014 ne zgjojm\u00eb dhe merremi me at\u00eb q\u00eb ka ndodhur keq. Nd\u00ebrsa nuk ka 'alarm', mund t\u00eb kufizohemi duke kontrolluar ngarkes\u00ebn n\u00eb komponent\u00ebt kryesor\u00eb \u2013 pajisjet rrjetore dhe ato t\u00eb p\u00ebrdoruesve.\u00a0<\/p>\n

Sipas k\u00ebsaj detyre, mjetet tradicionale t\u00eb monitorimit dhe mir\u00ebmbajtjes funksionojn\u00eb sipas parimeve t\u00eb rregullave strikte dhe nuk tregojn\u00eb gjithmon\u00eb n\u00eb koh\u00eb reale problemet e ekzistuese, p\u00ebr t\u00eb mos p\u00ebrmendur ndonj\u00eb analiz\u00eb parashikuese.\u00a0<\/p>\n

Problemi kryesor k\u00ebtu \u00ebsht\u00eb intervali i mbledhjes s\u00eb t\u00eb dh\u00ebnave. Informacioni mbi gjendjen e lidhjeve rrjet\u00ebsore pa tela mblidhet \u00e7do disa minuta, nd\u00ebrsa incidentet mund t\u00eb ndodhin n\u00eb intervale midis mbledhjes s\u00eb t\u00eb dh\u00ebnave (nj\u00eb shembull i shk\u00eblqyer jan\u00eb shp\u00ebrthimet e rralla t\u00eb ngarkes\u00ebs, q\u00eb \"pezullojn\u00eb\" rrjetin). Pa t\u00eb dh\u00ebna n\u00eb koh\u00eb reale, \u00ebsht\u00eb mjaft e v\u00ebshtir\u00eb t\u00eb kuptohet se \u00e7far\u00eb ishte shkaku themelor i problemit. A \u00ebsht\u00eb menaxhimi i gabuar i mbulimit rrjet\u00ebsor? Apo, ndoshta, nd\u00ebrhyrje t\u00eb jashtme, ndonj\u00ebher\u00eb t\u00eb pam lidhur me biznesin (p.sh., nj\u00eb nj\u00ebsit ushtarake n\u00eb af\u00ebrsi \"prishi\" val\u00ebt). Nuk ka t\u00eb dh\u00ebna ku mund t\u00eb shihen degradimet graduale t\u00eb karakteristikave t\u00eb caktuara t\u00eb rrjetit, dhe prandaj, lokalizimi i problemit nuk \u00ebsht\u00eb aq i leht\u00eb. Ekipi IT do t\u00eb duhet t\u00eb kaloj\u00eb or\u00eb shtes\u00eb duke k\u00ebrkuar nj\u00eb \"gjilp\u00ebr\u00eb n\u00eb nj\u00eb grur\u00eb hane\".
\nNga ana tjet\u00ebr, p\u00ebrdoruesit p\u00ebrfundimtar\u00eb e v\u00ebrejn\u00eb problemin praktikisht menj\u00ebher\u00eb. Gabimi i lidhjes, nd\u00ebrprerja e transmetimit t\u00eb videos \u2013 jan\u00eb tregues t\u00eb shk\u00eblqyer.<\/p>\n

Mjetet klasike t\u00eb monitorimit raportojn\u00eb se paketat rrjet\u00ebsore po kalojn\u00eb. Por ato nuk mund t\u00eb japin p\u00ebrgjigje p\u00ebr pyetjen, n\u00ebse p\u00ebrdoruesi ka zgjidhur problemin e tij.\n<\/p><\/blockquote>\n

\nP\u00ebr t\u00eb marr\u00eb p\u00ebrgjigje p\u00ebr k\u00ebt\u00eb pyetje, do t\u00eb duhet t\u00eb ndryshoni jo vet\u00ebm mjetin, por vet\u00eb qasjen ndaj organizimit t\u00eb monitorimit. Nga puna \"e zjarrfik\u00ebsit\" p\u00ebr k\u00ebrkesat (n\u00eb fakt, kontrolli i performanc\u00ebs dhe ngarkes\u00ebs s\u00eb pajisjeve specifike) kaloni n\u00eb kontrollin e p\u00ebrvoj\u00ebs s\u00eb p\u00ebrdoruesit dhe identifikimin e situatave q\u00eb mund t\u00eb \u00e7ojn\u00eb n\u00eb incidente.<\/p>\n

Kjo transformim n\u00ebnkupton zbatimin e algoritmeve m\u00eb komplekse p\u00ebr p\u00ebrcaktimin e problemeve, sesa thjesht paralajm\u00ebrime t\u00eb arritjes s\u00eb vlerave t\u00eb caktuara. N\u00eb platform\u00ebn e analiz\u00ebs inteligjente t\u00eb rrjetit Huawei CampusInsight, k\u00ebto algoritme bazohet n\u00eb p\u00ebrvoj\u00ebn e sh\u00ebrbimit t\u00eb rrjeteve pa tela dhe teknikave t\u00eb m\u00ebsimit t\u00eb vet\u00eb.<\/p>\n

N\u00ebn kapak CampusInsight<\/h2>\n

\nHuawei CampusInsight \u2013 nj\u00eb platform\u00eb e shkall\u00ebzuar p\u00ebr monitorimin e rrjeteve pa kab\u00ebll t\u00eb \u00e7do shkall\u00eb. E nd\u00ebrtuar mbi nj\u00eb arkitektur\u00eb mikrosh\u00ebrbimesh. \u00c7do sh\u00ebrbim \u00ebsht\u00eb i vendosur n\u00eb disa instanca, mesazhet mes t\u00eb cilave shp\u00ebrndahen nga autobusi i duhur. Instancat shtes\u00eb mund t\u00eb vendosen dinamikisht, duke rritur kapacitetin e instrumentit.<\/p>\n

N\u00eb fakt, CampusInsight mbledh, analizon dhe shfaq t\u00eb dh\u00ebnat n\u00eb UI-n\u00eb e tij n\u00eb pes\u00eb hapa.<\/p>\n

\"CampusInsight:
\n
\nHapi i par\u00eb dhe i dyt\u00eb<\/b> \u00ebsht\u00eb qasja n\u00eb t\u00eb dh\u00ebna (n\u00eb pajisjet q\u00eb sigurojn\u00eb gjenerimin e tyre) dhe mbledhja e \"leximeve\". Duke p\u00ebrdorur mbledhjen e telemetris\u00eb n\u00eb rrjedh\u00eb p\u00ebrmes protokollit GPB nga Google dhe \"tradicionalin\" Syslog (aty ku \u00ebsht\u00eb e mundur), Huawei CampusInsight akumulon t\u00eb dh\u00ebna n\u00eb m\u00ebnyr\u00eb praktikisht t\u00eb menj\u00ebhershme:<\/p>\n