{"id":34430,"date":"2019-10-31T21:58:16","date_gmt":"2019-10-31T18:58:16","guid":{"rendered":"https:\/\/prohoster.info\/blog\/pochemu-inzhenery-ne-zabotyatsya-o-monitoringe-prilozhenij\/"},"modified":"2019-10-31T21:58:16","modified_gmt":"2019-10-31T18:58:16","slug":"pochemu-inzhenery-ne-zabotyatsya-o-monitoringe-prilozhenij","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pochemu-inzhenery-ne-zabotyatsya-o-monitoringe-prilozhenij","title":{"rendered":"Pse inxhinier\u00ebt nuk e kuptojn\u00eb r\u00ebnd\u00ebsin\u00eb e monitorimit t\u00eb aplikacioneve?","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

G\u00ebzuar t\u00eb premten! Miq, sot vazhdojm\u00eb serin\u00eb e publikimeve q\u00eb i kushtohen kursit \u00abPraktikat dhe mjetet DevOps\u00bb<\/a><\/noindex>, sepse m\u00ebsimet n\u00eb grupin e ri p\u00ebr kursin fillojn\u00eb tashm\u00eb n\u00eb fund t\u00eb jav\u00ebs s\u00eb ardhshme. Pra, le t\u00eb fillojm\u00eb!<\/p>\n

\"Pse
\n
\nMonitorimi \u2014 \u00ebsht\u00eb thjesht<\/b>. Kjo \u00ebsht\u00eb nj\u00eb fakt i njohur. Aktivizoni Nagios, nisni NRPE n\u00eb sistemin e larg\u00ebt, konfiguroni Nagios p\u00ebr portin NRPE TCP 5666 dhe keni monitorim.<\/p>\n

\u00cbsht\u00eb kaq e leht\u00eb, saq\u00eb nuk \u00ebsht\u00eb interesante. Tani keni metrikat baz\u00eb p\u00ebr koh\u00ebn e procesorit, sistemin e diskut, memorjen e operativ, t\u00eb cilat vijn\u00eb me default n\u00eb Nagios dhe NRPE. Por n\u00eb t\u00eb v\u00ebrtet\u00eb, kjo nuk \u00ebsht\u00eb \u00abmonitorim\u00bb si i till\u00eb. Kjo \u00ebsht\u00eb vet\u00ebm fillimi.<\/p>\n

(Zakonisht vendosin PNP4Nagios, RRDtool dhe Thruk, konfiguroni njoftime n\u00eb Slack dhe shkojn\u00eb drejtp\u00ebrdrejt n\u00eb nagiosexchange, por le t\u00eb kalojm\u00eb k\u00ebt\u00eb p\u00ebr momentin).<\/a><\/noindex><\/p>\n

Nj\u00eb monitorim i mir\u00eb<\/b> n\u00eb t\u00eb v\u00ebrtet\u00eb \u00ebsht\u00eb mjaft i nd\u00ebrlikuar, duhet v\u00ebrtet t\u00eb dini brend\u00ebsin\u00eb e aplikacionit q\u00eb po monitoroni.<\/p>\n

A \u00ebsht\u00eb monitorimi i v\u00ebshtir\u00eb?<\/h2>\n

\n\u00c7do server, qoft\u00eb Linux apo Windows, p\u00ebr nga p\u00ebrkufizimi do t\u00eb sh\u00ebrbej\u00eb p\u00ebr ndonj\u00eb q\u00ebllim. Apache, Samba, Tomcat, ruajtja e skedar\u00ebve, LDAP \u2014 t\u00eb gjitha k\u00ebto sh\u00ebrbime jan\u00eb m\u00eb shum\u00eb ose m\u00eb pak unike n\u00eb nj\u00eb ose disa m\u00ebnyra. Secili ka funksionin e vet, ve\u00e7orit\u00eb e saj. Ka m\u00ebnyra t\u00eb ndryshme p\u00ebr t\u00eb marr\u00eb metrika, KPI (t\u00eb dh\u00ebna ky\u00e7e t\u00eb performanc\u00ebs), t\u00eb cilat ju interesojn\u00eb kur serveri \u00ebsht\u00eb n\u00ebn ngarkes\u00eb.<\/p>\n

\"Pse
\nAutori i fotos Luke Chesser<\/a><\/noindex> n\u00eb Unsplash
\n<\/a><\/noindex><\/i><\/p>\n

(do t\u00eb doja q\u00eb dashboard-et e mia t\u00eb ishin t\u00eb ngjyrosura n\u00eb ngjyr\u00eb t\u00eb kalt\u00ebr neon \u2014 duke shp\u00ebrthyer \u00ebndrrat \u2014\u2026 hmm\u2026)<\/p>\n

Cdo program q\u00eb ofron sh\u00ebrbime duhet t\u00eb ket\u00eb nj\u00eb mekaniz\u00ebm p\u00ebr mbledhjen e metrikave. Apache ka modulin mod-status<\/code>, i cili tregon faqen e gjendjes s\u00eb serverit. Nginx ka stub_status<\/code>. Tomcat ka JMX ose aplikacione t\u00eb ve\u00e7anta Web q\u00eb tregojn\u00eb metrikat kryesore. N\u00eb MySQL ka komand\u00ebn \u00abshow global status\u00bb etj.
\nPse nuk i p\u00ebrfshijn\u00eb programuesit mekanizma t\u00eb till\u00eb n\u00eb aplikacionet q\u00eb krijojn\u00eb?<\/p>\n

A e b\u00ebjn\u00eb k\u00ebt\u00eb vet\u00ebm programuesit?<\/h2>\n

\nNj\u00eb nivel i caktuar indiference ndaj integrimit t\u00eb metrikave nuk kufizohet vet\u00ebm te programuesit. Kam punuar n\u00eb kompani ku zhvillonin aplikacione duke p\u00ebrdorur Tomcat dhe nuk l\u00ebshonin asnj\u00eb metrik\u00eb t\u00eb veta, asnj\u00eb log t\u00eb aktivitetit t\u00eb sh\u00ebrbimit, p\u00ebrve\u00e7 regjistrave t\u00eb p\u00ebrgjithsh\u00ebm t\u00eb gabimeve t\u00eb Tomcat. Disa programues gjenerojn\u00eb nj\u00eb mori logs, t\u00eb cilat nuk kan\u00eb asnj\u00eb kuptim p\u00ebr administratorin e sistemit, i cili ka pasur fatin t'i lexoj\u00eb n\u00eb or\u00ebn 3:15 t\u00eb m\u00ebngjesit.<\/p>\n

\"Pse
\nAutori i fotos Tim Gouw<\/a><\/noindex> n\u00eb Unsplash<\/a><\/noindex><\/i><\/p>\n

Inxhinier\u00ebt sistemor\u00eb, t\u00eb cil\u00ebt lejojn\u00eb q\u00eb produkte t\u00eb tilla t\u00eb dalin n\u00eb treg, gjithashtu duhet t\u00eb mbajn\u00eb nj\u00eb p\u00ebrgjegj\u00ebsi t\u00eb caktuar p\u00ebr situat\u00ebn. Pak inxhinier\u00eb sistemor\u00eb kan\u00eb koh\u00eb dhe jan\u00eb t\u00eb interesuar t\u00eb p\u00ebrpiqen t\u00eb fitojn\u00eb metrika kuptimplota nga log\u00ebt, pa kontekstin e k\u00ebtyre metricave dhe mund\u00ebsin\u00eb p\u00ebr t'i interpretuar ato n\u00eb drit\u00ebn e aktivitetit t\u00eb aplikacionit. Disa nuk e kuptojn\u00eb se \u00e7far\u00eb dobi mund t\u00eb ken\u00eb nga kjo, p\u00ebrve\u00e7 treguesve t\u00eb tipit \"di\u00e7ka aktualisht (ose do t\u00eb jet\u00eb s\u00eb shpejti) nuk \u00ebsht\u00eb n\u00eb rregull\".<\/p>\n

Ndryshimi i mend\u00ebsis\u00eb mbi nevoj\u00ebn p\u00ebr metrika duhet t\u00eb ndodh\u00eb jo vet\u00ebm n\u00eb mesin e zhvilluesve, por edhe n\u00eb mesin e inxhinier\u00ebve sistemor\u00eb.<\/p>\n

P\u00ebr \u00e7do inxhinier sistemor, i cili duhet jo vet\u00ebm t\u00eb reagoj\u00eb n\u00eb ngjarje kritike, por edhe t\u00eb garantoj\u00eb q\u00eb ato t\u00eb mos ndodhin, mungesa e metricave zakonisht \u00ebsht\u00eb nj\u00eb penges\u00eb p\u00ebr k\u00ebt\u00eb.<\/p>\n

Megjithat\u00eb, inxhinier\u00ebt sistemor\u00eb zakonisht nuk kalojn\u00eb n\u00ebp\u00ebr kod, duke fituar para p\u00ebr kompanin\u00eb e tyre. Ata kan\u00eb nevoj\u00eb p\u00ebr zhvillues t\u00eb lider\u00ebve q\u00eb kuptojn\u00eb r\u00ebnd\u00ebsin\u00eb e p\u00ebrgjegj\u00ebsis\u00eb s\u00eb inxhinier\u00ebve sistemor\u00eb n\u00eb zbulimin e problemeve, rritjen e nd\u00ebrgjegj\u00ebsimit p\u00ebr problemet e performanc\u00ebs dhe gj\u00ebra t\u00eb tjera t\u00eb ngjashme.<\/p>\n

Kjo e gj\u00ebja devops<\/h2>\n

\nMentaliteti devops p\u00ebrshkruan sinergjin\u00eb e mend\u00ebsis\u00eb s\u00eb zhvilluesve (dev) dhe operacioneve (ops). \u00c7do kompani q\u00eb thot\u00eb se \"b\u00ebn\u00eb devops\" duhet t\u00eb:<\/p>\n

    \n
  1. thot\u00eb ato q\u00eb ata, me shum\u00eb mund\u00ebsi, nuk po e b\u00ebjn\u00eb (aluzion n\u00eb memin nga filmi \"Princesha Nefesuar\" \u2014 \"Nuk mendoj se kjo do t\u00eb thot\u00eb at\u00eb q\u00eb mendon se do t\u00eb thot\u00eb!\")<\/li>\n
  2. nxis\u00eb pozitat e p\u00ebrmir\u00ebsimit t\u00eb vazhduesh\u00ebm t\u00eb produktit.<\/li>\n<\/ol>\n

    \nNuk mund t\u00eb p\u00ebrmir\u00ebsosh produktin dhe t\u00eb dish se ai \u00ebsht\u00eb p\u00ebrmir\u00ebsuar, n\u00ebse nuk di si funksionon aktualisht. Nuk do t\u00eb jesh n\u00eb gjendje t\u00eb kuptosh se si funksionon produkti, n\u00ebse nuk kupton si funksionojn\u00eb komponent\u00ebt e tij, sh\u00ebrbimet nga t\u00eb cilat varet, dhimbjet e tij kryesore dhe ngushticat.
    \nN\u00ebse nuk v\u00ebzhgon ngushticat e mundshme, nuk do t\u00eb jesh n\u00eb gjendje t\u00eb ndjek\u00ebsh teknik\u00ebn \"Pes\u00eb pse\" gjat\u00eb shkrimit t\u00eb Postmortem-it. Nuk do t\u00eb jesh n\u00eb gjendje t\u00eb mbledh\u00ebsh gjith\u00e7ka n\u00eb nj\u00eb ekran, p\u00ebr t\u00eb par\u00eb si funksionon produkti ose p\u00ebr t\u00eb ditur se si duket \"m\u00eb n\u00eb rregull dhe i lumtur\".<\/p>\n

    L\u00ebvizja majtas, MAJLAT, E THA LEEEEEEEE\u2014 <\/h2>\n

    \nP\u00ebr mua, nj\u00eb nga parimet ky\u00e7e t\u00eb Devops \u00ebsht\u00eb \"L\u00ebvizja majtas\" (shift left). L\u00ebvizja majtas n\u00eb k\u00ebt\u00eb kontekst do t\u00eb thot\u00eb zhvendosja e mund\u00ebsis\u00eb (dhe jo p\u00ebrgjegj\u00ebsin\u00eb<\/b>, por mund\u00ebsi) p\u00ebr t\u00eb b\u00ebr\u00eb at\u00eb p\u00ebr t\u00eb cil\u00ebn kujdesen zakonisht inxhinier\u00ebt sistemor\u00eb, p\u00ebr shembull, t\u00eb krijojn\u00eb matjet e performanc\u00ebs, t\u00eb p\u00ebrdorin m\u00eb efektiv logjet etj., n\u00eb procesin e d\u00ebrgimit t\u00eb software-it (Software Delivery Life Cycle).<\/p>\n

    \"Pse
    \nAutori i fotos     NESA nga Makers<\/a><\/noindex> n\u00eb Unsplash<\/a><\/noindex><\/i><\/p>\n

    Zhvilluesit e software-it duhet t\u00eb ken\u00eb mund\u00ebsin\u00eb t\u00eb p\u00ebrdorin dhe t\u00eb din\u00eb mjetet e monitorimit q\u00eb p\u00ebrdor kompania, p\u00ebr t\u00eb realizuar monitorimin n\u00eb t\u00eb gjitha format e tij, metricat, logimin, nd\u00ebrfaqet e monitorimit dhe, \u00e7ka \u00ebsht\u00eb m\u00eb e r\u00ebnd\u00ebsishme, t\u00eb v\u00ebzhgojn\u00eb si funksionon produkti i tyre n\u00eb prodhim<\/i>. Ju nuk mund ta detyroni zhvilluesin t\u00eb angazhohet dhe t\u00eb investoj\u00eb koh\u00eb n\u00eb monitorim, derisa ata t\u00eb ken\u00eb mund\u00ebsin\u00eb t\u00eb shohin metricat dhe t\u00eb ndikojn\u00eb n\u00eb at\u00eb se si duken, si do t'i prezantoj\u00eb ato CTO-i n\u00eb bisedimin e ardhsh\u00ebm etj.<\/p>\n

    N\u00eb shkurt<\/h2>\n

    <\/p>\n

      \n
    1. Sillni kalin te uji. Tregoni zhvilluesve sa shum\u00eb probleme mund t\u00eb shmangin p\u00ebr veten e tyre, ndihmohuni t\u00eb identifikojn\u00eb KPI-t\u00eb dhe metricat e duhura p\u00ebr aplikacionet e tyre, n\u00eb m\u00ebnyr\u00eb q\u00eb t\u00eb ket\u00eb m\u00eb pak t\u00eb ulur nga pronari i produktit, i cili \u00ebsht\u00eb i qortuar nga CTO. Njihni ata me qet\u00ebsi dhe but\u00ebsi. N\u00ebse kjo nuk funksionon, at\u00ebher\u00eb \u00ebsht\u00eb nevoja t\u00eb korruptoni, k\u00ebrc\u00ebnoni dhe bindni ose ata ose pronarin e produktit p\u00ebr t\u00eb realizuar sa m\u00eb shpejt marrjen e k\u00ebtyre metricave nga aplikacionet, dhe pastaj vizatoni grafika. Kjo do t\u00eb jet\u00eb sfiduese, pasi nuk do t\u00eb konsiderohet si prioritet, dhe n\u00eb hart\u00ebn e produktit do t\u00eb ket\u00eb shum\u00eb projekte q\u00eb presin t\u00eb realizohen dhe sjellin t\u00eb ardhura. Prandaj, do t'ju nevojitet nj\u00eb arsyetim ekonomik p\u00ebr t\u00eb justifikuar koh\u00ebn dhe burimet e shpenzuara p\u00ebr implementimin e monitorimit n\u00eb produkt.<\/li>\n
    2. Ndihmni inxhinier\u00ebve sistemik\u00eb t\u00eb flen\u00eb mir\u00eb. Tregoni atyre se p\u00ebrdorimi i list\u00ebs s\u00eb kontrollit \"n\u00eb l\u00ebshimin e produktit\" p\u00ebr \u00e7do produkt t\u00eb l\u00ebshuar \u00ebsht\u00eb e mir\u00eb. Dhe kontrollimi i metrikave p\u00ebr t\u00eb gjitha aplikacionet n\u00eb prodhim do t\u00eb ndihmoj\u00eb q\u00eb ata t\u00eb flen\u00eb mir\u00eb n\u00eb nat\u00eb, duke u lejuar zhvilluesve t\u00eb shohin se \u00e7far\u00eb nuk funksionon dhe ku. Megjithat\u00eb, m\u00ebnyra e duhur p\u00ebr t\u00eb irrituar dhe shqet\u00ebsuar \u00e7do zhvillues, pronar produkti dhe drejtori teknik \u00ebsht\u00eb t\u00eb vulosni gjeografi dhe t\u00eb shkoni p\u00ebrpara. Kjo sjellje do t\u00eb ndikoj\u00eb n\u00eb dat\u00ebn e l\u00ebshimit t\u00eb \u00e7do produkti, n\u00ebse pritet deri n\u00eb minut\u00ebn e fundit, prandaj b\u00ebni p\u00ebrs\u00ebri nj\u00eb l\u00ebvizje t\u00eb majt\u00eb dhe p\u00ebrfshini k\u00ebto \u00e7\u00ebshtje sa m\u00eb shpejt n\u00eb planin e projektit. N\u00ebse \u00ebsht\u00eb e nevojshme, kaloni n\u00eb takimet q\u00eb i kushtohen produktit. Vishni mustaqe false dhe ndonj\u00eb gj\u00eb t\u00eb till\u00eb, kjo nuk do t\u00eb d\u00ebshtoj\u00eb kurr\u00eb. Raportoni problemet tuaja, tregoni p\u00ebrfitimet e dukshme dhe evangelizoni.<\/li>\n
    3. Sigurohuni q\u00eb si zhvilluesit (dev), ashtu edhe operacionet (ops) t\u00eb kuptojn\u00eb r\u00ebnd\u00ebsin\u00eb dhe pasojat e kalimit t\u00eb metrikave t\u00eb produktit n\u00eb \"zon\u00ebn e kuqe\". Mos e lini operacionin si roje t\u00eb vetme t\u00eb funksionalitetit t\u00eb produktit, sigurohuni q\u00eb zhvilluesit t\u00eb p\u00ebrfshihen gjithashtu (#productsquads).<\/li>\n
    4. Log-et jan\u00eb nj\u00eb gj\u00eb e shk\u00eblqyer, por metrikat gjithashtu. Bashkoni ato dhe mos lejoni q\u00eb log-et tuaja t\u00eb kthehen n\u00eb mbeturina n\u00eb nj\u00eb top gjigand zjarrfik\u00ebs pa kuptim. Shpjegoni dhe tregoni zhvilluesve pse askush p\u00ebrve\u00e7 tyre nuk do t\u00eb kuptoj\u00eb log-et e tyre, tregoni atyre si \u00ebsht\u00eb t\u00eb shohin log-e t\u00eb padobishme n\u00eb or\u00ebn 3:15 t\u00eb m\u00ebngjesit.<\/li>\n<\/ol>\n

      \n\"Pse
      \nAutori i fotos       Marko Horvat<\/a><\/noindex> n\u00eb Unsplash<\/a><\/noindex><\/p>\n

      Kjo \u00ebsht\u00eb gjith\u00e7ka. Materiali i ri do t\u00eb dal\u00eb jav\u00ebn e ardhshme. N\u00ebse d\u00ebshironi t\u00eb m\u00ebsoni m\u00eb shum\u00eb rreth kursit, ju ftojm\u00eb n\u00eb dit\u00ebn e hapur<\/a><\/noindex>, i cili do t\u00eb zhvillohet tashm\u00eb t\u00eb h\u00ebn\u00ebn. Dhe tani, tradicionalisht presim komentet tuaja.
      \n
      Burimi:       habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"

      \u0412\u0441\u0435\u0445 \u0441 \u043f\u044f\u0442\u043d\u0438\u0446\u0435\u0439! \u0414\u0440\u0443\u0437\u044c\u044f, \u0441\u0435\u0433\u043e\u0434\u043d\u044f \u043c\u044b \u043f\u0440\u043e\u0434\u043e\u043b\u0436\u0430\u0435\u043c \u0441\u0435\u0440\u0438\u044e \u043f\u0443\u0431\u043b\u0438\u043a\u0430\u0446\u0438\u0439 \u043f\u043e\u0441\u0432\u044f\u0449\u0435\u043d\u043d\u044b\u0445 \u043a\u0443\u0440\u0441\u0443 \u00abDevOps \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 \u0438 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b\u00bb, \u043f\u043e\u0442\u043e\u043c\u0443 \u043a\u0430\u043a \u0437\u0430\u043d\u044f\u0442\u0438\u044f \u0432 \u043d\u043e\u0432\u043e\u0439 \u0433\u0440\u0443\u043f\u043f\u0435 \u043f\u043e \u043a\u0443\u0440\u0441\u0443 \u0441\u0442\u0430\u0440\u0442\u0443\u044e\u0442 \u0443\u0436\u0435 \u0432 \u043a\u043e\u043d\u0446\u0435 \u0441\u043b\u0435\u0434\u0443\u044e\u0449\u0435\u0439 \u043d\u0435\u0434\u0435\u043b\u0438. \u0418\u0442\u0430\u043a, \u043d\u0430\u0447\u043d\u0451\u043c! \u041c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433 \u2014 \u044d\u0442\u043e \u043f\u0440\u043e\u0441\u0442\u043e. \u042d\u0442\u043e \u0438\u0437\u0432\u0435\u0441\u0442\u043d\u044b\u0439 \u0444\u0430\u043a\u0442. \u041f\u043e\u0434\u043d\u0438\u043c\u0438\u0442\u0435 Nagios, \u0437\u0430\u043f\u0443\u0441\u0442\u0438\u0442\u0435 NRPE \u043d\u0430 \u0443\u0434\u0430\u043b\u0451\u043d\u043d\u043e\u0439 \u0441\u0438\u0441\u0442\u0435\u043c\u0435, \u043d\u0430\u0441\u0442\u0440\u043e\u0439\u0442\u0435 Nagios \u043d\u0430 \u043f\u043e\u0440\u0442 NRPE TCP 5666 \u0438 \u0443 \u0432\u0430\u0441 […]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":25942,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-34430","post","type-post","status-publish","format-standard","has-post-thumbnail","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\udd47Pse inxhinier\u00ebt nuk u interesohen monitorimit t\u00eb aplikacioneve? | ProHoster","description":"T\u00eb gjith\u00ebve nj\u00eb t\u00eb premte t\u00eb mbar\u00eb!","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pochemu-inzhenery-ne-zabotyatsya-o-monitoringe-prilozhenij","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\udd47\u041f\u043e\u0447\u0435\u043c\u0443 \u0438\u043d\u0436\u0435\u043d\u0435\u0440\u044b \u043d\u0435 \u0437\u0430\u0431\u043e\u0442\u044f\u0442\u0441\u044f \u043e \u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433\u0435 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439? | ProHoster","og:description":"\u0412\u0441\u0435\u0445 \u0441 \u043f\u044f\u0442\u043d\u0438\u0446\u0435\u0439!","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/pochemu-inzhenery-ne-zabotyatsya-o-monitoringe-prilozhenij","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-10-31T18:58:16+00:00","article:modified_time":"2019-10-31T18:58:16+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"34430","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-21 19:16:10","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 02:21:35","updated":"2026-01-21 19:16:10","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\/34430","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=34430"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/34430\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/25942"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=34430"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=34430"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=34430"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}