{"id":31139,"date":"2019-10-31T21:39:40","date_gmt":"2019-10-31T18:39:40","guid":{"rendered":"https:\/\/prohoster.info\/blog\/monitorim-resursy-klasterov-kubernetes\/"},"modified":"2019-10-31T21:39:40","modified_gmt":"2019-10-31T18:39:40","slug":"monitorim-resursy-klasterov-kubernetes","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/monitorim-resursy-klasterov-kubernetes","title":{"rendered":"Monitorojm\u00eb burimet e klastereve Kubernetes","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/bn\/g6\/jg\/bng6jgpkvlzy8-2zahywzsnz8du.png\"><img decoding=\"async\" alt=\"Monitorojm\u00eb burimet e klastereve Kubernetes\" src=\"\/wp-content\/uploads\/2019\/04\/e3e07ee5a2271263948b3d3b39f3b66d.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<p>Kam krijova Kube Eagle - eksportuesin Prometheus. Doli t\u00eb jet\u00eb nj\u00eb gj\u00eb e shk\u00eblqyer, q\u00eb ndihmon n\u00eb kuptimin m\u00eb t\u00eb mir\u00eb t\u00eb burimeve t\u00eb grupeve t\u00eb vogla dhe t\u00eb mesme. N\u00eb fund, kursyeva me qindra dollar\u00eb, sepse zgjodha llojet e duhura t\u00eb makinave dhe konfigurava kufijt\u00eb e burimeve t\u00eb aplikacioneve n\u00eb p\u00ebrputhje me ngarkesat e pun\u00ebs.<\/p>\n<p><\/p>\n<p>Do t\u00eb flas p\u00ebr avantazhet <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/google-cloud-tools\/kube-eagle\">Kube Eagle<\/a><\/noindex>, por s\u00eb pari do t\u00eb shpjegoj se \u00e7far\u00eb e shkaktoi k\u00ebt\u00eb situat\u00eb dhe p\u00ebrse kishte nevoj\u00eb p\u00ebr monitorim cil\u00ebsor.<\/p>\n<p><noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><\/p>\n<p>Kam menaxhuar disa grupe me 4-50 nod\u00eb. N\u00eb \u00e7do grup - deri n\u00eb 200 mikroservise dhe aplikacione. P\u00ebr t\u00eb p\u00ebrdorur m\u00eb mir\u00eb pajisjet e disponueshme, shumica e deplozeve ishin konfiguruar me memorie dhe burime CPU burstable. K\u00ebshtu q\u00eb pod-i mund t\u00eb marr\u00eb burimet e disponueshme, n\u00ebse nevojitet, dhe n\u00eb t\u00eb nj\u00ebjt\u00ebn koh\u00eb t\u00eb mos pengoj\u00eb aplikacionet e tjera n\u00eb k\u00ebt\u00eb nod\u00eb. A nuk \u00ebsht\u00eb e mrekullueshme?<\/p>\n<p><\/p>\n<p>Dhe ndon\u00ebse grupi konsumonte relativisht pak CPU (8%) dhe RAM (40%), vazhdimisht kishim probleme me p\u00ebrjashtimin e pod-eve, kur ato p\u00ebrpiqeshin t\u00eb merrnin m\u00eb shum\u00eb memorie sesa ishte e disponueshme n\u00eb nod\u00eb. At\u00ebher\u00eb kishim vet\u00ebm nj\u00eb panel p\u00ebr monitorimin e burimeve Kubernetes. Ja si ishte:<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/qr\/cp\/x2\/qrcpx2avguhqnbxxg7trlxfnh4u.png\"><img decoding=\"async\" alt=\"Monitorojm\u00eb burimet e klastereve Kubernetes\" src=\"\/wp-content\/uploads\/2019\/04\/4ff784375fd4d01cc420d0d5b6389524.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<em>Paneli Grafana vet\u00ebm me metrika cAdvisor<\/em><\/p>\n<p><\/p>\n<p>Me k\u00ebt\u00eb panel, nod\u00ebt q\u00eb konsumonin shum\u00eb memorie dhe CPU, ishin t\u00eb dukshme pa problem. Problemi ishte t\u00eb kuptohej se \u00e7far\u00eb ishte arsyeja. P\u00ebr t\u00eb mbajtur pod-et n\u00eb vend, mund t\u00eb konfiguroni burime t\u00eb garantuara p\u00ebr t\u00eb gjitha pod-et (burimet e k\u00ebrkuara barazohen me kufirin). Por kjo nuk \u00ebsht\u00eb p\u00ebrdorimi m\u00eb inteligjent i pajisjeve. N\u00eb grup ishin disa qindra gigabajt memorie, dhe disa nod\u00eb ishin t\u00eb uritur, nd\u00ebrsa t\u00eb tjera kishin mbetje prej 4-10 GB.<\/p>\n<p><\/p>\n<p>K\u00ebshtu, planifikuesi Kubernetes shp\u00ebrndante ngarkesat e pun\u00ebs sipas burimeve t\u00eb disponueshme n\u00eb m\u00ebnyr\u00eb jo t\u00eb barabart\u00eb. Planifikuesi Kubernetes merr parasysh konfigurime t\u00eb ndryshme: rregullat e afinitetit, taints dhe tolerations, selektor\u00ebt e nod\u00ebve, q\u00eb mund t\u00eb kufizojn\u00eb nod\u00ebt e disponueshme. Por n\u00eb rastin tim, nuk kishte asgj\u00eb t\u00eb till\u00eb, dhe pod-et planifikoheshin n\u00eb var\u00ebsi t\u00eb burimeve t\u00eb k\u00ebrkuara n\u00eb \u00e7do nod\u00eb.<\/p>\n<p><\/p>\n<p>P\u00ebr nj\u00eb pod zgjidhej nodi me burimet m\u00eb t\u00eb lira dhe q\u00eb plot\u00ebsonte kushtet e k\u00ebrkes\u00ebs. Kaluam n\u00eb nj\u00eb situat\u00eb ku burimet e k\u00ebrkuara n\u00eb nod\u00eb nuk p\u00ebrputhen me shfryt\u00ebzimin aktual, dhe k\u00ebtu ndihmoi Kube Eagle dhe mund\u00ebsit\u00eb e tij p\u00ebr monitorimin e burimeve.<\/p>\n<p><\/p>\n<p>G hampir t\u00eb gjitha grupet Kubernetes monitoroheshin vet\u00ebm me <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/prometheus\/node_exporter\">Node exporter<\/a><\/noindex> dhe <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/kubernetes\/kube-state-metrics\">Metrikat e Shtetit t\u00eb Kube<\/a><\/noindex>. Node Exporter ofron statistika p\u00ebr hyrjet dhe daljet dhe p\u00ebrdorimin e diskut, CPU dhe RAM, nd\u00ebrsa Kube State Metrics tregon metrika p\u00ebr objektet Kubernetes, si\u00e7 jan\u00eb k\u00ebrkesat dhe kufijt\u00eb p\u00ebr burimet e CPU dhe memorjes.<\/p>\n<p><\/p>\n<p>Na nevojitet t\u00eb bashkojm\u00eb metrikat e p\u00ebrdorimit me metrikat e k\u00ebrkesave dhe kufijve n\u00eb Grafana, dhe at\u00ebher\u00eb do t\u00eb kemi t\u00eb gjitha informacionet mbi problemin. Kjo duket e thjesht\u00eb, por n\u00eb t\u00eb v\u00ebrtet\u00eb n\u00eb k\u00ebto dy mjete etiketat quhen ndryshe, dhe disa metrika madje nuk kan\u00eb fare etiketat e metadatas. Kube Eagle e b\u00ebn gjith\u00e7ka automatikisht dhe paneli duket k\u00ebshtu:<\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/u3\/ce\/hk\/u3cehkycztlwc9m7lpip-4lw2xe.png\"><img decoding=\"async\" alt=\"Monitorojm\u00eb burimet e klastereve Kubernetes\" src=\"\/wp-content\/uploads\/2019\/04\/53898543679d337df5a151b54fb75f5d.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><\/p>\n<p><\/p>\n<p><noindex><a rel=\"nofollow\" href=\"https:\/\/habrastorage.org\/webt\/po\/zi\/fm\/pozifm1dgtkf9nsasb42k1faqi4.png\"><img decoding=\"async\" alt=\"Monitorojm\u00eb burimet e klastereve Kubernetes\" src=\"\/wp-content\/uploads\/2019\/04\/a549c865b24f90fcc4375ffbb76ea270.png\" style=\"display:block;margin: 0 auto;\" \/><\/a><\/noindex><br \/>\n<em><noindex><a rel=\"nofollow\" href=\"https:\/\/grafana.com\/dashboards\/9871\">Paneli i monitorimit t\u00eb Kube Eagle<\/a><\/noindex><\/em><\/p>\n<p><\/p>\n<p>Kemi arritur t\u00eb zgjidhim shum\u00eb probleme me burimet dhe t\u00eb kursejm\u00eb pajisjet:<\/p>\n<p><\/p>\n<ol>\n<li>Disa zhvillues nuk dinin se sa burime i nevojiten mikrosh\u00ebrbimeve (ose thjesht nuk e merrnin seriozisht). Nuk kishim m\u00ebnyr\u00eb p\u00ebr t\u00eb identifikuar k\u00ebrkesat e gabshme p\u00ebr burime - p\u00ebr k\u00ebt\u00eb na duhej t\u00eb dinim konsumin plus k\u00ebrkesat dhe kufijt\u00eb. Tani ata shikojn\u00eb metrikat Prometheus, monitorojn\u00eb p\u00ebrdorimin aktual dhe p\u00ebrshtasin k\u00ebrkesat dhe kufijt\u00eb.<\/li>\n<li>Aplikacionet JVM marrin aq shum\u00eb RAM sa mund t\u00eb mbajn\u00eb. Mblidh\u00ebsi i plehrave liro burimin vet\u00ebm n\u00ebse \u00ebsht\u00eb p\u00ebrdorur m\u00eb shum\u00eb se 75%. Dhe pasi q\u00eb shumica e sh\u00ebrbimeve kan\u00eb memorje burstable, JVM gjithmon\u00eb e konsumonte at\u00eb. Prandaj, t\u00eb gjitha k\u00ebto sh\u00ebrbime Java konsumonin shum\u00eb m\u00eb tep\u00ebr RAM sesa pritej.<\/li>\n<li>Disa aplikacione k\u00ebrkuan shum\u00eb m\u00eb tep\u00ebr RAM, dhe planifikuesi i Kubernetes nuk u jepte k\u00ebto node aplikacioneve t\u00eb tjera, ndon\u00ebse n\u00eb fakt ata ishin m\u00eb t\u00eb lir\u00eb se node t\u00eb tjera. Nj\u00eb zhvillues rast\u00ebsisht u shtoi nj\u00eb num\u00ebr t\u00eb panevojsh\u00ebm n\u00eb k\u00ebrkes\u00eb dhe zuri nj\u00eb pjes\u00eb t\u00eb madhe t\u00eb RAM-it: 20 GB n\u00eb vend t\u00eb 2. Askush nuk e vuri re. Aplikacioni kishte 3 replik\u00eb, k\u00ebshtu q\u00eb u prek\u00ebn deri n\u00eb 3 node.<\/li>\n<li>Kemi vendosur kufizime p\u00ebr burimet, riplanifikuar pod-et me k\u00ebrkesat e duhura dhe arrit\u00ebm nj\u00eb balans t\u00eb p\u00ebrsosur t\u00eb p\u00ebrdorimit t\u00eb pajisjeve n\u00eb t\u00eb gjitha node-t. Disa node mund t\u00eb mbylleshin plot\u00ebsisht. M\u00eb pas e kuptuam se kishim makineri t\u00eb gabuara (orientuara ndaj CPU-s\u00eb, e jo ndaj memorjes). Ndryshuam tipin dhe fshim\u00eb edhe disa node t\u00eb tjera.<\/li>\n<\/ol>\n<p><\/p>\n<h3 id=\"itogi\">P\u00ebrfundime<\/h3>\n<p><\/p>\n<p>Me burimet burstable n\u00eb klaster, p\u00ebrdorni m\u00eb efektivisht pajisjet ekzistuese, por planifikuesi i Kubernetes planifikon pod-et sipas k\u00ebrkesave p\u00ebr burime, dhe kjo \u00ebsht\u00eb problematike. P\u00ebr t\u00eb eliminuar dy zogj me nj\u00eb gur: t\u00eb shmangim problemet dhe t\u00eb p\u00ebrdorim burimet n\u00eb maksimum, na nevojitet nj\u00eb monitorim i mir\u00eb. Pik\u00ebrisht p\u00ebr k\u00ebt\u00eb \u00ebsht\u00eb i nevojsh\u00ebm. <noindex><a rel=\"nofollow\" href=\"https:\/\/github.com\/google-cloud-tools\/kube-eagle\">Kube Eagle<\/a><\/noindex> (eksportuesi Prometheus dhe paneli i monitorimit Grafana).<\/p>\n<p>Burimi: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/company\/southbridge\/blog\/447336\/\">habr.com<\/a><\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u042f \u0441\u043e\u0437\u0434\u0430\u043b Kube Eagle\u00a0\u2014 \u044d\u043a\u0441\u043f\u043e\u0440\u0442\u0435\u0440 Prometheus. \u041e\u043a\u0430\u0437\u0430\u043b\u043e\u0441\u044c, \u043a\u0440\u0443\u0442\u0430\u044f \u0448\u0442\u0443\u043a\u0430, \u043a\u043e\u0442\u043e\u0440\u0430\u044f \u043f\u043e\u043c\u043e\u0433\u0430\u0435\u0442 \u043b\u0443\u0447\u0448\u0435 \u0440\u0430\u0437\u0431\u0438\u0440\u0430\u0442\u044c\u0441\u044f \u0432 \u0440\u0435\u0441\u0443\u0440\u0441\u0430\u0445 \u043c\u0430\u043b\u0435\u043d\u044c\u043a\u0438\u0445 \u0438 \u0441\u0440\u0435\u0434\u043d\u0438\u0445 \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432. \u0412 \u0438\u0442\u043e\u0433\u0435 \u044f \u0441\u044d\u043a\u043e\u043d\u043e\u043c\u0438\u043b \u043d\u0435 \u043e\u0434\u043d\u0443 \u0441\u043e\u0442\u043d\u044e \u0434\u043e\u043b\u043b\u0430\u0440\u043e\u0432, \u043f\u043e\u0442\u043e\u043c\u0443 \u0447\u0442\u043e \u043f\u043e\u0434\u0431\u0438\u0440\u0430\u043b \u043f\u0440\u0430\u0432\u0438\u043b\u044c\u043d\u044b\u0435 \u0442\u0438\u043f\u044b \u043c\u0430\u0448\u0438\u043d \u0438 \u043d\u0430\u0441\u0442\u0440\u0430\u0438\u0432\u0430\u043b \u043e\u0433\u0440\u0430\u043d\u0438\u0447\u0435\u043d\u0438\u044f \u0440\u0435\u0441\u0443\u0440\u0441\u043e\u0432 \u043f\u0440\u0438\u043b\u043e\u0436\u0435\u043d\u0438\u0439 \u043f\u043e\u0434 \u0440\u0430\u0431\u043e\u0447\u0438\u0435 \u043d\u0430\u0433\u0440\u0443\u0437\u043a\u0438. \u042f \u0440\u0430\u0441\u0441\u043a\u0430\u0436\u0443 \u043e \u043f\u0440\u0435\u0438\u043c\u0443\u0449\u0435\u0441\u0442\u0432\u0430\u0445 Kube Eagle, \u043d\u043e \u0441\u043d\u0430\u0447\u0430\u043b\u0430 \u043e\u0431\u044a\u044f\u0441\u043d\u044e, \u0438\u0437-\u0437\u0430 \u0447\u0435\u0433\u043e \u0432\u044b\u0448\u0435\u043b \u0441\u044b\u0440-\u0431\u043e\u0440 \u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":23107,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-31139","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.1.1 - aioseo.com -->\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\/sq\/blog\/administrirovanie\/monitorim-resursy-klasterov-kubernetes\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.1.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sq_AL\" \/>\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\u041c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043c \u0440\u0435\u0441\u0443\u0440\u0441\u044b \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes | ProHoster\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/monitorim-resursy-klasterov-kubernetes\" \/>\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:39:40+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2019-10-31T18:39:40+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\udd47Monitorojm\u00eb burimet e grupeve Kubernetes | ProHoster","description":"","canonical_url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/monitorim-resursy-klasterov-kubernetes","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\u041c\u043e\u043d\u0438\u0442\u043e\u0440\u0438\u043c \u0440\u0435\u0441\u0443\u0440\u0441\u044b \u043a\u043b\u0430\u0441\u0442\u0435\u0440\u043e\u0432 Kubernetes | ProHoster","og:url":"https:\/\/prohoster.info\/sq\/blog\/administrirovanie\/monitorim-resursy-klasterov-kubernetes","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:39:40+00:00","article:modified_time":"2019-10-31T18:39:40+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"31139","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:42:20","breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-03-01 03:22:34","updated":"2026-01-21 04:42:20","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\/31139","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=31139"}],"version-history":[{"count":0,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/posts\/31139\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media\/23107"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/media?parent=31139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/categories?post=31139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sq\/wp-json\/wp\/v2\/tags?post=31139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}