{"id":56206,"date":"2020-02-07T00:00:00","date_gmt":"2020-02-06T21:00:00","guid":{"rendered":"https:\/\/prohoster.info\/blog\/blog_prohoster\/loki-sbor-logov-ispolzuya-podhod-prometheus"},"modified":"2021-02-01T11:41:00","modified_gmt":"2021-02-01T09:41:00","slug":"loki-sbor-logov-ispolzuya-podhod-prometheus","status":"publish","type":"post","link":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/loki-sbor-logov-ispolzuya-podhod-prometheus","title":{"rendered":"Loki \u2014 colector de log-uri, utiliz\u00e2nd abordarea Prometheus","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><i>Salutare, comunitate! \u00cen anticiparea \u00eenceperii unui nou curs <noindex><a rel=\"nofollow\" href=\"https:\/\/otus.pw\/P37L\/\">\u201ePracticile \u0219i instrumentele DevOps\u201d<\/a><\/noindex> v-am preg\u0103tit o traducere a unui material interesant.<\/i><\/p>\n<p>Acest articol este o introducere scurt\u0103 \u00een Loki. Proiectul Loki <noindex><a rel=\"nofollow\" href=\"https:\/\/grafana.com\/oss\/loki\/\">este sus\u021binut de Grafana<\/a><\/noindex> \u0219i are ca scop colectarea centralizat\u0103 a log-urilor (de pe servere sau containere).<\/p>\n<p>Principala surs\u0103 de inspira\u021bie pentru Loki a fost <noindex><a rel=\"nofollow\" href=\"http:\/\/prometheus.io\/\">Prometheus<\/a><\/noindex> ideea de a aplica metodele sale de gestionare a log-urilor:<\/p>\n<ul>\n<li>utilizarea etichetelor (labels) pentru stocarea datelor<\/li>\n<li>consumul redus de resurse<\/li>\n<\/ul>\n<p>Ne vom \u00eentoarce la principiile de func\u021bionare ale Prometheus \u0219i vom oferi c\u00e2teva exemple de utilizare a acestora \u00een contextul Kubernetes.<\/p>\n<h3>C\u00e2teva cuvinte despre Prometheus<\/h3>\n<p>Pentru a \u00een\u021belege pe deplin cum func\u021bioneaz\u0103 Loki, este important s\u0103 facem un pas \u00eenapoi \u0219i s\u0103 ne amintim pu\u021bin despre Prometheus.<\/p>\n<p>Una dintre caracteristicile distinctive ale Prometheus este extragerea metricilor din punctele de colectare (prin exportoare) \u0219i salvarea acestora \u00een TSDB (Time Series Data Base, baza de date a seriilor temporale) cu ad\u0103ugarea de metadate sub form\u0103 de etichete.<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<h3>De ce este necesar<\/h3>\n<p>\u00cen ultima vreme, Prometheus a devenit standardul de facto \u00een lumea containerelor \u0219i Kubernetes: instalarea sa este foarte simpl\u0103, iar \u00een clusterul Kubernetes exist\u0103 deja un endpoint pentru Prometheus. De asemenea, Prometheus poate extrage metrici din aplica\u021biile desf\u0103\u0219urate \u00een containere, p\u0103str\u00e2nd anumite etichete. Prin urmare, monitorizarea aplica\u021biilor este foarte u\u0219or de realizat.<\/p>\n<p>Din p\u0103cate, nu exist\u0103 \u00eenc\u0103 o solu\u021bie \u201eready to use\u201d pentru gestionarea log-urilor, iar tu trebuie s\u0103 g\u0103se\u0219ti o solu\u021bie pentru tine:<\/p>\n<ul>\n<li>un serviciu cloud gestionat pentru centralizarea log-urilor (AWS, Azure sau Google)<\/li>\n<li>un serviciu de monitorizare \u201emonitoring as a service\u201d (de exemplu, Datadog)<\/li>\n<li>crearea propriului serviciu de colectare a log-urilor.<\/li>\n<\/ul>\n<p>Pentru a treia op\u021biune, am folosit \u00een mod tradi\u021bional Elasticsearch, de\u0219i nu am fost \u00eentotdeauna mul\u021bumit de el (\u00een special de dificultatea \u0219i complexitatea configur\u0103rii).<\/p>\n<p>Loki a fost proiectat cu scopul de a simplifica implementarea conform urm\u0103toarelor principii:<\/p>\n<ul>\n<li>s\u0103 fie u\u0219or de \u00eenceput<\/li>\n<li>s\u0103 consume pu\u021bine resurse<\/li>\n<li>s\u0103 func\u021bioneze autonom f\u0103r\u0103 \u00eentre\u021binere special\u0103<\/li>\n<li>s\u0103 serveasc\u0103 drept complement pentru Prometheus \u00een investigarea erorilor<\/li>\n<\/ul>\n<p>Cu toate acestea, aceast\u0103 simplitate este realizat\u0103 prin anumite compromisuri. Unul dintre ele este neindexarea con\u021binutului. Prin urmare, c\u0103utarea \u00een text nu este foarte eficient\u0103 sau bogat\u0103 \u0219i nu permite statistici relevante despre con\u021binutul textului. Dar, deoarece Loki dore\u0219te s\u0103 fie echivalentul lui grep \u0219i un complement pentru Prometheus, aceasta nu este o deficien\u021b\u0103.<\/p>\n<h3>Investigarea incidentelor<\/h3>\n<p>Pentru a \u00een\u021belege mai bine de ce Loki nu are nevoie de indexare, s\u0103 ne \u00eentoarcem la metoda de investigare a incidentelor utilizat\u0103 de dezvoltatorii Loki:<\/p>\n<p><img decoding=\"async\" alt=\"Loki \u2014 colector de log-uri, utiliz\u00e2nd abordarea Prometheus\" src=\"\/wp-content\/uploads\/2020\/02\/2f9ba72d68ccafbe44ab1700d08e3a33.jpg\" style=\"display:block;margin: 0 auto;\"><br \/>\n<i>1 Alerte \u2192 2 Tabloane de bord \u2192 3 Interogare Adhoc \u2192 4 Agregare de loguri \u2192 5 Trasare distribuit\u0103 \u2192 6 Reparare!<br \/>\n(1 Alerte \u2192 2 Tabloane de bord \u2192 3 Interogare Adhoc \u2192 4 Agregare de loguri \u2192 5 Trasare distribuit\u0103 \u2192 6 Reparare!)<\/i><\/p>\n<p>Ideea este c\u0103 primim un anumit alert (Notificare Slack, SMS etc.) \u0219i dup\u0103 aceea:<\/p>\n<ul>\n<li>ne uit\u0103m la tablourile de bord Grafana<\/li>\n<li>ne uit\u0103m la metricile serviciilor (de exemplu, \u00een Prometheus)<\/li>\n<li>ne uit\u0103m la \u00eenregistr\u0103rile logurilor (de exemplu, \u00een Elasticsearch)<\/li>\n<li>probabil c\u0103 ne uit\u0103m la traseele distribuite (Jaeger, Zipkin etc.)<\/li>\n<li>\u0219i, \u00een final, remediem problema de baz\u0103.<\/li>\n<\/ul>\n<p>Aici, \u00een cazul stivei Grafana + Prometheus + Elasticsearch + Zipkin, va trebui s\u0103 folosim patru instrumente diferite. Pentru a economisi timp, ar fi util s\u0103 putem realiza toate aceste etape folosind un singur instrument: Grafana. Merit\u0103 men\u021bionat c\u0103 aceast\u0103 abordare a investiga\u021biei este implementat\u0103 \u00een Grafana \u00eencep\u00e2nd cu versiunea 6. Astfel, devine posibil s\u0103 accedem la datele Prometheus direct din Grafana.<\/p>\n<p><img decoding=\"async\" alt=\"Loki \u2014 colector de log-uri, utiliz\u00e2nd abordarea Prometheus\" src=\"\/wp-content\/uploads\/2020\/02\/eefc5a599a23abeb0624f4e3265a31e6.jpg\" style=\"display:block;margin: 0 auto;\"><br \/>\n<i>Ecranul Explorer este \u00eemp\u0103r\u021bit \u00eentre Prometheus \u0219i Loki<\/i><\/p>\n<p>Pe acest ecran, pute\u021bi vizualiza logurile \u00een Loki, corelate cu metricile Prometheus, utiliz\u00e2nd conceptul de \u00eemp\u0103r\u021bire a ecranului. \u00cencep\u00e2nd cu versiunea 6.5, Grafana permite procesarea ID-ului de trasare (trace id) \u00een \u00eenregistr\u0103rile logurilor Loki pentru a naviga c\u0103tre instrumentele dvs. preferate de trasare distribuit\u0103 (Jaeger).<\/p>\n<h3>Testare local\u0103 Loki<\/h3>\n<p>Cel mai simplu mod de a testa local Loki este s\u0103 folose\u0219ti docker-compose. Fi\u0219ierul docker-compose se afl\u0103 \u00een depozitul Loki. Pute\u021bi ob\u021bine depozitul cu ajutorul urm\u0103toarei comenzi: <code>git<\/code>:<\/p>\n<pre><code class=\"go\">$ git clone https:\/\/github.com\/grafana\/loki.git<\/code><\/pre>\n<p>Apoi, trebuie s\u0103 merge\u021bi \u00een directorul de produc\u021bie:<\/p>\n<pre><code class=\"go\">$ cd production<\/code><\/pre>\n<p>Dup\u0103 aceasta, pute\u021bi ob\u021bine cea mai recent\u0103 versiune a imaginilor Docker:<\/p>\n<pre><code class=\"go\">$ docker-compose pull<\/code><\/pre>\n<p>\u00cen final, stiva Loki se porne\u0219te cu urm\u0103toarea comand\u0103:<\/p>\n<pre><code class=\"go\">$ docker-compose up<\/code><\/pre>\n<h3>Arhitectura Loki<\/h3>\n<p>Iat\u0103 un mic diagram\u0103 cu arhitectura Loki:<\/p>\n<p><img decoding=\"async\" alt=\"Loki \u2014 colector de log-uri, utiliz\u00e2nd abordarea Prometheus\" src=\"\/wp-content\/uploads\/2020\/02\/fc5703bcebc1391e719640e99544f909.jpg\" style=\"display:block;margin: 0 auto;\"><br \/>\n<i>Principiile arhitecturii Loki<\/i><\/p>\n<p>Web client runs applications on the server, Promtail collects logs and sends them to Loki, the web client also sends metadata to Loki. Loki aggregates everything and passes it to Grafana.<br \/>\nLoki is running. To view the available components, execute the following command:<\/p>\n<pre><code class=\"go\">$ docker ps<\/code><\/pre>\n<p>In the case of a freshly installed Docker, the command should return the following result:<\/p>\n<pre><code class=\"go\">IMAGE               PORTS                  NAMES\ngrafana\/promtail:                          production_promtail_1\ngrafana\/grafana: m  0.0.0.0:3000-&gt;3000\/tcp production_grafana_1\ngrafana\/loki: late  80\/tcp,0.0.0.0:3100... production_loki_1<\/code><\/pre>\n<p>We see the following components:<\/p>\n<ul>\n<li>Promtail: agent responsible for log centralization<\/li>\n<li>Grafana: well-known tool for dashboards<\/li>\n<li>Loki: data centralization daemon<\/li>\n<\/ul>\n<p>In a traditional infrastructure (e.g., based on virtual machines), an agent Promtail must be deployed on each machine. Grafana and Loki can be installed on the same machine.<\/p>\n<h3>Deployment in Kubernetes<\/h3>\n<p>Installing Loki components in Kubernetes will consist of the following:<\/p>\n<ul>\n<li>daemonSet to deploy the Promtail agent on each machine in the server cluster<\/li>\n<li>deployment for Loki<\/li>\n<li>and finally \u2014 deployment of Grafana.<\/li>\n<\/ul>\n<p>Fortunately, Loki is available as a Helm package, which simplifies its deployment.<\/p>\n<h3>Installation via Helm<\/h3>\n<p>Helm should already be installed on your machine. It can be downloaded from the project's GitHub repository. It is installed by unpacking the archive corresponding to your architecture and adding helm to <code>$PATH<\/code>.<\/p>\n<blockquote><p><i><b>Not\u0103:<\/b> version 3.0.0 Helm was recently released. Since there have been many changes, it is recommended that the reader wait a bit before starting to use it<\/i>.<\/p><\/blockquote>\n<h3>Adding a source for Helm<\/h3>\n<p>The first step will be to add the 'loki' repository using the following command:<\/p>\n<pre><code class=\"go\">$ helm add loki https:\/\/grafana.github.io\/loki\/charts<\/code><\/pre>\n<p>After that, you can search for packages with the name 'loki':<\/p>\n<pre><code class=\"go\">$ helm search loki<\/code><\/pre>\n<p>Rezultatul:<\/p>\n<pre><code class=\"go\">loki\/loki       0.17.2 v0.4.0 Loki: like Prometheus, but for logs.\nloki\/loki-stack 0.19.1 v0.4.0 Loki: like Prometheus, but for logs.\nloki\/fluent-bit 0.0.2  v0.0.1 Uses fluent-bit Loki go plugin for...\nloki\/promtail   0.13.1 v0.4.0 Responsible for gathering logs and...<\/code><\/pre>\n<p>These packages have the following functionalities:<\/p>\n<ul>\n<li>package <b>loki\/loki<\/b> corresponds only to the Loki server<\/li>\n<li>package <b>loki\/fluent-bit<\/b> allows you to deploy DaemonSet using fluent-bit for log collection instead of Promtail<\/li>\n<li>package <b>loki\/promtail<\/b> contains the log file collection agent<\/li>\n<li>package <b>loki\/loki-stack<\/b>, allows you to deploy Loki along with Promtail at once.<\/li>\n<\/ul>\n<h3>Installing Loki<\/h3>\n<p>To deploy Loki in Kubernetes, run the following command in the 'monitoring' namespace:<\/p>\n<pre><code class=\"go\">$ helm upgrade --install loki loki\/loki-stack --namespace monitoring<\/code><\/pre>\n<p>Pentru a salva pe disc, ad\u0103uga\u021bi parametrul <code>--set loki.persistence.enabled = true:<\/code><\/p>\n<pre><code class=\"go\">$ helm upgrade --install loki loki\/loki-stack \n              --namespace monitoring \n              --set loki.persistence.enabled=true<\/code><\/pre>\n<blockquote><p><i><b>Not\u0103:<\/b> dac\u0103 dori\u021bi s\u0103 dezvolta\u021bi simultan Grafana, atunci ad\u0103uga\u021bi parametrul <code>--set grafana.enabled = true<\/code><\/i><\/p><\/blockquote>\n<p>C\u00e2nd rula\u021bi aceast\u0103 comand\u0103, ar trebui s\u0103 ob\u021bine\u021bi urm\u0103toarea ie\u0219ire:<\/p>\n<pre><code class=\"go\">ULTIMA CONFIGURARE: Mar, 19 Noi 2019 15:56:54\nSPATIU: monitoring\nSTATUT: CONFIGURAT\nRESURSE:\n==&amp;gt; v1\/ClusterRole\nNUME VARSTA\nloki-promtail-clusterrole 189z\n&hellip;\nNOTE:\nStiva Loki a fost configurat\u0103 &icirc;n clusterul dumneavoastr\u0103. Loki poate fi acum ad\u0103ugat ca o surs\u0103 de date &icirc;n Grafana.\nVezi &lt;a href=&quot;http:\/\/docs.grafana.org\/features\/datasources\/loki\/&quot;&gt;http:\/\/docs.grafana.org\/features\/datasources\/loki\/&lt;\/a&gt; pentru mai multe detalii.<\/code><\/pre>\n<p>Privind starea podurilor \u00een spa\u021biul de nume \u201emonitoring\u201d, vom vedea c\u0103 totul a fost desf\u0103\u0219urat:<\/p>\n<pre><code class=\"go\">$ kubectl -n monitoring get pods -l release=loki<\/code><\/pre>\n<p>Rezultatul:<\/p>\n<pre><code class=\"go\">NUME                 READY  STATUS   RESTARTS  AGE\nloki-0               1\/1    Running  0         147m\nloki-promtail-9zjvc  1\/1    Running  0         3h25m\nloki-promtail-f6brf  1\/1    Running  0         11h\nloki-promtail-hdcj7  1\/1    Running  0         3h23m\nloki-promtail-jbqhc  1\/1    Running  0         11h\nloki-promtail-mj642  1\/1    Running  0         62m\nloki-promtail-nm64g  1\/1    Running  0         24m<\/code><\/pre>\n<p>Toate podurile sunt pornite. Acum este timpul s\u0103 facem c\u00e2teva teste!<\/p>\n<h3>Conectarea la Grafana<\/h3>\n<p>Pentru a te conecta la Grafana prin Kubernetes, trebuie s\u0103 deschizi un tunel c\u0103tre podul s\u0103u. Iat\u0103 comanda pentru a deschide portul 3000 pentru podul Grafana:<\/p>\n<pre><code class=\"go\">$ kubectl -n port-forward monitoring svc\/loki-grafana 3000:80<\/code><\/pre>\n<p>Un alt aspect important este necesitatea de a recupera parola administratorului Grafana. Parola este stocat\u0103 \u00een secret <code>loki-grafana<\/code> \u00een c\u00e2mpul <code>.data.admin-user<\/code> \u00een format base64.<\/p>\n<p>Pentru a o recupera, trebuie s\u0103 executa\u021bi urm\u0103toarea comand\u0103:<\/p>\n<pre><code class=\"go\">$ kubectl -n monitoring get secret loki-grafana \n --template '{{index .data \"admin-password\" | base64decode}}'; echo<\/code><\/pre>\n<p>Utiliza\u021bi aceast\u0103 parol\u0103 \u00eempreun\u0103 cu contul de administrator implicit (admin).<\/p>\n<h3>Definirea sursei de date Loki \u00een Grafana<\/h3>\n<p>\u00cen primul r\u00e2nd, asigura\u021bi-v\u0103 c\u0103 a fost creat\u0103 o surs\u0103 de date Loki (Configuration \/ Datasource).<br \/>\nIat\u0103 un exemplu:<\/p>\n<p><img decoding=\"async\" alt=\"Loki \u2014 colector de log-uri, utiliz\u00e2nd abordarea Prometheus\" src=\"\/wp-content\/uploads\/2020\/02\/3b670a4b1a8b4db74b1e1f525fd03129.jpg\" style=\"display:block;margin: 0 auto;\"><br \/>\n<i>Exemplu de configurare a sursei de date pentru Loki<\/i><\/p>\n<p>Ap\u0103s\u00e2nd pe \u201eTest\u201d, pute\u021bi verifica conexiunea cu Loki.<\/p>\n<h3>Formul\u0103m cereri c\u0103tre Loki<\/h3>\n<p>Acum du-te la Grafana \u00een sec\u021biunea \u201eExplore\u201d. C\u00e2nd prime\u0219te loguri din containere, Loki adaug\u0103 metadate din Kubernetes. Astfel, devine posibil s\u0103 vezi logurile unui anumit container.<\/p>\n<p>De exemplu, pentru a selecta logurile din containerul promtail, po\u021bi folosi urm\u0103toarea cerere: <code>{container_name = \"promtail\"}<\/code>.<br \/>\nAici, de asemenea, nu uita\u021bi s\u0103 selecta\u021bi sursa de date Loki.<\/p>\n<p>Aceast\u0103 cerere va returna activitatea containerelor \u00een urm\u0103torul format:<\/p>\n<p><img decoding=\"async\" alt=\"Loki \u2014 colector de log-uri, utiliz\u00e2nd abordarea Prometheus\" src=\"\/wp-content\/uploads\/2020\/02\/ed2baebd374b9a6242cfc397776fa65f.jpg\" style=\"display:block;margin: 0 auto;\"><br \/>\n<i>Rezultatul cererii \u00een Grafana <\/i><\/p>\n<h3>Ad\u0103ugarea pe tabloul de bord<\/h3>\n<p>\u00cencep\u00e2nd cu Grafana 6.4, este posibil s\u0103 plasezi informa\u021biile despre loguri direct pe tabloul de bord. Dup\u0103 aceea, utilizatorul se va putea deplasa rapid \u00eentre num\u0103rul cererilor de pe site-ul s\u0103u \u0219i tras\u0103rile aplica\u021biei.<\/p>\n<p>Iat\u0103 un exemplu de tablou de bord care implementeaz\u0103 aceast\u0103 interac\u021biune:<\/p>\n<p><img decoding=\"async\" alt=\"Loki \u2014 colector de log-uri, utiliz\u00e2nd abordarea Prometheus\" src=\"\/wp-content\/uploads\/2020\/02\/d76c5345d543579eb3768fcdb0a2567b.jpg\" style=\"display:block;margin: 0 auto;\"><br \/>\n<i>Exemplu de tablou de bord cu metrici Prometheus \u0219i jurnale Loki<\/i><\/p>\n<h3>Viitorul Loki<\/h3>\n<p>Am \u00eenceput s\u0103 folosesc Loki \u00een mai\/iunie cu versiunea 0.1. Ast\u0103zi a fost lansat\u0103 versiunea 1, iar acum avem chiar \u0219i 1.1 \u0219i 1.2.<\/p>\n<p>Trebuie s\u0103 recunosc c\u0103 versiunea 0.1 nu a fost suficient de stabil\u0103. \u00cens\u0103 0.3 a ar\u0103tat deja semne reale de maturitate, iar versiunile urm\u0103toare (0.4, apoi 1.0) au \u00eent\u0103rit aceast\u0103 impresie.<\/p>\n<p>Dup\u0103 1.0.0, nimeni nu mai poate g\u0103si o scuz\u0103 pentru a nu folosi acest instrument minunat.<\/p>\n<p>\u00cembun\u0103t\u0103\u021birile ulterioare ar trebui s\u0103 se concentreze nu pe Loki, ci mai degrab\u0103 pe integrarea sa cu excelenta Grafana. De fapt, \u00een Grafana 6.4 a ap\u0103rut deja o integrare bun\u0103 cu tablourile de bord.<\/p>\n<p>Grafana 6.5, care a fost lansat\u0103 recent, \u00eembun\u0103t\u0103\u021be\u0219te \u0219i mai mult aceast\u0103 integrare, recunosc\u00e2nd automat con\u021binutul jurnalele \u00een format JSON.<\/p>\n<p>Mai jos este un scurt exemplu al acestui mecanism:<\/p>\n<p><img decoding=\"async\" alt=\"Loki \u2014 colector de log-uri, utiliz\u00e2nd abordarea Prometheus\" src=\"\/wp-content\/uploads\/2020\/02\/1e0a5269f21e401f349a35788672aec1.jpg\" style=\"display:block;margin: 0 auto;\"><br \/>\n<i>Utilizarea string-urilor Loki afi\u0219ate \u00een Grafana<\/i><\/p>\n<p>Devine posibil s\u0103 utiliza\u021bi unul dintre c\u00e2mpurile JSON, de exemplu, pentru:<\/p>\n<ul>\n<li>linkuri c\u0103tre un instrument extern<\/li>\n<li>filtrarea con\u021binutului jurnalelor<\/li>\n<\/ul>\n<p>De exemplu, pute\u021bi face clic pe traceId pentru a naviga la Zipkin sau Jaeger.<\/p>\n<p>A\u0219tept\u0103m tradi\u021bional comentariile voastre \u0219i v\u0103 invit\u0103m la <noindex><a rel=\"nofollow\" href=\"https:\/\/otus.pw\/P37L\/\">webinarul deschis<\/a><\/noindex>, unde vom discuta despre cum a evoluat industria DevOps \u00een 2019 \u0219i vom discuta despre posibilele direc\u021bii de dezvoltare pentru 2020.<\/p>\n<p>Sursa: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/otus\/blog\/487118\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u0421\u0430\u043b\u044e\u0442, \u0445\u0430\u0431\u0440\u043e\u0432\u0447\u0430\u043d\u0435! \u0412 \u043f\u0440\u0435\u0434\u0434\u0432\u0435\u0440\u0438\u0438 \u0441\u0442\u0430\u0440\u0442\u0430 \u043d\u043e\u0432\u043e\u0433\u043e \u043d\u0430\u0431\u043e\u0440\u0430 \u043d\u0430 \u043a\u0443\u0440\u0441 \u00abDevOps \u043f\u0440\u0430\u043a\u0442\u0438\u043a\u0438 \u0438 \u0438\u043d\u0441\u0442\u0440\u0443\u043c\u0435\u043d\u0442\u044b\u00bb \u043f\u043e\u0434\u0433\u043e\u0442\u043e\u0432\u0438\u043b\u0438 \u0434\u043b\u044f \u0432\u0430\u0441 \u043f\u0435\u0440\u0435\u0432\u043e\u0434 \u0438\u043d\u0442\u0435\u0440\u0435\u0441\u043d\u043e\u0433\u043e \u043c\u0430\u0442\u0435\u0440\u0438\u0430\u043b\u0430. \u042d\u0442\u0430 \u0441\u0442\u0430\u0442\u044c\u044f \u2014 \u043a\u0440\u0430\u0442\u043a\u043e\u0435 \u0432\u0432\u0435\u0434\u0435\u043d\u0438\u0435 \u0432 Loki. \u041f\u0440\u043e\u0435\u043a\u0442 Loki \u043f\u043e\u0434\u0434\u0435\u0440\u0436\u0438\u0432\u0430\u0435\u0442\u0441\u044f Grafana \u0438 \u043d\u0430\u043f\u0440\u0430\u0432\u043b\u0435\u043d \u043d\u0430 \u0446\u0435\u043d\u0442\u0440\u0430\u043b\u0438\u0437\u043e\u0432\u0430\u043d\u043d\u044b\u0439 \u0441\u0431\u043e\u0440 \u043b\u043e\u0433\u043e\u0432 (\u0441 \u0441\u0435\u0440\u0432\u0435\u0440\u043e\u0432 \u0438\u043b\u0438 \u043a\u043e\u043d\u0442\u0435\u0439\u043d\u0435\u0440\u043e\u0432). \u041e\u0441\u043d\u043e\u0432\u043d\u044b\u043c \u0438\u0441\u0442\u043e\u0447\u043d\u0438\u043a\u043e\u043c \u0432\u0434\u043e\u0445\u043d\u043e\u0432\u0435\u043d\u0438\u044f \u0434\u043b\u044f Loki \u0431\u044b\u043b Prometheus \u0441 \u0438\u0434\u0435\u0435\u0439 \u043f\u0440\u0438\u043c\u0435\u043d\u0435\u043d\u0438\u044f \u0435\u0433\u043e \u043f\u043e\u0434\u0445\u043e\u0434\u043e\u0432 \u043a \u0443\u043f\u0440\u0430\u0432\u043b\u0435\u043d\u0438\u044e \u043b\u043e\u0433\u0430\u043c\u0438: [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-56206","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.2.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u0421\u0430\u043b\u044e\u0442, \u0445\u0430\u0431\u0440\u043e\u0432\u0447\u0430\u043d\u0435!\" \/>\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\/ro\/blog\/administrirovanie\/loki-sbor-logov-ispolzuya-podhod-prometheus\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.2.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\udd47Loki \u2014 \u0441\u0431\u043e\u0440 \u043b\u043e\u0433\u043e\u0432, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044f \u043f\u043e\u0434\u0445\u043e\u0434 Prometheus | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u0421\u0430\u043b\u044e\u0442, \u0445\u0430\u0431\u0440\u043e\u0432\u0447\u0430\u043d\u0435!\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/loki-sbor-logov-ispolzuya-podhod-prometheus\" \/>\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=\"2020-02-06T21:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2021-02-01T09:41:00+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\udd47Loki - colectarea jurnalelor folosind abordarea Prometheus | ProHoster","description":"Salut, habrienilor!","canonical_url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/loki-sbor-logov-ispolzuya-podhod-prometheus","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"ro_RO","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\udd47Loki \u2014 \u0441\u0431\u043e\u0440 \u043b\u043e\u0433\u043e\u0432, \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u0443\u044f \u043f\u043e\u0434\u0445\u043e\u0434 Prometheus | ProHoster","og:description":"\u0421\u0430\u043b\u044e\u0442, \u0445\u0430\u0431\u0440\u043e\u0432\u0447\u0430\u043d\u0435!","og:url":"https:\/\/prohoster.info\/ro\/blog\/administrirovanie\/loki-sbor-logov-ispolzuya-podhod-prometheus","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":"2020-02-06T21:00:00+00:00","article:modified_time":"2021-02-01T09:41:00+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"56206","title":null,"description":"","keywords":"","keyphrases":null,"primary_term":null,"canonical_url":"","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":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 19:29:18","updated":"2022-09-28 02:03:48","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/56206","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/comments?post=56206"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/posts\/56206\/revisions"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/media?parent=56206"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/categories?post=56206"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/ro\/wp-json\/wp\/v2\/tags?post=56206"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}