{"id":1039,"date":"2026-10-04T15:57:27","date_gmt":"2026-10-04T15:57:27","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=1039"},"modified":"2026-10-04T09:41:22","modified_gmt":"2026-10-04T09:41:22","slug":"vpste-prometheus-grafana-kurulumu","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/vpste-prometheus-grafana-kurulumu\/","title":{"rendered":"VPS&#8217;te Prometheus ve Grafana ile \u0130zleme"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; VPS \u0130zleme<\/p>\n<p>Prometheus metrikleri toplar, Node Exporter Linux kaynaklar\u0131n\u0131 d\u0131\u015fa aktar\u0131r, Grafana ise bu verileri panellere ve alarmlara d\u00f6n\u00fc\u015ft\u00fcr\u00fcr. G\u00fcvenli port eri\u015fimi ve test edilmi\u015f bildirim kanal\u0131 kurulum kadar \u00f6nemlidir.<\/p>\n<ul>\n<li><strong>Temel bile\u015fenler<\/strong> \u2014 Prometheus veri toplar, Node Exporter sistem metriklerini sunar, Grafana g\u00f6rselle\u015ftirme sa\u011flar.<\/li>\n<li><strong>Port plan\u0131<\/strong> \u2014 Prometheus 9090, Grafana 3000 ve Node Exporter 9100 portlar\u0131n\u0131 yaln\u0131zca gerekli kaynaklara a\u00e7\u0131n.<\/li>\n<li><strong>Kaynak s\u0131n\u0131r\u0131<\/strong> \u2014 Scrape aral\u0131\u011f\u0131n\u0131 ve veri saklama s\u00fcresini disk kapasitesine g\u00f6re belirleyin.<\/li>\n<li><strong>\u0130lk metrikler<\/strong> \u2014 CPU, kullan\u0131labilir RAM, root dosya sistemi, a\u011f trafi\u011fi ve hedef eri\u015filebilirli\u011fiyle ba\u015flay\u0131n.<\/li>\n<li><strong>Alarm yakla\u015f\u0131m\u0131<\/strong> \u2014 E\u015fik, bekleme s\u00fcresi ve bildirim kanal\u0131n\u0131 her alarm i\u00e7in a\u00e7\u0131k\u00e7a tan\u0131mlay\u0131n.<\/li>\n<li><strong>Geri d\u00f6n\u00fc\u015f<\/strong> \u2014 Prometheus yap\u0131land\u0131rmas\u0131n\u0131, Grafana panellerini ve alarm kurallar\u0131n\u0131 ayr\u0131 olarak yedekleyip test edin.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">VPS&#039;te Prometheus ve Grafana kurulumu i\u00e7in Prometheus metrikleri toplar, Node Exporter Linux kaynaklar\u0131n\u0131 sunar ve Grafana bunlar\u0131 grafiklerle g\u00f6sterir. G\u00fcvenli bir kurulumda 9090, 3000 ve 9100 portlar\u0131 herkese a\u00e7\u0131lmaz; servisler ayr\u0131 kullan\u0131c\u0131larla \u00e7al\u0131\u015f\u0131r, disk saklama s\u0131n\u0131r\u0131 belirlenir ve alarm bildirimleri ger\u00e7ek bir testle do\u011frulan\u0131r.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 11 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#prometheus-ve-grafana-ne-ise-yarar\">Prometheus ve Grafana ne i\u015fe yarar?<\/a><\/li>\n<li><a href=\"#kurulumdan-once-vps-kaynaklari-nasil-planlanir\">Kurulumdan \u00f6nce VPS kaynaklar\u0131 nas\u0131l planlan\u0131r?<\/a><\/li>\n<li><a href=\"#prometheus-grafana-kurulumu-hangi-adimlarla-yapilir\">Prometheus Grafana kurulumu hangi ad\u0131mlarla yap\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#node-exporter-vps-metriklerini-nasil-toplar\">Node Exporter VPS metriklerini nas\u0131l toplar?<\/a><\/li>\n<li><a href=\"#prometheus-servisi-ve-erisim-guvenligi\">Prometheus servisi ve eri\u015fim g\u00fcvenli\u011fi<\/a><\/li>\n<li><a href=\"#grafanada-veri-kaynagi-ve-dashboard-nasil-eklenir\">Grafana&#039;da veri kayna\u011f\u0131 ve dashboard nas\u0131l eklenir?<\/a><\/li>\n<li><a href=\"#prometheus-ile-hangi-alarmlar-kurulmali\">Prometheus ile hangi alarmlar kurulmal\u0131?<\/a><\/li>\n<li><a href=\"#izleme-verisi-ne-kadar-sure-saklanmali\">\u0130zleme verisi ne kadar s\u00fcre saklanmal\u0131?<\/a><\/li>\n<li><a href=\"#kurulumdan-sonra-hangi-kontroller-yapilir\">Kurulumdan sonra hangi kontroller yap\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#kurulumu-tamamlamadan-once-sunlari-kontrol-edin\">Kurulumu Tamamlamadan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"prometheus-ve-grafana-ne-ise-yarar\">Prometheus ve Grafana ne i\u015fe yarar?<\/h2>\n<p>Bir VPS&#8217;in SSH ba\u011flant\u0131s\u0131n\u0131n a\u00e7\u0131k kalmas\u0131, sa\u011fl\u0131kl\u0131 \u00e7al\u0131\u015ft\u0131\u011f\u0131 anlam\u0131na gelmez. Disk dolabilir, RAM t\u00fckenebilir veya Nginx gelen istekleri kar\u015f\u0131layamayacak kadar yo\u011funla\u015fabilir. Prometheus metrikleri zaman serisi olarak toplar; Grafana bu verileri grafik, panel ve alarm kurallar\u0131na d\u00f6n\u00fc\u015ft\u00fcr\u00fcr. Sa\u011flam bir izleme d\u00fczeni yaln\u0131zca CPU y\u00fczdesini g\u00f6stermez, de\u011fi\u015fimin ne zaman ba\u015flad\u0131\u011f\u0131n\u0131 da ortaya \u00e7\u0131kar\u0131r.<\/p>\n<p>Prometheus, HTTP \u00fczerinden metrikleri \u00e7eken ve bunlar\u0131 kendi zaman serisi veritaban\u0131nda saklayan bir izleme sunucusudur. Grafana do\u011frudan sistem \u00f6l\u00e7mez; Prometheus gibi bir veri kayna\u011f\u0131na ba\u011flanarak sorgu sonu\u00e7lar\u0131n\u0131 g\u00f6rselle\u015ftirir. K\u00fc\u00e7\u00fck bir VPS ortam\u0131nda temel mimari \u015f\u00f6yledir:<\/p>\n<ul>\n<li><strong>Prometheus:<\/strong> Metrikleri toplar, saklar ve PromQL ile sorgular.<\/li>\n<li><strong>Node Exporter:<\/strong> Linux \u00e7ekirde\u011fi ve sistem kaynaklar\u0131n\u0131 metrik olarak sunar.<\/li>\n<li><strong>Grafana:<\/strong> Panelleri ve uyar\u0131lar\u0131 g\u00f6sterir.<\/li>\n<li><strong>systemd:<\/strong> Servislerin a\u00e7\u0131l\u0131\u015fta ba\u015flamas\u0131n\u0131 ve \u00e7al\u0131\u015f\u0131rken y\u00f6netilmesini sa\u011flar.<\/li>\n<\/ul>\n<p>Prometheus&#8217;un temel \u00e7al\u0131\u015fma modeli pull yakla\u015f\u0131m\u0131d\u0131r: Prometheus belirli aral\u0131klarla hedefteki <code>\/metrics<\/code> u\u00e7 noktas\u0131n\u0131 sorgular. Bu ayr\u0131nt\u0131, g\u00fcvenlik duvar\u0131nda yaln\u0131zca gerekli eri\u015fimi a\u00e7mak ve hedeflerin ger\u00e7ekten eri\u015filebilir oldu\u011funu do\u011frulamak a\u00e7\u0131s\u0131ndan \u00f6nemlidir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; \u0130zleme tasar\u0131m\u0131nda CPU, RAM, disk, a\u011f, servis eri\u015filebilirli\u011fi ve alarm teslimini ayr\u0131 ayr\u0131 planlay\u0131n.<\/p>\n<h2 id=\"kurulumdan-once-vps-kaynaklari-nasil-planlanir\">Kurulumdan \u00f6nce VPS kaynaklar\u0131 nas\u0131l planlan\u0131r?<\/h2>\n<p>Tek VPS \u00fczerinde Prometheus, Grafana ve Node Exporter \u00e7al\u0131\u015ft\u0131rmak k\u00fc\u00e7\u00fck ortamlar i\u00e7in m\u00fcmk\u00fcnd\u00fcr. Kaynak ihtiyac\u0131 hedef say\u0131s\u0131na, scrape aral\u0131\u011f\u0131na, saklama s\u00fcresine ve metrik kardinalitesine ba\u011fl\u0131d\u0131r. Tek bir Linux VPS&#8217;ini izlemek i\u00e7in a\u011f\u0131r bir k\u00fcme gerekmez; \u00f6l\u00e7\u00fcm verisini de s\u0131radan bir log gibi s\u0131n\u0131rs\u0131z b\u0131rakmamak gerekir.<\/p>\n<table>\n<thead>\n<tr>\n<th>Bile\u015fen<\/th>\n<th>Varsay\u0131lan port<\/th>\n<th>G\u00f6revi<\/th>\n<th>Eri\u015fim \u00f6nerisi<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Prometheus<\/td>\n<td>9090\/TCP<\/td>\n<td>Metrikleri toplar ve sorgular<\/td>\n<td>Yaln\u0131zca y\u00f6netim a\u011f\u0131 veya VPN<\/td>\n<\/tr>\n<tr>\n<td>Grafana<\/td>\n<td>3000\/TCP<\/td>\n<td>Paneller ve alarmlar<\/td>\n<td>HTTPS arkas\u0131nda veya g\u00fcvenilir IP&#8217;ler<\/td>\n<\/tr>\n<tr>\n<td>Node Exporter<\/td>\n<td>9100\/TCP<\/td>\n<td>Sunucu metrikleri<\/td>\n<td>Sadece Prometheus sunucusu<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Prometheus&#8217;un disk t\u00fcketimi; \u00f6rnek say\u0131s\u0131, etiket say\u0131s\u0131 ve saklama s\u00fcresiyle b\u00fcy\u00fcr. Her be\u015f saniyede veri toplamak daha ayr\u0131nt\u0131l\u0131 grafik sa\u011flayabilir, ancak gereksiz \u00f6rnek y\u00fck\u00fc olu\u015fturur. Ba\u015flang\u0131\u00e7 i\u00e7in 15 veya 30 saniyelik <code>scrape_interval<\/code> \u00e7o\u011fu VPS uygulamas\u0131nda yeterlidir. Disk kullan\u0131m\u0131n\u0131 hesaplarken Prometheus&#8217;un kendi veri dizinini de hesaba kat\u0131n.<\/p>\n<p>Ubuntu 22.04 veya 24.04 gibi desteklenen bir da\u011f\u0131t\u0131m, ayr\u0131 bir izleme VPS&#8217;i ve g\u00fcncel paketlerle daha temiz bir ba\u015flang\u0131\u00e7 sa\u011flar. \u0130zleme sunucusu izledi\u011fi makineyle ayn\u0131 VPS&#8217;teyse, makine tamamen \u00e7\u00f6kt\u00fc\u011f\u00fcnde alarm\u0131 da g\u00f6remezsiniz. Kritik sistemlerde Prometheus ve Grafana&#8217;y\u0131 farkl\u0131 bir VPS&#8217;te tutmak daha g\u00fcvenlidir.<\/p>\n<p>Sunucunuzda i\u015flem ve bellek t\u00fcketimini ilk kontrolden ge\u00e7irmek i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/linux-islem-yonetimi-ps-top-kill\/\">Linux&#8217;ta \u0130\u015flem Y\u00f6netimi: ps, top ve kill Kullan\u0131m\u0131<\/a> ba\u015fl\u0131\u011f\u0131ndaki temel komutlardan yararlanabilirsiniz. Grafana&#8217;n\u0131n veritaban\u0131, eklenti ve panel say\u0131s\u0131 artt\u0131k\u00e7a bellek ihtiyac\u0131 da y\u00fckselir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; \u0130zleme bile\u015fenlerini m\u00fcmk\u00fcnse izlenen uygulamadan ayr\u0131 bir VPS&#8217;e yerle\u015ftirin ve veri saklama s\u00fcresini kurulumdan \u00f6nce belirleyin.<\/p>\n<h2 id=\"prometheus-grafana-kurulumu-hangi-adimlarla-yapilir\">Prometheus Grafana kurulumu hangi ad\u0131mlarla yap\u0131l\u0131r?<\/h2>\n<p>A\u015fa\u011f\u0131daki \u00f6rnek Debian veya Ubuntu \u00fczerinde ayr\u0131 kullan\u0131c\u0131larla \u00e7al\u0131\u015fan binary kurulumunu g\u00f6sterir. Da\u011f\u0131t\u0131m deposundaki s\u00fcr\u00fcm eski olabilir; \u00fcretimde s\u00fcr\u00fcm\u00fc Prometheus ve Grafana&#8217;n\u0131n resmi indirme sayfalar\u0131ndan kontrol edin. Buradaki Prometheus <code>2.55.1<\/code> ve Node Exporter <code>1.8.2<\/code> de\u011ferleri \u00f6rnek kurulum s\u00fcr\u00fcmleridir; kurulum g\u00fcn\u00fcnde yay\u0131mlanan s\u00fcr\u00fcm\u00fc ve SHA256 de\u011ferini do\u011frulay\u0131n.<\/p>\n<h3>Prometheus kullan\u0131c\u0131s\u0131n\u0131 ve dizinlerini olu\u015fturma<\/h3>\n<pre><code>sudo useradd --no-create-home --shell \/usr\/sbin\/nologin prometheus\nsudo mkdir -p \/etc\/prometheus \/var\/lib\/prometheus\nsudo chown prometheus:prometheus \/var\/lib\/prometheus<\/code><\/pre>\n<p>Prometheus&#8217;un yap\u0131land\u0131rmas\u0131 <code>\/etc\/prometheus\/prometheus.yml<\/code>, zaman serisi verisi ise <code>\/var\/lib\/prometheus<\/code> alt\u0131nda tutulabilir. Servisi root olarak \u00e7al\u0131\u015ft\u0131rmamak, bir s\u00fcre\u00e7 a\u00e7\u0131\u011f\u0131ndan sonra yetki alan\u0131n\u0131 daralt\u0131r.<\/p>\n<h3>Prometheus binary dosyas\u0131n\u0131 yerle\u015ftirme<\/h3>\n<pre><code>cd \/tmp\ncurl -LO https:\/\/github.com\/prometheus\/prometheus\/releases\/download\/v2.55.1\/prometheus-2.55.1.linux-amd64.tar.gz\ntar xzf prometheus-2.55.1.linux-amd64.tar.gz\nsudo cp prometheus-2.55.1.linux-amd64\/prometheus \/usr\/local\/bin\/\nsudo cp prometheus-2.55.1.linux-amd64\/promtool \/usr\/local\/bin\/\nsudo cp -r prometheus-2.55.1.linux-amd64\/consoles \/etc\/prometheus\/\nsudo cp -r prometheus-2.55.1.linux-amd64\/console_libraries \/etc\/prometheus\/\nsudo chown -R prometheus:prometheus \/etc\/prometheus<\/code><\/pre>\n<p>\u00dcretimde ar\u015fivin SHA256 de\u011ferini resmi s\u00fcr\u00fcm sayfas\u0131ndaki de\u011ferle kar\u015f\u0131la\u015ft\u0131r\u0131n. HTTPS \u00fczerinden indirmek ba\u011flant\u0131y\u0131 korur; dosyan\u0131n b\u00fct\u00fcnl\u00fc\u011f\u00fcn\u00fc tek ba\u015f\u0131na kan\u0131tlamaz.<\/p>\n<h3>Temel yap\u0131land\u0131rmay\u0131 yazma<\/h3>\n<pre><code>sudo vim \/etc\/prometheus\/prometheus.yml<\/code><\/pre>\n<pre><code>global:\n  scrape_interval: 15s\n  evaluation_interval: 15s\n\nrule_files:\n  - \/etc\/prometheus\/alerts.yml\n\nscrape_configs:\n  - job_name: prometheus\n    static_configs:\n      - targets: ['127.0.0.1:9090']\n\n  - job_name: node\n    static_configs:\n      - targets: ['127.0.0.1:9100']<\/code><\/pre>\n<p>Buradaki <code>job_name<\/code> ve <code>instance<\/code> etiketleri daha sonra PromQL sorgular\u0131nda kullan\u0131l\u0131r. Prometheus yap\u0131land\u0131rmas\u0131n\u0131 servisi ba\u015flatmadan \u00f6nce <code>promtool<\/code> ile kontrol edin:<\/p>\n<pre><code>sudo -u prometheus promtool check config \/etc\/prometheus\/prometheus.yml<\/code><\/pre>\n<p>Ge\u00e7erli bir dosyada <code>SUCCESS<\/code> mesaj\u0131 g\u00f6r\u00fcrs\u00fcn\u00fcz. Girinti hatas\u0131 veya tan\u0131nmayan alan varsa servis ba\u015flat\u0131lmadan \u00f6nce d\u00fczeltilmelidir.<\/p>\n<h2 id=\"node-exporter-vps-metriklerini-nasil-toplar\">Node Exporter VPS metriklerini nas\u0131l toplar?<\/h2>\n<p>Node Exporter; CPU, bellek, dosya sistemi, a\u011f ve y\u00fck gibi Linux sistem metriklerini Prometheus&#8217;un okuyabilece\u011fi bi\u00e7imde sunar. Temel ak\u0131\u015f, exporter servisinin \u00e7al\u0131\u015ft\u0131r\u0131lmas\u0131 ve Prometheus&#8217;un <code>9100<\/code> portundan scrape etmesidir.<\/p>\n<pre><code>sudo useradd --no-create-home --shell \/usr\/sbin\/nologin node_exporter\ncd \/tmp\ncurl -LO https:\/\/github.com\/prometheus\/node_exporter\/releases\/download\/v1.8.2\/node_exporter-1.8.2.linux-amd64.tar.gz\ntar xzf node_exporter-1.8.2.linux-amd64.tar.gz\nsudo cp node_exporter-1.8.2.linux-amd64\/node_exporter \/usr\/local\/bin\/\nsudo chown node_exporter:node_exporter \/usr\/local\/bin\/node_exporter<\/code><\/pre>\n<p>Servis tan\u0131m\u0131n\u0131 olu\u015fturun:<\/p>\n<pre><code>sudo vim \/etc\/systemd\/system\/node_exporter.service<\/code><\/pre>\n<pre><code>[Unit]\nDescription=Prometheus Node Exporter\nAfter=network-online.target\n\n[Service]\nUser=node_exporter\nGroup=node_exporter\nType=simple\nExecStart=\/usr\/local\/bin\/node_exporter\n\n[Install]\nWantedBy=multi-user.target<\/code><\/pre>\n<pre><code>sudo systemctl daemon-reload\nsudo systemctl enable --now node_exporter\ncurl -s http:\/\/127.0.0.1:9100\/metrics | head<\/code><\/pre>\n<p>\u00c7\u0131kt\u0131da <code># HELP<\/code> ve <code># TYPE<\/code> sat\u0131rlar\u0131yla ba\u015flayan metrik a\u00e7\u0131klamalar\u0131 g\u00f6r\u00fcn\u00fcr. Bu endpoint internete a\u00e7\u0131k b\u0131rak\u0131lmamal\u0131d\u0131r. Node Exporter&#8217;\u0131n 9100 portuna yaln\u0131zca Prometheus sunucusunun eri\u015fmesine izin veren bir firewall kural\u0131 yeterlidir.<\/p>\n<p>Web sunucusu da izlenecekse <a href=\"https:\/\/www.vps.tc\/blog\/tr\/ubuntu-nginx-kurulumu-ilk-yapilandirma\/\">Nginx kurulumu ve ilk yap\u0131land\u0131rma<\/a> ad\u0131mlar\u0131ndan sonra Nginx exporter veya uygun bir metrics mod\u00fcl\u00fc ayr\u0131ca planlanmal\u0131d\u0131r. Node Exporter, Nginx&#8217;in istek say\u0131s\u0131 ve upstream gecikmesi gibi uygulamaya \u00f6zg\u00fc metriklerini kendili\u011finden sa\u011flamaz.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Node Exporter&#8217;\u0131 ayr\u0131 kullan\u0131c\u0131yla \u00e7al\u0131\u015ft\u0131r\u0131n ve 9100\/TCP portunu yaln\u0131zca Prometheus sunucusuna a\u00e7\u0131n.<\/p>\n<h2 id=\"prometheus-servisi-ve-erisim-guvenligi\">Prometheus servisi ve eri\u015fim g\u00fcvenli\u011fi<\/h2>\n<p>Prometheus i\u00e7in systemd servis dosyas\u0131 olu\u015fturun:<\/p>\n<pre><code>sudo vim \/etc\/systemd\/system\/prometheus.service<\/code><\/pre>\n<pre><code>[Unit]\nDescription=Prometheus\nWants=network-online.target\nAfter=network-online.target\n\n[Service]\nUser=prometheus\nGroup=prometheus\nType=simple\nExecStart=\/usr\/local\/bin\/prometheus \\\n  --config.file=\/etc\/prometheus\/prometheus.yml \\\n  --storage.tsdb.path=\/var\/lib\/prometheus \\\n  --web.listen-address=127.0.0.1:9090 \\\n  --storage.tsdb.retention.time=15d \\\n  --storage.tsdb.retention.size=20GB\n\n[Install]\nWantedBy=multi-user.target<\/code><\/pre>\n<pre><code>sudo systemctl daemon-reload\nsudo systemctl enable --now prometheus\nsudo systemctl status prometheus --no-pager\ncurl -s http:\/\/127.0.0.1:9090\/-\/ready<\/code><\/pre>\n<p><code>\/-\/ready<\/code> iste\u011finin HTTP 200 d\u00f6nd\u00fcrmesi Prometheus&#8217;un sorgu kabul etmeye haz\u0131r oldu\u011funu g\u00f6sterir. Servis ba\u015flamazsa do\u011frudan yeniden ba\u015flatmak yerine <code>journalctl -u prometheus -n 50 --no-pager<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 okuyun. Yanl\u0131\u015f dosya yolu, sahiplik veya YAML s\u00f6zdizimi genellikle burada g\u00f6r\u00fcn\u00fcr.<\/p>\n<p>Grafana&#8217;n\u0131n resmi Debian kurulumunda imzal\u0131 paket deposu veya da\u011f\u0131t\u0131m paketi kullan\u0131labilir. Kurulumdan sonra servisi etkinle\u015ftirin:<\/p>\n<pre><code>sudo systemctl enable --now grafana-server\nsudo systemctl status grafana-server --no-pager<\/code><\/pre>\n<p>Grafana&#8217;n\u0131n 3000 portunu do\u011frudan internete a\u00e7mak yerine Nginx reverse proxy, HTTPS ve eri\u015fim k\u0131s\u0131tlamas\u0131 kullan\u0131n. Nginx kullan\u0131yorsan\u0131z domain, URL ve proxy ba\u015fl\u0131klar\u0131n\u0131 ayr\u0131ca do\u011frulay\u0131n; eri\u015fim problemi her zaman Grafana servisinin kapal\u0131 oldu\u011fu anlam\u0131na gelmez.<\/p>\n<p>Prometheus&#8217;u <code>127.0.0.1:9090<\/code> \u00fczerinde dinletmek, web aray\u00fcz\u00fcn\u00fc d\u0131\u015f a\u011fa kapat\u0131r. Grafana farkl\u0131 bir VPS&#8217;teyse Prometheus&#8217;un dinleme adresi, firewall ve TLS gereksinimleri yeniden tasarlanmal\u0131d\u0131r. Y\u00f6netim portlar\u0131n\u0131 yaln\u0131zca SSH t\u00fcneli veya WireGuard \u00fczerinden eri\u015filebilir yapmak \u00e7o\u011fu k\u00fc\u00e7\u00fck ortamda daha d\u00fc\u015f\u00fck risklidir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Prometheus ve Grafana portlar\u0131n\u0131 herkese a\u00e7madan \u00f6nce reverse proxy, firewall ve eri\u015fim kayna\u011f\u0131n\u0131 birlikte belirleyin.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>Dikkat: 9100 portunu internete a\u00e7mak Node Exporter metriklerini herkese g\u00f6sterebilir. Firewall&#039;da yaln\u0131zca Prometheus sunucusunun kaynak IP&#039;sine izin verin; SSH portunu de\u011fi\u015ftirmek tek ba\u015f\u0131na g\u00fcvenlik politikas\u0131 de\u011fildir.<\/p>\n<\/div>\n<h2 id=\"grafanada-veri-kaynagi-ve-dashboard-nasil-eklenir\">Grafana&#8217;da veri kayna\u011f\u0131 ve dashboard nas\u0131l eklenir?<\/h2>\n<p>Grafana aray\u00fcz\u00fcne ilk giri\u015ften sonra <code>Connections<\/code> veya s\u00fcr\u00fcme g\u00f6re <code>Data sources<\/code> b\u00f6l\u00fcm\u00fcnden Prometheus&#8217;u ekleyin. Ayn\u0131 VPS \u00fczerindeki kurulumda URL olarak <code>http:\/\/127.0.0.1:9090<\/code> kullan\u0131labilir. Grafana konteynerde, Prometheus host \u00fczerinde \u00e7al\u0131\u015f\u0131yorsa <code>127.0.0.1<\/code> konteyneri ifade eder; bu durumda servis ad\u0131 veya eri\u015filebilir host adresi gerekir.<\/p>\n<p>Ba\u011flant\u0131y\u0131 <code>Save &amp; test<\/code> ile s\u0131nay\u0131n. Ba\u015far\u0131l\u0131 ba\u011flant\u0131dan sonra Explore ekran\u0131nda \u015fu PromQL sorgular\u0131n\u0131 deneyin:<\/p>\n<pre><code>up\nnode_memory_MemAvailable_bytes\nrate(node_cpu_seconds_total{mode=\"idle\"}[5m])\n100 - (node_filesystem_avail_bytes{mountpoint=\"\/\"} * 100 \/ node_filesystem_size_bytes{mountpoint=\"\/\"})<\/code><\/pre>\n<p><code>up<\/code> de\u011feri 1 ise hedef son scrape i\u015fleminde eri\u015filebilir, 0 ise eri\u015fim veya exporter sorunu vard\u0131r. CPU sorgusu \u00e7ekirdek ba\u015f\u0131na idle oran\u0131n\u0131 verir; toplam kullan\u0131m i\u00e7in sorgunun matematiksel bi\u00e7imi ve panel birimi do\u011fru ayarlanmal\u0131d\u0131r. Disk sorgusunda ge\u00e7ici dosya sistemlerini filtrelemek gerekebilir.<\/p>\n<p>Haz\u0131r dashboard i\u00e7e aktarmak h\u0131zl\u0131d\u0131r, fakat rastgele bir JSON dosyas\u0131na g\u00fcvenmeyin. Dashboard&#8217;un kulland\u0131\u011f\u0131 metrik adlar\u0131n\u0131, de\u011fi\u015fkenleri ve sorgular\u0131 inceleyin. Prometheus s\u00fcr\u00fcm\u00fc, Node Exporter s\u00fcr\u00fcm\u00fc veya etiket isimleri farkl\u0131ysa grafikler bo\u015f g\u00f6r\u00fcnebilir.<\/p>\n<p>Panel tasar\u0131m\u0131nda tek grafi\u011fe \u00e7ok fazla seri eklemek yerine \u00f6nce VPS&#8217;in sa\u011fl\u0131\u011f\u0131na odaklan\u0131n: CPU kullan\u0131m e\u011filimi, kullan\u0131labilir bellek, root dosya sistemi, a\u011f trafi\u011fi ve <code>up<\/code> durumu. TTFB&#8217;yi milisaniye hassasiyetinde izlemek istiyorsan\u0131z \u00f6nce uygulama ve cache \u00f6l\u00e7\u00fcm\u00fcn\u00fcn ger\u00e7ekten kurulu oldu\u011fundan emin olun.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>\u0130pucu: Kurulumdan sonra \u00f6nce Prometheus&#039;un \/targets ekran\u0131n\u0131, ard\u0131ndan Grafana&#039;daki up sorgusunu kontrol edin. Hedef UP g\u00f6r\u00fcnmeden dashboard i\u00e7e aktarmak sorunu yaln\u0131zca daha renkli hale getirir.<\/p>\n<\/div>\n<h2 id=\"prometheus-ile-hangi-alarmlar-kurulmali\">Prometheus ile hangi alarmlar kurulmal\u0131?<\/h2>\n<p>Grafik g\u00f6rmek ile olaydan haberdar olmak ayn\u0131 \u015fey de\u011fildir. Prometheus alerting rule dosyalar\u0131 ko\u015fullar\u0131 tan\u0131mlar; Alertmanager ise gruplama, susturma ve e-posta, webhook veya ba\u015fka bildirim kanallar\u0131n\u0131 y\u00f6netir. K\u00fc\u00e7\u00fck bir VPS i\u00e7in ilk alarmlar \u00f6l\u00e7\u00fclebilir ve eyleme d\u00f6n\u00fck olmal\u0131d\u0131r.<\/p>\n<pre><code>groups:\n  - name: vps-health\n    rules:\n      - alert: InstanceDown\n        expr: up{job=\"node\"} == 0\n        for: 5m\n        labels:\n          severity: critical\n        annotations:\n          summary: \"Node Exporter eri\u015filemiyor\"\n\n      - alert: RootFilesystemLow\n        expr: 100 * node_filesystem_avail_bytes{mountpoint=\"\/\",fstype!=\"rootfs\"} \/ node_filesystem_size_bytes{mountpoint=\"\/\"} &lt; 15\n        for: 10m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"Root dosya sisteminde bo\u015f alan az\"\n\n      - alert: HighMemoryPressure\n        expr: 100 * (1 - node_memory_MemAvailable_bytes \/ node_memory_MemTotal_bytes) &gt; 90\n        for: 10m\n        labels:\n          severity: warning\n        annotations:\n          summary: \"Kullan\u0131labilir bellek d\u00fc\u015f\u00fck\"<\/code><\/pre>\n<p>Dosya sistemi sorgular\u0131nda <code>fstype<\/code>, <code>mountpoint<\/code> ve <code>device<\/code> etiketlerini ortam\u0131n\u0131za g\u00f6re daralt\u0131n. Aksi halde <code>\/run<\/code>, container bind mount&#8217;lar\u0131 veya sanal dosya sistemleri gereksiz alarm \u00fcretebilir. Alarm e\u015fi\u011fini ger\u00e7ek \u00e7al\u0131\u015fma desenini g\u00f6rd\u00fckten sonra belirlemek, gece boyunca s\u00fcren sahte alarmlar\u0131 azalt\u0131r.<\/p>\n<p>Alarm dosyas\u0131n\u0131 Prometheus&#8217;a tan\u0131tmak i\u00e7in <code>rule_files<\/code> alan\u0131n\u0131 yap\u0131land\u0131r\u0131n ve kurallar\u0131 do\u011frulay\u0131n:<\/p>\n<pre><code>sudo -u prometheus promtool check rules \/etc\/prometheus\/alerts.yml\nsudo systemctl reload prometheus<\/code><\/pre>\n<p>Bir alarm tan\u0131mlamak yetmez. Bildirimin ger\u00e7ekten ula\u015ft\u0131\u011f\u0131n\u0131 test edin; e-posta, webhook veya telefon uygulamas\u0131nda teslim bilgisi g\u00f6r\u00fcnmelidir. \u0130zleme sisteminin kendisi de izlenmelidir. Prometheus servisi durmu\u015fsa Grafana paneli bir s\u00fcre eski veriyi g\u00f6stererek sahte g\u00fcven yaratabilir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Her kritik alarm i\u00e7in e\u015fik, bekleme s\u00fcresi, bildirim kanal\u0131 ve m\u00fcdahale ad\u0131m\u0131n\u0131 yaz\u0131l\u0131 hale getirin.<\/p>\n<h2 id=\"izleme-verisi-ne-kadar-sure-saklanmali\">\u0130zleme verisi ne kadar s\u00fcre saklanmal\u0131?<\/h2>\n<p>Prometheus varsay\u0131lan olarak veriyi yerel TSDB alan\u0131nda saklar. Saklama s\u00fcresi ve disk s\u0131n\u0131r\u0131 i\u00e7in servis parametreleri kullan\u0131labilir:<\/p>\n<pre><code>--storage.tsdb.retention.time=15d\n--storage.tsdb.retention.size=20GB<\/code><\/pre>\n<p>Zaman ve boyut s\u0131n\u0131rlar\u0131n\u0131 birlikte kullanmak daha \u00f6ng\u00f6r\u00fclebilir bir disk kullan\u0131m\u0131 sa\u011flar. Boyut s\u0131n\u0131r\u0131 diskin tamamen dolmas\u0131n\u0131 engellemeye yard\u0131mc\u0131 olur; i\u015fletim sistemi, Grafana ve loglar i\u00e7in ayr\u0131ca bo\u015f alan b\u0131rak\u0131lmal\u0131d\u0131r. Prometheus verisini ayn\u0131 diskteki yo\u011fun uygulama loglar\u0131yla yar\u0131\u015ft\u0131rmay\u0131n.<\/p>\n<p>Uzun d\u00f6nem kapasite veya \u00e7ok say\u0131da VPS izlenecekse remote write, Thanos veya ba\u015fka uzun s\u00fcreli depolama mimarileri de\u011ferlendirilebilir. K\u00fc\u00e7\u00fck bir VPS&#8217;te \u00f6nce do\u011fru metrikleri ve alarm ak\u0131\u015f\u0131n\u0131 oturtmak daha sa\u011fl\u0131kl\u0131d\u0131r. Snapshot almak geri d\u00f6n\u00fc\u015f i\u00e7in yararl\u0131 olsa da canl\u0131 Prometheus verisinin tek yede\u011fi say\u0131lmaz; <a href=\"https:\/\/www.vps.tc\/blog\/tr\/vps-snapshot-nedir-anlik-yedekleme-rehberi\/\">VPS Snapshot Nedir? Anl\u0131k Yedekleme Rehberi<\/a> ba\u015fl\u0131\u011f\u0131ndaki ayr\u0131m\u0131 dikkate al\u0131n.<\/p>\n<p>Prometheus verisinin yede\u011fi al\u0131nacaksa servisin veri tutarl\u0131l\u0131\u011f\u0131, TSDB belgeleri ve geri d\u00f6n\u00fc\u015f prosed\u00fcr\u00fc ayr\u0131ca test edilmelidir. Grafana dashboard JSON&#8217;lar\u0131, provisioning dosyalar\u0131, alarm kurallar\u0131 ve Prometheus yap\u0131land\u0131rmas\u0131 da yedeklenmelidir. Yaln\u0131zca grafik ekran\u0131n\u0131 yedeklemek izleme sistemini yeniden kurmaya yetmez.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>\u00d6rnek senaryo: 2 vCPU ve 4 GB RAM&#039;li bir VPS&#039;te 15 saniyelik scrape aral\u0131\u011f\u0131yla CPU, bellek, disk ve a\u011f metrikleri izlenebilir. Ancak 300 hedefi tek bir Prometheus&#039;a eklemek yerine hedef ba\u015f\u0131na seri say\u0131s\u0131n\u0131, saklama s\u00fcresini ve disk b\u00fcy\u00fcmesini \u00f6l\u00e7erek kapasite planlay\u0131n.<\/p>\n<\/div>\n<h2 id=\"kurulumdan-sonra-hangi-kontroller-yapilir\">Kurulumdan sonra hangi kontroller yap\u0131l\u0131r?<\/h2>\n<p>\u00d6nce hedef durumunu kontrol edin. Prometheus aray\u00fcz\u00fcnde <code>Status &gt; Targets<\/code> b\u00f6l\u00fcm\u00fcnde Node Exporter hedefi <code>UP<\/code> g\u00f6r\u00fcnmelidir. Ard\u0131ndan ayn\u0131 kontrol\u00fc komut sat\u0131r\u0131ndan yap\u0131n:<\/p>\n<pre><code>curl -s http:\/\/127.0.0.1:9090\/api\/v1\/targets | jq '.data.activeTargets[] | {instance,health,lastError}'<\/code><\/pre>\n<p><code>health<\/code> alan\u0131 <code>up<\/code>, <code>lastError<\/code> alan\u0131 bo\u015fsa scrape ba\u015far\u0131l\u0131d\u0131r. <code>connection refused<\/code> Node Exporter&#8217;\u0131n \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 veya adresin yanl\u0131\u015f oldu\u011funu, <code>context deadline exceeded<\/code> ise firewall ya da a\u011f gecikmesini d\u00fc\u015f\u00fcnd\u00fcr\u00fcr.<\/p>\n<p>Grafana&#8217;da panel sorgular\u0131n\u0131n zaman aral\u0131\u011f\u0131n\u0131 de\u011fi\u015ftirerek eski verinin geldi\u011fini do\u011frulay\u0131n. Ard\u0131ndan bilerek bir test alarm\u0131 \u00fcretin veya Alertmanager test mekanizmas\u0131n\u0131 kullan\u0131n. Alarm\u0131n olu\u015fmas\u0131, gruplanmas\u0131 ve kapanmas\u0131 ayr\u0131 ayr\u0131 g\u00f6r\u00fclmelidir.<\/p>\n<p>\u0130zleme VPS&#8217;inde <code>journalctl -u prometheus<\/code>, <code>journalctl -u grafana-server<\/code> ve disk kullan\u0131m\u0131n\u0131 d\u00fczenli kontrol edin. Bir grafik bo\u015fsa servisi yeniden ba\u015flatmadan \u00f6nce hedef listesini, HTTP endpoint&#8217;ini, etiketleri ve sorguyu kar\u015f\u0131la\u015ft\u0131r\u0131n. Log okumadan restart etmek bazen yaln\u0131zca kan\u0131t\u0131 siler.<\/p>\n<p>DNS \u00fczerinden Grafana yay\u0131nlanacaksa alan ad\u0131n\u0131n do\u011fru IP&#8217;ye \u00e7\u00f6z\u00fcld\u00fc\u011f\u00fcn\u00fc <code>dig +short<\/code> ile kontrol edin. DNS de\u011fi\u015fikliklerinin etkisini anlamak i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/dns-yayilmasi-ne-kadar-surer\/\">DNS Yay\u0131lmas\u0131 Nedir? Ne Kadar S\u00fcrer?<\/a> ba\u015fl\u0131\u011f\u0131ndaki TTL ve resolver ayr\u0131m\u0131ndan yararlanabilirsiniz.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir gece yanl\u0131\u015f sunucuda rm -rf \u00e7al\u0131\u015ft\u0131rmak \u00fczereydim. Tab&#039;a bast\u0131\u011f\u0131mda k\u0131rm\u0131z\u0131 prompt&#039;ta hostname belirince komutu durdurdum; o g\u00fcnden sonra \u00f6zellikle izleme sunucular\u0131nda \u00f6nce hostname ve hedef listesini do\u011fruluyorum.<\/p>\n<\/div>\n<h2 id=\"kurulumu-tamamlamadan-once-sunlari-kontrol-edin\">Kurulumu Tamamlamadan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Prometheus ve Grafana&#039;y\u0131 ayr\u0131, yetkisiz kullan\u0131c\u0131larla \u00e7al\u0131\u015ft\u0131r\u0131n.<\/li>\n<li>Node Exporter&#039;\u0131n 9100 portunu yaln\u0131zca Prometheus sunucusuna a\u00e7\u0131n.<\/li>\n<li>promtool check config ve promtool check rules komutlar\u0131n\u0131 \u00e7al\u0131\u015ft\u0131r\u0131n.<\/li>\n<li>Prometheus Targets ekran\u0131nda b\u00fct\u00fcn hedeflerin UP oldu\u011funu do\u011frulay\u0131n.<\/li>\n<li>Grafana&#039;da CPU, RAM, disk, a\u011f ve up panellerini test edin.<\/li>\n<li>Disk saklama s\u00fcresiyle boyut s\u0131n\u0131r\u0131n\u0131 birlikte yap\u0131land\u0131r\u0131n.<\/li>\n<li>Bir alarm \u00fcretip bildirimin ger\u00e7ekten ula\u015ft\u0131\u011f\u0131n\u0131 ve kapand\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>\u00d6nce tek bir VPS&#039;i izleyip hedef durumunu, disk b\u00fcy\u00fcmesini ve alarm ak\u0131\u015f\u0131n\u0131 birka\u00e7 g\u00fcn g\u00f6zlemleyin. Paneller \u00e7o\u011falmadan \u00f6nce ger\u00e7ekten m\u00fcdahale gerektiren metrikleri ay\u0131klamak, daha sessiz ve g\u00fcvenilir bir izleme sistemi kurar.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>Prometheus ve Grafana aras\u0131ndaki fark nedir?<\/summary>\n<p>Prometheus metrikleri belirli aral\u0131klarla toplar, zaman serisi olarak saklar ve PromQL ile sorgular. Grafana ise Prometheus dahil veri kaynaklar\u0131ndan sonu\u00e7lar\u0131 al\u0131p grafik, tablo ve alarm panellerinde g\u00f6sterir. Grafana tek ba\u015f\u0131na VPS kaynaklar\u0131n\u0131 \u00f6l\u00e7mez; veri kayna\u011f\u0131na ihtiya\u00e7 duyar. Node Exporter da Linux sistem metriklerini Prometheus&#039;un okuyabilece\u011fi formata d\u00f6n\u00fc\u015ft\u00fcr\u00fcr.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Prometheus VPS \u00fczerinde hangi portu kullan\u0131r?<\/summary>\n<p>Prometheus&#039;un web aray\u00fcz\u00fc ve HTTP API&#039;si varsay\u0131lan olarak 9090\/TCP portunu kullan\u0131r. Node Exporter varsay\u0131lan olarak 9100\/TCP, Grafana ise 3000\/TCP portunda dinler. Bu portlar\u0131n \u00fc\u00e7\u00fcn\u00fc de internete a\u00e7mak gerekmez. Prometheus ve Grafana&#039;y\u0131 loopback, VPN veya g\u00fcvenilir y\u00f6netim a\u011f\u0131yla s\u0131n\u0131rland\u0131r\u0131n; Node Exporter&#039;a yaln\u0131zca Prometheus eri\u015fsin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Node Exporter kurulmadan Prometheus kullan\u0131labilir mi?<\/summary>\n<p>Evet, Prometheus kendi metriklerini ve HTTP endpoint sunan ba\u015fka servisleri Node Exporter olmadan da izleyebilir. Ancak Linux&#039;un CPU, bellek, disk ve a\u011f metriklerini kolayca almak i\u00e7in Node Exporter pratik \u00e7\u00f6z\u00fcmd\u00fcr. Uygulama, Nginx veya veritaban\u0131 metrikleri i\u00e7in ayr\u0131ca ilgili exporter ya da native metrics endpoint gerekebilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Grafana dashboard neden veri g\u00f6stermiyor?<\/summary>\n<p>\u00d6nce Grafana&#039;n\u0131n Prometheus veri kayna\u011f\u0131na eri\u015fti\u011fini Save &amp; test ile do\u011frulay\u0131n. Ard\u0131ndan Prometheus&#039;ta Status &gt; Targets ekran\u0131nda hedefin UP olup olmad\u0131\u011f\u0131na bak\u0131n. Hedef DOWN ise adres, port, firewall ve exporter servisini kontrol edin. Hedef UP oldu\u011fu halde panel bo\u015fsa dashboard&#039;un kulland\u0131\u011f\u0131 metrik adlar\u0131n\u0131, etiketleri ve zaman aral\u0131\u011f\u0131n\u0131 mevcut Prometheus verisiyle kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Prometheus verisi ne kadar s\u00fcre saklanmal\u0131?<\/summary>\n<p>Saklama s\u00fcresi hedef say\u0131s\u0131na, scrape aral\u0131\u011f\u0131na, metrik kardinalitesine ve disk kapasitesine g\u00f6re belirlenir. K\u00fc\u00e7\u00fck bir VPS&#039;te 7-15 g\u00fcnl\u00fck yerel saklama ile ba\u015flamak, kullan\u0131m art\u0131\u015f\u0131n\u0131 \u00f6l\u00e7mek i\u00e7in makul olabilir; bu sabit bir standart de\u011fildir. &#8211;storage.tsdb.retention.time ve &#8211;storage.tsdb.retention.size se\u00e7eneklerini birlikte kullan\u0131n, i\u015fletim sistemi i\u00e7in bo\u015f disk alan\u0131 b\u0131rak\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Prometheus alarm g\u00f6nderir mi?<\/summary>\n<p>Prometheus alerting rule ko\u015fullar\u0131n\u0131 de\u011ferlendirir ve alarm durumunu \u00fcretir. E-posta, webhook veya ba\u015fka bildirim kanallar\u0131na y\u00f6nlendirme, gruplama ve susturma i\u015flemleri genellikle Alertmanager ile yap\u0131l\u0131r. up == 0, d\u00fc\u015f\u00fck disk alan\u0131 ve y\u00fcksek bellek kullan\u0131m\u0131 gibi alarmlar i\u00e7in for s\u00fcresi belirleyin. Kurulum tamamland\u0131ktan sonra test alarm\u0131 \u00fcreterek bildirimin ger\u00e7ekten ula\u015ft\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n<\/details>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>VPS kaynaklar\u0131n\u0131 Prometheus ve Grafana ile izlemek i\u00e7in Node Exporter kurulumu, g\u00fcvenli port yap\u0131land\u0131rmas\u0131, dashboard, PromQL sorgular\u0131 ve alarm kurallar\u0131n\u0131 anlatan uygulamal\u0131 bir kurulum.<\/p>\n","protected":false},"author":2,"featured_media":1037,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[873],"tags":[],"class_list":["post-1039","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"lang":"tr","translations":{"tr":1039,"en":1040},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1039","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=1039"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1039\/revisions"}],"predecessor-version":[{"id":1041,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1039\/revisions\/1041"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/1037"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=1039"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=1039"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=1039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}