{"id":12955,"date":"2026-08-19T10:36:50","date_gmt":"2026-08-19T08:36:50","guid":{"rendered":"https:\/\/mybox.com\/help\/?post_type=manual_kb&#038;p=12955"},"modified":"2026-08-19T10:36:55","modified_gmt":"2026-08-19T08:36:55","slug":"devops-lista-de-verificare-a-stivei-de-observabilitate-indicatori-jurnale-urme-alerte-si-responsabilitati","status":"publish","type":"manual_kb","link":"https:\/\/mybox.com\/help\/ro\/knowledgebase\/devops-observability-stack-checklist-metrics-logs-traces-alerts-and-ownership\/","title":{"rendered":"Lista de verificare pentru stiva de observabilitate DevOps: indicatori, jurnale, trasee, alerte \u0219i responsabilit\u0103\u021bi"},"content":{"rendered":"<div class=\"translation-block translation-block-merged\">\n<p class=\"wp-block-paragraph\">O suit\u0103 fiabil\u0103 de instrumente de observabilitate DevOps ajut\u0103 echipa s\u0103 detecteze incidentele, s\u0103 \u00een\u021beleag\u0103 ce a e\u0219uat \u0219i s\u0103 ia decizii clare \u00een timpul serviciului de gard\u0103. Folosi\u021bi aceast\u0103 list\u0103 de verificare pentru a analiza colectarea datelor de telemetrie, corelarea semnalelor, tablourile de bord, alertele, perioada de p\u0103strare a datelor, accesul, instrumentarea \u0219i repartizarea costurilor \u00een \u00eentregul mediu.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Cuprins<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class=\"ez-toc-list ez-toc-list-level-1\"><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/devops-observability-stack-checklist-metrics-logs-traces-alerts-and-ownership\/#1_Confirm_the_purpose_of_each_signal\">1. Confirma\u021bi scopul fiec\u0103rui semnal<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/devops-observability-stack-checklist-metrics-logs-traces-alerts-and-ownership\/#2_Check_telemetry_collection_and_instrumentation\">2. Verifica\u021bi colectarea datelor de telemetrie \u0219i instrumenta\u021bia<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/devops-observability-stack-checklist-metrics-logs-traces-alerts-and-ownership\/#3_Test_correlation_between_signals\">3. Testarea corela\u021biei dintre semnale<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/devops-observability-stack-checklist-metrics-logs-traces-alerts-and-ownership\/#4_Review_dashboards_for_decisions\">4. Analiza\u021bi tablourile de bord pentru a lua decizii<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/devops-observability-stack-checklist-metrics-logs-traces-alerts-and-ownership\/#5_Audit_alert_quality_and_on-call_ownership\">5. Auditarea calit\u0103\u021bii alertelor \u0219i a responsabilit\u0103\u021bii de gard\u0103<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/devops-observability-stack-checklist-metrics-logs-traces-alerts-and-ownership\/#6_Check_retention_access_and_cost_ownership\">6. Verifica\u021bi reten\u021bia, accesul \u0219i costurile de proprietate<\/a><\/li><li class=\"ez-toc-page-1 ez-toc-heading-level-2\"><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/devops-observability-stack-checklist-metrics-logs-traces-alerts-and-ownership\/#Final_audit_result\">Rezultatul final al auditului<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"1_Confirm_the_purpose_of_each_signal\"><\/span>1. Confirma\u021bi scopul fiec\u0103rui semnal<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Telemetria reprezint\u0103 datele opera\u021bionale colectate de la sisteme \u0219i aplica\u021bii. Principalele semnale din aceast\u0103 list\u0103 de verificare sunt metricile, jurnalele \u0219i urmele. Acestea r\u0103spund la \u00eentreb\u0103ri diferite, astfel \u00eenc\u00e2t auditul ar trebui s\u0103 arate de unde provine fiecare semnal, unde este stocat \u0219i cine \u00eel utilizeaz\u0103 \u00een timpul unui incident.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Indicatori:<\/strong> confirm\u0103 faptul c\u0103 comportamentul important al serviciilor \u0219i al infrastructurii este m\u0103surat \u00een timp.<\/li>\n\n\n\n<li><strong>Jurnale:<\/strong> confirm\u0103 faptul c\u0103 evenimentele din aplica\u021bii \u0219i sisteme pot fi analizate cu suficient context pentru a sus\u021bine analiza defec\u021biunilor.<\/li>\n\n\n\n<li><strong>Urm\u0103riri:<\/strong> confirm\u0103 faptul c\u0103 o solicitare poate fi urm\u0103rit\u0103 prin toate p\u0103r\u021bile sistemului care o proceseaz\u0103.<\/li>\n\n\n\n<li><strong>Alerte:<\/strong> confirm\u0103 faptul c\u0103 echipa este notificat\u0103 atunci c\u00e2nd un eveniment necesit\u0103 o ac\u021biune, \u00een loc s\u0103 primeasc\u0103 un mesaj pentru fiecare modificare.<\/li>\n<\/ul>\n\n\n\n<\/div>\n\n<div id=\"mybox-1108772653\" class=\"mybox-content mybox-entity-placement\"><div class=\"early-access-banner-inpost\">\r\n  <div class=\"banner-left-inpost\">\r\n    <div class=\"icon-box-inpost\">\r\n      <img decoding=\"async\" src=\"https:\/\/mybox.com\/help\/wp-content\/uploads\/2026\/02\/square-info-icon.svg\" alt=\"Info\">\r\n    <\/div>\r\n    <div class=\"text-box-inpost\">\r\n      <span class=\"label-inpost\"><span class=\"translation-block translation-block-banner-text\">Acces timpuriu<\/span><\/span>\r\n      <h4><span class=\"translation-block translation-block-banner-text\">Mai ave\u021bi nevoie de ajutor?<\/span><\/h4>\r\n      <p><span class=\"translation-block translation-block-banner-text\">Contacta\u021bi echipa noastr\u0103 de servicii pentru clien\u021bi.<\/span><\/p>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <div class=\"banner-right-inpost\">\r\n    <a href=\"https:\/\/panel.mybox.com\/helpdesk2\/v\/list\/\" class=\"banner-button-inpost\"><span class=\"translation-block translation-block-banner-text\">Trimite mesaj<\/span><\/a>\r\n  <\/div>\r\n<\/div><\/div>\n\n<div class=\"translation-block translation-block-merged\"><p class=\"wp-block-paragraph\">OpenTelemetry \u0219i Prometheus r\u0103spund unor nevoi de observabilitate conexe, dar diferite. Alegerea depinde de faptul dac\u0103 echipa are nevoie de colectarea datelor de telemetrie, de metrici, de trasee sau de o combina\u021bie a acestor capacit\u0103\u021bi. Consemna\u021bi aceast\u0103 distinc\u021bie \u00een raportul de audit, \u00een loc s\u0103 trata\u021bi toate instrumentele de observabilitate ca fiind interschimbabile. <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/opentelemetry-vs-prometheus-ce-instrument-de-observabilitate-ar-trebui-sa-foloseasca-echipele-devops\/\">Compara\u021bia realizat\u0103 de mybox \u00eentre OpenTelemetry \u0219i Prometheus<\/a> ofer\u0103 distinc\u021bia relevant\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"2_Verifica\u021bi_colectarea_telemetriei_\u0219i_instrumentarea\"><\/span>2. Verifica\u021bi colectarea datelor de telemetrie \u0219i instrumentarea<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru fiecare serviciu critic, \u00eenregistra\u021bi dac\u0103 exist\u0103 instrumentare \u0219i ce semnale produce aceasta. Rezultatul ar trebui s\u0103 permit\u0103 identificarea serviciului, a mediului s\u0103u \u0219i a componentei care a emis datele.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Enumera\u021bi fiecare aplica\u021bie \u0219i component\u0103 de infrastructur\u0103 care ar trebui s\u0103 produc\u0103 date de telemetrie.<\/li>\n\n\n\n<li>Indica\u021bi dac\u0103 pentru fiecare component\u0103 se colecteaz\u0103 metrici, jurnale \u0219i urme.<\/li>\n\n\n\n<li>\u00cenregistra\u021bi metoda de colectare \u0219i instrumentul responsabil de aceasta.<\/li>\n\n\n\n<li>Verifica\u021bi dac\u0103 \u00een datele colectate apar cereri importante, sarcini de fundal \u0219i dependen\u021be.<\/li>\n\n\n\n<li>Identifica\u021bi serviciile care genereaz\u0103 date, dar nu sunt conectate la un tablou de bord sau la un sistem de alerte.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Include\u021bi Prometheus, Grafana, Loki, OpenTelemetry \u0219i Jaeger \u00een inventarul de instrumente atunci c\u00e2nd acestea fac parte din stiv\u0103. Pentru fiecare dintre acestea, documenta\u021bi rolul s\u0103u efectiv, semnalele pe care le gestioneaz\u0103, proprietarul s\u0103u \u0219i utilizatorii din aval. Acest lucru previne o configurare fragmentat\u0103 \u00een care un instrument este implementat, dar nicio echip\u0103 nu este responsabil\u0103 pentru rezultat.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"3_Test_correlation_between_signals\"><\/span>3. Testa\u021bi corela\u021bia dintre semnale<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Detectarea \u0219i diagnosticarea necesit\u0103 mai mult dec\u00e2t simple baze de date separate. Inginerul de gard\u0103 ar trebui s\u0103 poat\u0103 trece de la o alert\u0103 la serviciul, jurnalele \u0219i detaliile cererii asociate, f\u0103r\u0103 a fi nevoit s\u0103 ghiceasc\u0103 ce identificatori sau interval de timp s\u0103 utilizeze.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u00cencepe\u021bi cu o alert\u0103 real\u0103 \u0219i \u00eenregistra\u021bi pa\u0219ii necesari pentru a ajunge la metricile, jurnalele \u0219i urmele asociate.<\/li>\n\n\n\n<li>Verifica\u021bi dac\u0103 numele serviciilor, numele mediilor \u0219i informa\u021biile temporale utilizeaz\u0103 valori consecvente \u00een toate instrumentele.<\/li>\n\n\n\n<li>Confirma\u021bi c\u0103 acela\u0219i incident poate fi investigat pe baza mai multor semnale.<\/li>\n\n\n\n<li>\u00cenregistra\u021bi unde se \u00eentrerupe calea, cum ar fi un nume de serviciu lips\u0103 sau un semnal stocat f\u0103r\u0103 un context util.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">O stiv\u0103 care colecteaz\u0103 toate cele trei semnale, dar nu le poate conecta, las\u0103 \u00een continuare o lacun\u0103 \u00een diagnosticare. Trata\u021bi corela\u021bia ca o cerin\u021b\u0103 de audit separat\u0103, nu ca un rezultat automat al instal\u0103rii mai multor instrumente.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"4_Review_dashboards_for_decisions\"><\/span>4. Analiza\u021bi tablourile de bord pentru luarea deciziilor<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Tablourile de bord ar trebui s\u0103 sus\u021bin\u0103 o decizie opera\u021bional\u0103 specific\u0103. Crea\u021bi un inventar cu numele tabloului de bord, utilizatorul vizat, serviciul, semnalul \u0219i ac\u021biunea pe care o sus\u021bine.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>P\u0103stra\u021bi o vizualizare la nivel de serviciu pentru a detecta o schimbare a st\u0103rii de func\u021bionare.<\/li>\n\n\n\n<li>Men\u021bine\u021bi o perspectiv\u0103 la nivel de component\u0103 pentru a restr\u00e2nge zona afectat\u0103.<\/li>\n\n\n\n<li>Afi\u0219a\u021bi acelea\u0219i etichete de serviciu \u0219i mediu utilizate de alerte.<\/li>\n\n\n\n<li>Elimina\u021bi panourile care nu sunt utilizate \u00een timpul detect\u0103rii, diagnostic\u0103rii sau recuper\u0103rii.<\/li>\n\n\n\n<li>Desemna\u021bi un responsabil care s\u0103 verifice tabloul de bord atunci c\u00e2nd serviciul sufer\u0103 modific\u0103ri.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Monitorizarea disponibilit\u0103\u021bii ar trebui s\u0103 acopere \u0219i cauzele externe ale perioadelor de nefunc\u021bionare. Problemele legate de DNS, domeniile expirate \u0219i conflictele dintre pluginuri pot face ca un site web s\u0103 fie offline, chiar \u0219i atunci c\u00e2nd mediul de g\u0103zduire este disponibil. <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/cele-mai-bune-5-instrumente-pentru-monitorizarea-disponibilitatii-site-urilor-web\/\">Prezentarea general\u0103 a monitoriz\u0103rii disponibilit\u0103\u021bii site-urilor web realizat\u0103 de mybox<\/a> identific\u0103 aceste elemente ca factori care trebuie inclu\u0219i \u00een analiz\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"5_Audit_alert_quality_and_on-call_ownership\"><\/span>5. Auditul calit\u0103\u021bii alertelor \u0219i al responsabilit\u0103\u021bii de gard\u0103<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Pentru fiecare alert\u0103, nota\u021bi condi\u021bia, serviciul afectat, gravitatea, responsabilul de r\u0103spuns \u0219i ac\u021biunea urm\u0103toare. O alert\u0103 trece auditul atunci c\u00e2nd persoana de gard\u0103 poate decide ce m\u0103suri s\u0103 ia pe baza alertei \u0219i a contextului asociat acesteia.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Separa\u021bi alertele care necesit\u0103 ac\u021biune imediat\u0103 de evenimentele care necesit\u0103 doar analiz\u0103.<\/li>\n\n\n\n<li>Verifica\u021bi dac\u0103 alertele repetate sunt grupate \u00eentr-un singur incident.<\/li>\n\n\n\n<li>Confirma\u021bi c\u0103 fiecare alert\u0103 critic\u0103 are un responsabil actual \u0219i o cale de escaladare.<\/li>\n\n\n\n<li>Analiza\u021bi alertele care nu au nicio ac\u021biune \u00eenregistrat\u0103 sau care se \u00eenchid \u00een mod repetat f\u0103r\u0103 a fi investigate.<\/li>\n\n\n\n<li>Testa\u021bi alertele \u00een timpul unei revizuiri planificate, astfel \u00eenc\u00e2t echipa s\u0103 \u0219tie c\u0103 notificarea \u0219i atribuirea responsabilit\u0103\u021bii func\u021bioneaz\u0103 \u00een continuare.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Monitorizarea infrastructurii ar trebui s\u0103 sus\u021bin\u0103 verific\u0103rile de disponibilitate, performan\u021b\u0103 \u0219i securitate, problemele fiind identificate \u00eenainte de a afecta utilizatorii. Acestea sunt obiectivele principale de monitorizare descrise \u00een <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/instrument-de-monitorizare-a-infrastructurii-nagios\/\">prezentarea general\u0103 a Nagios realizat\u0103 de mybox<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"6_Check_retention_access_and_cost_ownership\"><\/span>6. Verifica\u021bi perioada de p\u0103strare, accesul \u0219i responsabilitatea pentru costuri<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Perioada de p\u0103strare define\u0219te c\u00e2t timp r\u0103m\u00e2ne disponibil fiecare semnal pentru investigare. \u00cenregistra\u021bi set\u0103rile de reten\u021bie pentru metrici, jurnale, trasee \u0219i istoricul alertelor, apoi compara\u021bi-le cu perioada necesar\u0103 pentru analiza incidentelor \u0219i raportarea opera\u021bional\u0103.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Documenta\u021bi cine poate citi, modifica \u0219i \u0219terge fiecare tip de date de telemetrie.<\/li>\n\n\n\n<li>Utiliza\u021bi grupuri de acces care corespund responsabilit\u0103\u021bilor opera\u021bionale.<\/li>\n\n\n\n<li>Verifica\u021bi dac\u0103 datele sensibile sau cu volum mare sunt accesibile unui num\u0103r mai mare de persoane dec\u00e2t este necesar.<\/li>\n\n\n\n<li>\u00cenregistra\u021bi responsabilul pentru stocare, preluare, tablouri de bord, reguli de alert\u0103 \u0219i opera\u021biuni de gard\u0103.<\/li>\n\n\n\n<li>Urm\u0103ri\u021bi care servicii genereaz\u0103 cea mai mare cantitate de date de telemetrie \u0219i care echipe sunt responsabile de aceast\u0103 utilizare.<\/li>\n\n\n\n<li>Verifica\u021bi dac\u0103 colectarea duplicat\u0103 sau datele de telemetrie neutilizate cresc costurile f\u0103r\u0103 a \u00eembun\u0103t\u0103\u021bi detectarea sau diagnosticul.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Responsabilitatea pentru costuri trebuie s\u0103 fie vizibil\u0103 la nivel de serviciu \u0219i de echip\u0103. Atunci c\u00e2nd nicio echip\u0103 nu este responsabil\u0103 pentru volumul de telemetrie, perioada de p\u0103strare sau utilizarea interog\u0103rilor, datele \u00een exces pot r\u0103m\u00e2ne \u00een stiv\u0103 f\u0103r\u0103 un factor de decizie clar. Atunci c\u00e2nd responsabilitatea este \u00eemp\u0103r\u021bit\u0103 \u00eentre echipe, \u00eenregistra\u021bi punctele de predare \u0219i persoana responsabil\u0103 pentru rezolvarea lacunelor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Final_audit_result\"><\/span>Rezultatul final al auditului<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Marca\u021bi fiecare cerin\u021b\u0103 ca fiind \u00eendeplinit\u0103, par\u021bial \u00eendeplinit\u0103 sau necesit\u00e2nd ac\u021biune. O \u00eenregistrare final\u0103 util\u0103 men\u021bioneaz\u0103 semnalul, instrumentul, serviciul, responsabilul, tabloul de bord, alerta, setarea de p\u0103strare, grupul de acces \u0219i responsabilul pentru costuri. Acorda\u021bi prioritate mai \u00eent\u00e2i elementelor care \u00eempiedic\u0103 detectarea, apoi celor care \u00eencetinesc diagnosticarea sau fac ca deciziile luate \u00een timpul g\u0103rzii s\u0103 fie neclare.<\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[11426,11447,11496,42,11442,11490],"manual_kb_tag":[],"class_list":["post-12955","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-monitoring-availability","manualknowledgebasecat-monitoring-observability","manualknowledgebasecat-debugging-testing-deployment","manualknowledgebasecat-miscellaneous","manualknowledgebasecat-devops-containers","manualknowledgebasecat-developer-resources"],"_links":{"self":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/12955","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/12955\/revisions"}],"predecessor-version":[{"id":12969,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/12955\/revisions\/12969"}],"wp:attachment":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/media?parent=12955"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manualknowledgebasecat?post=12955"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb_tag?post=12955"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}