{"id":31014,"date":"2019-10-31T21:38:54","date_gmt":"2019-10-31T18:38:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/trassirovka-servisov-opentracing-i-jaeger\/"},"modified":"2019-10-31T21:38:54","modified_gmt":"2019-10-31T18:38:54","slug":"trassirovka-servisov-opentracing-i-jaeger","status":"publish","type":"post","link":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/trassirovka-servisov-opentracing-i-jaeger","title":{"rendered":"Pra\u0107enje usluga, OpenTracing i Jaeger","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><img decoding=\"async\" alt=\"Pra\u0107enje usluga, OpenTracing i Jaeger\" src=\"\/wp-content\/uploads\/2019\/04\/045800f00c8da9702f62cf3de53df7b6.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nU na\u0161im projektima koristimo mikroservisnu arhitekturu. Kada se pojave uska grla u performansama, \u010desto se tro\u0161i mnogo vremena na pra\u0107enje i analizu logova. Kada se evidentiraju tajmingi pojedina\u010dnih operacija u log datoteku, obi\u010dno je te\u0161ko shvatiti \u0161ta je uzrokovalo pozivanje tih operacija, pratiti redoslijed radnji ili pomak u vremenu jedne operacije u odnosu na drugu izme\u0111u razli\u010ditih usluga. <\/p>\n<p>Kako bismo minimalizovali ru\u010dni rad, odlu\u010dili smo se iskoristiti jedan od alata za pra\u0107enje. O tome kako i za \u0161ta se mo\u017ee koristiti pra\u0107enje i kako smo to radili, rije\u010d je u ovom \u010dlanku. <br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>Koje probleme se mogu rije\u0161iti pomo\u0107u pra\u0107enja<\/h3>\n<p><\/p>\n<ol>\n<li>Prona\u0107i uska grla u performansama unutar jedne usluge, kao i u cijelom stablu izvr\u0161enja izme\u0111u svih uklju\u010denih usluga. Na primjer:\n<ul>\n<li>Mnoge kratke uzastopne pozive izme\u0111u usluga, na primjer, na geokoding ili bazu podataka.<\/li>\n<li>Duga \u010dekanja za unos\/izlaz, na primjer, prenos podataka putem mre\u017ee ili \u010ditanje sa diska.<\/li>\n<li>Dugo procesiranje podataka.<\/li>\n<li>Duge operacije koje zahtijevaju CPU.<\/li>\n<li>Dijelovi koda koji nisu potrebni za postizanje kona\u010dnog rezultata i mogu se ukloniti ili pokrenuti odlo\u017eeno.<\/li>\n<\/ul>\n<\/li>\n<li>Jasno razumjeti u kojem redoslijedu se \u0161ta poziva i \u0161ta se de\u0161ava kada se izvr\u0161ava operacija.<br \/>\n<img decoding=\"async\" alt=\"Pra\u0107enje usluga, OpenTracing i Jaeger\" src=\"\/wp-content\/uploads\/2019\/04\/f22f14599568bff5573fe59eeeaea753.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\nVidljivo je da, na primjer, zahtjev dolazi u uslugu WS -&gt; usluga WS dopunjuje podatke putem usluge R -&gt; zatim \u0161alje zahtjev u uslugu V -&gt; usluga V u\u010ditava mnogo podataka iz usluge R -&gt; odlazi u uslugu P -&gt; usluga P jo\u0161 jednom odlazi u uslugu R -&gt; usluga V ignorira rezultat i ide u uslugu J -&gt; i tek tada vra\u0107a odgovor u uslugu WS, dok u pozadini nastavlja izra\u010dunavati ne\u0161to drugo.<br \/>\nBez takvog traga ili detaljne dokumentacije o cijelom procesu, veoma je te\u0161ko razumjeti \u0161ta se de\u0161ava, prvi put gledaju\u0107i kod, i kod je razbacan po razli\u010ditim uslugama i skriven iza gomile binaire i interface-a.\n<\/li>\n<li>Prikupljanje informacija o stablu izvr\u0161enja za kasniju analizu. U svakoj fazi izvr\u0161avanja u trag se mo\u017ee dodati informacija koja je dostupna u toj fazi, a zatim ispitati koji su ulazni podaci doveli do sli\u010dnog scenarija. Na primjer:\n<ul>\n<li>ID korisnika<\/li>\n<li>Prava<\/li>\n<li>Tip odabrane metode<\/li>\n<li>Log ili gre\u0161ka izvr\u0161enja<\/li>\n<\/ul>\n<\/li>\n<li>Pretvaranje tragova u podskup metrika i dalje analizira u obliku metrika.<\/li>\n<\/ol>\n<h3>\u0160ta mo\u017ee logirati traganje. Span<\/h3>\n<p>U tragovanju postoji pojam span, to je analog jednog loga, u konzoli. Span ima:<\/p>\n<ul>\n<li>Naziv, obi\u010dno naziv metode koja je izvr\u0161ena<\/li>\n<li>Naziv usluge u kojoj je generisan span<\/li>\n<li>Vlastiti jedinstveni ID<\/li>\n<li>Neka metainformacija u obliku key\/value koja je zabilje\u017eena u njemu. Na primjer, parametri metode ili je metoda zavr\u0161ila gre\u0161kom ili ne<\/li>\n<li>Vrijeme po\u010detka i kraja izvr\u0161enja ovog spana<\/li>\n<li>ID roditeljskog spana<\/li>\n<\/ul>\n<p>\nSvaki span se \u0161alje u sakuplja\u010d spana za \u010duvanje u bazu za naknadni pregled \u010dim zavr\u0161i svoje izvr\u0161enje. Kasnije se mo\u017ee izgraditi stablo svih spana povezuju\u0107i po id roditelja. Tokom analize, mo\u017ee se prona\u0107i, na primjer, svi spani u nekoj usluzi koji su trajali du\u017ee od nekog vremena. Zatim, prelaze\u0107i na konkretan span, vidjeti cijelo stablo iznad i ispod ovog spana.<\/p>\n<p><img decoding=\"async\" alt=\"Pra\u0107enje usluga, OpenTracing i Jaeger\" src=\"\/wp-content\/uploads\/2019\/04\/9cc97f1278af60f0efd5e393cd183c5c.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<h3>Opentrace, Jagger i kako smo to implementirali za na\u0161e projekte<\/h3>\n<p>\nPostoji zajedni\u010dki standard <noindex><a rel=\"nofollow\" href=\"https:\/\/opentracing.io\/docs\/overview\/\">Opentrace<\/a><\/noindex>, koji opisuje kako i \u0161ta treba prikupljati, ne vezuju\u0107i tragovanje za konkretnu implementaciju u nekom jeziku. Na primjer, u Javi se sav rad sa tragovima obavlja putem zajedni\u010dkog API-ja Opentrace, a ispod njega mo\u017ee se sakriti, na primjer, Jaeger ili prazna podrazumijevana implementacija koja ni\u0161ta ne radi.<br \/>\nKod nas se koristi <noindex><a rel=\"nofollow\" href=\"https:\/\/www.jaegertracing.io\/\">Jaeger<\/a><\/noindex> kao implementacija Opentrace. Sastoji se od nekoliko komponenti:<\/p>\n<p><img decoding=\"async\" alt=\"Pra\u0107enje usluga, OpenTracing i Jaeger\" src=\"\/wp-content\/uploads\/2019\/04\/1fd4ae8563569271b067861c81101d71.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<\/p>\n<ul>\n<li>Jaeger-agent \u2014 lokalni agent koji obi\u010dno stoji na svakoj ma\u0161ini i u njega logiraju usluge na lokalnu podrazumijevanu port. Ako agenta nema, onda su tragovi svih usluga na ovoj ma\u0161ini obi\u010dno isklju\u010deni.<\/li>\n<li>Jaeger-collector \u2014 u njega svi agenti \u0161alju prikupljene tragove, a on ih sme\u0161ta u odabranu bazu podataka.<\/li>\n<li>Baza podataka \u2014 preferirana je kod njih cassandra, ali mi koristimo elasticsearch, postoje i implementacije za nekoliko drugih baza i in memory implementaciju koja ni\u0161ta ne \u010duva na disku.<\/li>\n<li>Jaeger-query \u2014 to je usluga koja ide u bazu podataka i vra\u0107a ve\u0107 prikupljene tragove za analizu.<\/li>\n<li>Jaeger-ui \u2014 to je web interfejs za pretragu i pregled tragova, ide u jaeger-query.<\/li>\n<\/ul>\n<p><img decoding=\"async\" alt=\"Pra\u0107enje usluga, OpenTracing i Jaeger\" src=\"\/wp-content\/uploads\/2019\/04\/afc415cb5d4f19e7ba18394c2c1a9dd5.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nPosebnom komponentom mo\u017ee se nazvati implementacija opentrace jaeger za konkretne jezike, kroz koju se spani \u0161alju u jaeger-agent.<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/jaegertracing\/jaeger-client-java\">Povezivanje Jagger u Javi<\/a><\/noindex> sve se svodi na implementaciju interfejsa io.opentracing.Tracer, nakon \u010dega \u0107e svi tragovi kroz njega biti poslani stvarnom agentu.<\/p>\n<p><img decoding=\"async\" alt=\"Pra\u0107enje usluga, OpenTracing i Jaeger\" src=\"\/wp-content\/uploads\/2019\/04\/5ce4bdfc06def7e4645bd58163e99dab.png\" style=\"display:block;margin: 0 auto;\" \/><br \/>\n<br \/>\nTako\u0111e, za Spring komponente mo\u017ee se povezati <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/opentracing-contrib\/java-spring-cloud\">opentracing-spring-cloud-starter<\/a><\/noindex> i implementaciju od Jaeger <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/opentracing-contrib\/java-spring-jaeger\">opentracing-spring-jaeger-cloud-starter<\/a><\/noindex> koja automatski konfiguri\u0161e pra\u0107enje za sve \u0161to prolazi kroz te komponente, poput HTTP zahteva u kontrolerima, zahteva prema Bazi podataka putem jdbc itd.<\/p>\n<h3>Logovanje tragova u Javi<\/h3>\n<p>\nNegde na najvi\u0161em nivou mora biti kreiran prvi Span, \u0161to mo\u017ee biti u\u010dinjeno automatski, na primer, od Spring kontrolera prilikom primanja zahteva, ili ru\u010dno ako takvog nema. Zatim se prenosi kroz Scope ni\u017ee. Ako neki metod ispod \u017eeli dodati Span, uzima trenutni activeSpan iz Scope-a, kreira novi Span i postavlja svoj roditeljski span na dobijeni activeSpan, i \u010dini novi Span aktivnim. Kada se pozivaju spoljne usluge, trenutni aktivni span se prenosi njima, i te usluge kreiraju nove spane vezane za ovaj span.<br \/>\nSav rad ide kroz instancu Tracer, koju mo\u017eete dobiti kroz DI mehanizam, ili GlobalTracer.get() kao globalnu promenljivu, ako DI mehanizam ne radi. Podrazumevano, ako tracer nije inicijalizovan, vrati\u0107e se NoopTracer koji ni\u0161ta ne radi.<br \/>\nZatim se iz tracer-a preko ScopeManager-a uzima trenutni scope, kreira se novi scope od trenutnog sa vezom novog spana, a zatim se zatvara stvoreni Scope, koji zatvara stvoreni span i vra\u0107a prethodni Scope u aktivno stanje. Scope je vezan za nit, tako da prilikom vi\u0161edretvenog programiranja ne zaboravite prenositi aktivni span u drugu nit, za dalju aktivaciju Scope-a druge niti u vezi sa tim spanom.<\/p>\n<pre><code class=\"java\">io.opentracing.Tracer tracer = ...; \/\/ GlobalTracer.get()\n\nvoid DoSmth () {\n   try (Scope scope = tracer.buildSpan(\"DoSmth\").startActive(true)) {\n      ...\n   }\n}\nvoid DoOther () {\n    Span span = tracer.buildSpan(\"someWork\").start();\n    try (Scope scope = tracer.scopeManager().activate(span, false)) {\n        \/\/ Radimo stvari.\n    } catch(Exception ex) {\n        Tags.ERROR.set(span, true);\n        span.log(Map.of(Fields.EVENT, \"error\", Fields.ERROR_OBJECT, ex, Fields.MESSAGE, ex.getMessage()));\n    } finally {\n        span.finish();\n    }\n}\n\nvoid DoAsync () {\n    try (Scope scope = tracer.buildSpan(\"ServiceHandlerSpan\").startActive(false)) {\n        ...\n        final Span span = scope.span();\n        doAsyncWork(() -&gt; {\n            \/\/ KORAK 2 IZNAD: ponovo aktivirajte Span u povratnom pozivu, postavljaju\u0107i true na\n            \/\/ startActive() ako\/kada span treba da bude zavr\u0161en.\n            try (Scope scope = tracer.scopeManager().activate(span, false)) {\n                ...\n            }\n        });\n    }\n}<\/code><\/pre>\n<p>Za vi\u0161edretveno programiranje postoje TracedExecutorService i sli\u010dni omota\u010di koji automatski prenose trenutni span u nit prilikom pokretanja asinhronih zadataka:<\/p>\n<pre><code class=\"java\">private ExecutorService executor = new TracedExecutorService(\n    Executors.newFixedThreadPool(10), GlobalTracer.get()\n);<\/code><\/pre>\n<p>Za spoljna http upitavanja postoji <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/opentracing-contrib\/java-apache-httpclient\">TracingHttpClient<\/a><\/noindex><\/p>\n<pre><code class=\"java\">HttpClient httpClient = new TracingHttpClientBuilder().build();<\/code><\/pre>\n<h3>Problemi s kojima smo se susreli<\/h3>\n<p><\/p>\n<ul>\n<li>Bini i DI ne rade uvek ako se tracer ne koristi u servisu ili komponenti, tada <noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/users\/autowired\/\" class=\"user_link\">Autowired<\/a><\/noindex> Tracer mo\u017eda ne\u0107e raditi i bi\u0107e potrebno koristiti GlobalTracer.get().<\/li>\n<li>Anotacije ne rade ako to nije komponenta ili servis, ili ako se poziv metode vr\u0161i iz susedne metode iste klase. Treba biti oprezan, proveriti \u0161ta radi, i koristiti ru\u010dno kreiranje trejza ako @Traced ne funkcioni\u0161e. Tako\u0111e se mo\u017ee dodati dodatni kompajler za java anotacije, tada bi trebalo raditi svuda.<\/li>\n<li>U starim spring i spring boot verzijama ne radi automatska konfiguracija opentracing spring cloud zbog gre\u0161aka u DI, pa ako \u017eelite da automatski rade trejzovi u komponentama springa, to se mo\u017ee u\u010diniti po analogiji sa <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/opentracing-contrib\/java-spring-jaeger\/blob\/master\/opentracing-spring-jaeger-starter\/src\/main\/java\/io\/opentracing\/contrib\/java\/spring\/jaeger\/starter\/JaegerAutoConfiguration.java\">github.com\/opentracing-contrib\/java-spring-jaeger\/blob\/master\/opentracing-spring-jaeger-starter\/src\/main\/java\/io\/opentracing\/contrib\/java\/spring\/jaeger\/starter\/JaegerAutoConfiguration.java<\/a><\/noindex><\/li>\n<li>U groovy-ju ne radi try with resources, obavezno je koristiti try finally.<\/li>\n<li>Svaki servis treba da ima svoj spring.application.name pod kojim \u0107e se logovati trejzovi. Pri \u010demu poseban naziv za produkciju i test, da ih ne bi me\u0161ali.<\/li>\n<li>Ako se koristi GlobalTracer i tomcat, tada svi servisi pokrenuti u tom tomcat-u imaju jedan GlobalTracer, pa \u0107e im na svim biti isto ime servisa.<\/li>\n<li>Prilikom dodavanja trejzova u metodu, treba biti siguran da se ne poziva u petlji vi\u0161e puta. Treba dodati jedan zajedni\u010dki trejz za sve pozive, koji \u0107e zabele\u017eiti ukupno vreme rada. Ina\u010de \u0107e se stvoriti suvi\u0161na optere\u0107enja.<\/li>\n<li>Jednom smo u jaeger-ui pravili prevelike upite na veliki broj trejzova i po\u0161to nismo \u010dekali odgovor, ponovo smo ih pravili. Na kraju je jaeger-query po\u010deo tro\u0161iti mnogo memorije i usporavati elastik. Pomoglo je restartovanje jaeger-query.<\/li>\n<\/ul>\n<h3>Sempliranje, \u010duvanje i pregled trejzova<\/h3>\n<p>\nPostoje tri tipa <noindex><a rel=\"nofollow\" href=\"https:\/\/www.jaegertracing.io\/docs\/1.9\/sampling\/\">sempliranja trejzova<\/a><\/noindex>:<\/p>\n<ol>\n<li>Const koji \u0161alje i \u010duva sve trejzove.<\/li>\n<li>Probabilistic koji filtrira trejzove sa nekom odre\u0111enom verovatno\u0107om.<\/li>\n<li>Ratelimiting koji ograni\u010dava broj tragova u sekundi. Ove parametre mo\u017eete postaviti na klijentu, ili na jaeger-agentu ili u kolektoru. Trenutno u na\u0161em steku validatora koristimo const 1, jer zahtjeva nije mnogo, ali traje dugo. U budu\u0107nosti, ako to uzrokuje prekomjerna optere\u0107enja na sustavu, mo\u017ee se ograni\u010diti.<\/li>\n<\/ol>\n<p>\nAko koristite cassandra, ona po defaultu \u010duva tragove samo dva dana. Kod nas se koristi <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/jaegertracing\/jaeger\/tree\/master\/plugin\/storage\/es\">elasticsearch<\/a><\/noindex> i tragovi se \u010duvaju zauvijek i ne bri\u0161u se. Za svaki dan se kreira poseban indeks, na primjer jaeger-service-2019-03-04. U budu\u0107nosti treba postaviti automatsko \u010di\u0161\u0107enje starih tragova.<\/p>\n<p>Da biste pogledali tragove, potrebno je:<\/p>\n<ul>\n<li>Odabrati uslugu prema kojoj \u017eelite filtrirati tragove, na primjer tomcat7-default za uslugu koja se pokre\u0107e u Tomcat-u i ne mo\u017ee imati svoje ime.<\/li>\n<li>Zatim odabrati operaciju, vremenski period i minimalno vreme operacije, na primjer od 10 sekundi, kako biste uzeli samo duga\u010dka izvr\u0161enja.<br \/>\n<img decoding=\"async\" alt=\"Pra\u0107enje usluga, OpenTracing i Jaeger\" src=\"\/wp-content\/uploads\/2019\/04\/bc712d4aabfe9c2ae961d3b8f9396a42.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<li>Pre\u0107i u jedan od tragova i vidjeti \u0161ta je usporavalo.<br \/>\n<img decoding=\"async\" alt=\"Pra\u0107enje usluga, OpenTracing i Jaeger\" src=\"\/wp-content\/uploads\/2019\/04\/16e9dd11903358f5498fe11034bbf848.png\" style=\"display:block;margin: 0 auto;\" \/><\/li>\n<\/ul>\n<p>\nTako\u0111e, ako je poznat neki ID zahtjeva, trag se mo\u017ee prona\u0107i prema tom ID-ju putem pretrage po oznakama, ako je ovaj ID zabilje\u017een u span-tragu.<\/p>\n<h3>Dokumentacija<\/h3>\n<p><\/p>\n<ul>\n<li>Dokumentacija opentracing <noindex><a rel=\"nofollow\" href=\"https:\/\/opentracing.io\/docs\/overview\/what-is-tracing\/\">opentracing.io\/docs\/overview\/what-is-tracing<\/a><\/noindex><\/li>\n<li>Dokumentacija jaeger <noindex><a rel=\"nofollow\" href=\"https:\/\/www.jaegertracing.io\/docs\/1.10\/\">www.jaegertracing.io\/docs\/1.10<\/a><\/noindex><\/li>\n<li>Povezivanje jaeger java <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/jaegertracing\/jaeger-client-java\">github.com\/jaegertracing\/jaeger-client-java<\/a><\/noindex><\/li>\n<li>Povezivanje spring opentracing<br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/jaegertracing\/jaeger-client-java\">github.com\/jaegertracing\/jaeger-client-java<\/a><\/noindex><br \/>\n<noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/opentracing-contrib\/java-spring-cloud\">github.com\/opentracing-contrib\/java-spring-cloud<\/a><\/noindex><\/li>\n<\/ul>\n<h3>\u010clanci<\/h3>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/carprice\/blog\/340946\/\">habr.com\/ru\/company\/carprice\/blog\/340946<\/a><\/noindex> Jaeger Opentracing i mikroslu\u017ebe u pravom projektu na PHP i Golangu<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/eng.uber.com\/distributed-tracing\/\">eng.uber.com\/distributed-tracing<\/a><\/noindex> Evolving Distributed Tracing at Uber Engineering<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/opentracing.io\/guides\/java\/\">opentracing.io\/guides\/java<\/a><\/noindex><\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/medium.com\/jaegertracing\/running-jaeger-agent-on-bare-metal-d1fc47d31fab\">medium.com\/jaegertracing\/running-jaeger-agent-on-bare-metal-d1fc47d31fab<\/a><\/noindex> Pokretanje Jaeger agenta na hardveru bez virtualizacije<\/li>\n<\/ul>\n<h3>Video<\/h3>\n<p><\/p>\n<ul>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=qg0ENOdP1Lo\">www.youtube.com\/watch?v=qg0ENOdP1Lo<\/a><\/noindex> Kako smo koristili Jaeger i Prometheus za isporuku munjevito brzih korisni\u010dkih upita \u2014 Bryan Boreham<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=WRntQsUajow\">www.youtube.com\/watch?v=WRntQsUajow<\/a><\/noindex> Uvod: Jaeger \u2014 Yuri Shkuro, Uber &amp; Pavol Loffay, Red Hat<\/li>\n<li><noindex><a rel=\"nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=fsHb0qK37bc\">www.youtube.com\/watch?v=fsHb0qK37bc<\/a><\/noindex> Serghei Iakovlev, \u201cMala pri\u010da o velikoj pobjedi: OpenTracing, AWS i Jaeger\u201d<\/li>\n<\/ul>\n<p>Izvor: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/srg\/blog\/446752\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0412 \u043d\u0430\u0448\u0438\u0445 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445 \u043c\u044b \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u0443\u044e \u0430\u0440\u0445\u0438\u0442\u0435\u043a\u0442\u0443\u0440\u0443. \u041f\u0440\u0438 \u0432\u043e\u0437\u043d\u0438\u043a\u043d\u043e\u0432\u0435\u043d\u0438\u0438 \u0443\u0437\u043a\u0438\u0445 \u043c\u0435\u0441\u0442 \u0432 \u043f\u0440\u043e\u0438\u0437\u0432\u043e\u0434\u0438\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u0438 \u0434\u043e\u0441\u0442\u0430\u0442\u043e\u0447\u043d\u043e \u043c\u043d\u043e\u0433\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0438 \u0442\u0440\u0430\u0442\u0438\u0442\u0441\u044f \u043d\u0430 \u043c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043d\u0433 \u0438 \u0440\u0430\u0437\u0431\u043e\u0440 \u043b\u043e\u0433\u043e\u0432. \u041f\u0440\u0438 \u043b\u043e\u0433\u0438\u0440\u043e\u0432\u0430\u043d\u0438\u0438 \u0442\u0430\u0439\u043c\u0438\u043d\u0433\u043e\u0432 \u043e\u0442\u0434\u0435\u043b\u044c\u043d\u044b\u0445 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u0439 \u0432 \u043b\u043e\u0433-\u0444\u0430\u0439\u043b, \u043a\u0430\u043a \u043f\u0440\u0430\u0432\u0438\u043b\u043e, \u0441\u043b\u043e\u0436\u043d\u043e \u043f\u043e\u043d\u044f\u0442\u044c \u0447\u0442\u043e \u043f\u0440\u0438\u0432\u0435\u043b\u043e \u043a \u0432\u044b\u0437\u043e\u0432\u0443 \u044d\u0442\u0438\u0445 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u0439, \u043e\u0442\u0441\u043b\u0435\u0434\u0438\u0442\u044c \u043f\u043e\u0441\u043b\u0435\u0434\u043e\u0432\u0430\u0442\u0435\u043b\u044c\u043d\u043e\u0441\u0442\u044c \u0434\u0435\u0439\u0441\u0442\u0432\u0438\u0439 \u0438\u043b\u0438 \u0441\u043c\u0435\u0449\u0435\u043d\u0438\u0435 \u0432\u043e \u0432\u0440\u0435\u043c\u0435\u043d\u0438 \u043e\u0434\u043d\u043e\u0439 \u043e\u043f\u0435\u0440\u0430\u0446\u0438\u0438 \u043e\u0442\u043d\u043e\u0441\u0438\u0442\u0435\u043b\u044c\u043d\u043e \u0434\u0440\u0443\u0433\u043e\u0439 \u0432 \u0440\u0430\u0437\u043d\u044b\u0445 \u0441\u0435\u0440\u0432\u0438\u0441\u0430\u0445. \u0414\u043b\u044f \u043c\u0438\u043d\u0438\u043c\u0438\u0437\u0430\u0446\u0438\u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":22990,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31014","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0412 \u043d\u0430\u0448\u0438\u0445 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445 \u043c\u044b \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u0443\u044e.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/trassirovka-servisov-opentracing-i-jaeger\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"bs_BA\" \/>\n\t\t<meta property=\"og:site_name\" content=\"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\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u0422\u0440\u0430\u0441\u0441\u0438\u0440\u043e\u0432\u043a\u0430 \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432, OpenTracing \u0438 Jaeger | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0412 \u043d\u0430\u0448\u0438\u0445 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445 \u043c\u044b \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u0443\u044e.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/trassirovka-servisov-opentracing-i-jaeger\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2019-10-31T18:38:54+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:38:54+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Trafika usluga, OpenTracing i Jaeger | ProHoster","description":"U na\u0161im projektima koristimo mikroslu\u017ebenu arhitekturu.","canonical_url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/trassirovka-servisov-opentracing-i-jaeger","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"bs_BA","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\u0422\u0440\u0430\u0441\u0441\u0438\u0440\u043e\u0432\u043a\u0430 \u0441\u0435\u0440\u0432\u0438\u0441\u043e\u0432, OpenTracing \u0438 Jaeger | ProHoster","og:description":"\u0412 \u043d\u0430\u0448\u0438\u0445 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445 \u043c\u044b \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u0435\u043c \u043c\u0438\u043a\u0440\u043e\u0441\u0435\u0440\u0432\u0438\u0441\u043d\u0443\u044e.","og:url":"https:\/\/prohoster.info\/bs\/blog\/administrirovanie\/trassirovka-servisov-opentracing-i-jaeger","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:38:54+00:00","article:modified_time":"2019-10-31T18:38:54+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31014","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 04:06:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:26:04","updated":"2026-01-21 04:06:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/31014","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/comments?post=31014"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/posts\/31014\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media\/22990"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/media?parent=31014"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/categories?post=31014"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/bs\/wp-json\/wp\/v2\/tags?post=31014"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}