{"id":4800,"date":"2026-02-08T19:16:30","date_gmt":"2026-02-08T16:16:30","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/merkezi-sunucu-izleme-ve-alarm-mimarisi\/"},"modified":"2026-02-08T19:16:30","modified_gmt":"2026-02-08T16:16:30","slug":"merkezi-sunucu-izleme-ve-alarm-mimarisi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/merkezi-sunucu-izleme-ve-alarm-mimarisi\/","title":{"rendered":"Merkezi Sunucu \u0130zleme ve Alarm Mimarisi"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Neden_Merkezi_Sunucu_Izleme_ve_Alarm_Mimarisi_Kurmalisiniz\"><span class=\"toc_number toc_depth_1\">1<\/span> Neden Merkezi Sunucu \u0130zleme ve Alarm Mimarisi Kurmal\u0131s\u0131n\u0131z?<\/a><\/li><li><a href=\"#Mimari_Temeller_Izleme_Loglama_ve_Izlenebilirlik_Ucgeni\"><span class=\"toc_number toc_depth_1\">2<\/span> Mimari Temeller: \u0130zleme, Loglama ve \u0130zlenebilirlik \u00dc\u00e7geni<\/a><\/li><li><a href=\"#Prometheus_Tabanli_Izleme_Mimarisi\"><span class=\"toc_number toc_depth_1\">3<\/span> Prometheus Tabanl\u0131 \u0130zleme Mimarisi<\/a><ul><li><a href=\"#Prometheusun_Temel_Bilesenleri\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Prometheus\u2019un Temel Bile\u015fenleri<\/a><\/li><li><a href=\"#DCHost_Uzerinde_Tipik_Prometheus_Yerlesimi\"><span class=\"toc_number toc_depth_2\">3.2<\/span> DCHost \u00dczerinde Tipik Prometheus Yerle\u015fimi<\/a><\/li><li><a href=\"#Metrik_Tasarimi_Sadece_CPU_ve_RAM_Yeterli_Degil\"><span class=\"toc_number toc_depth_2\">3.3<\/span> Metrik Tasar\u0131m\u0131: Sadece CPU ve RAM Yeterli De\u011fil<\/a><\/li><li><a href=\"#Alertmanager_ile_Alarm_Gurultusunu_Kontrol_Altina_Almak\"><span class=\"toc_number toc_depth_2\">3.4<\/span> Alertmanager ile Alarm G\u00fcr\u00fclt\u00fcs\u00fcn\u00fc Kontrol Alt\u0131na Almak<\/a><\/li><li><a href=\"#Prometheusun_Olceklenmesi_Onlarca_Sunucudan_Yuzlerce_Sunucuya\"><span class=\"toc_number toc_depth_2\">3.5<\/span> Prometheus\u2019un \u00d6l\u00e7eklenmesi: Onlarca Sunucudan Y\u00fczlerce Sunucuya<\/a><\/li><\/ul><\/li><li><a href=\"#Zabbix_ile_Agent_Tabanli_Izleme_Mimarisi\"><span class=\"toc_number toc_depth_1\">4<\/span> Zabbix ile Agent Tabanl\u0131 \u0130zleme Mimarisi<\/a><ul><li><a href=\"#Zabbix_Mimarisi_Nasil_Calisir\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Zabbix Mimarisi Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/a><\/li><li><a href=\"#Prometheus_mu_Zabbix_mi\"><span class=\"toc_number toc_depth_2\">4.2<\/span> Prometheus mu, Zabbix mi?<\/a><\/li><li><a href=\"#Zabbixte_Pratik_Alarm_Ornekleri\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Zabbix\u2019te Pratik Alarm \u00d6rnekleri<\/a><\/li><\/ul><\/li><li><a href=\"#Grafana_ile_Tek_Merkezden_Gorunurluk_ve_Alarm_Katmani\"><span class=\"toc_number toc_depth_1\">5<\/span> Grafana ile Tek Merkezden G\u00f6r\u00fcn\u00fcrl\u00fck ve Alarm Katman\u0131<\/a><\/li><li><a href=\"#Hosted_Izleme_Cozumleri_Avantajlar_Dezavantajlar_ve_Hibrit_Model\"><span class=\"toc_number toc_depth_1\">6<\/span> Hosted \u0130zleme \u00c7\u00f6z\u00fcmleri: Avantajlar, Dezavantajlar ve Hibrit Model<\/a><\/li><li><a href=\"#Cok_Kiracili_Multi-Tenant_Izleme_Mimarisi_Ajanslar_ve_SaaS_Icin\"><span class=\"toc_number toc_depth_1\">7<\/span> \u00c7ok Kirac\u0131l\u0131 (Multi-Tenant) \u0130zleme Mimarisi: Ajanslar ve SaaS \u0130\u00e7in<\/a><ul><li><a href=\"#PrometheusGrafana_Tarafinda_Cok_Kiracili_Yapi\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Prometheus\/Grafana Taraf\u0131nda \u00c7ok Kirac\u0131l\u0131 Yap\u0131<\/a><\/li><li><a href=\"#Zabbix_Tarafinda_Cok_Kiracili_Yapi\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Zabbix Taraf\u0131nda \u00c7ok Kirac\u0131l\u0131 Yap\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Uzerinde_Ornek_Mimariler\"><span class=\"toc_number toc_depth_1\">8<\/span> DCHost \u00dczerinde \u00d6rnek Mimariler<\/a><ul><li><a href=\"#1_Orta_Olcekli_E-Ticaret_Kumesi\"><span class=\"toc_number toc_depth_2\">8.1<\/span> 1) Orta \u00d6l\u00e7ekli E-Ticaret K\u00fcmesi<\/a><\/li><li><a href=\"#2_Ajanslar_Icin_Onlarca_Musteri_Sitesini_Izleme\"><span class=\"toc_number toc_depth_2\">8.2<\/span> 2) Ajanslar \u0130\u00e7in Onlarca M\u00fc\u015fteri Sitesini \u0130zleme<\/a><\/li><li><a href=\"#3_Colocation_Sunucular_Icin_Veri_Merkezi_Ici_Izleme\"><span class=\"toc_number toc_depth_2\">8.3<\/span> 3) Colocation Sunucular \u0130\u00e7in Veri Merkezi \u0130\u00e7i \u0130zleme<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_ve_Yol_Haritasi_Kucuk_Baslayin_Merkezilestirerek_Buyutun\"><span class=\"toc_number toc_depth_1\">9<\/span> Sonu\u00e7 ve Yol Haritas\u0131: K\u00fc\u00e7\u00fck Ba\u015flay\u0131n, Merkezile\u015ftirerek B\u00fcy\u00fct\u00fcn<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Neden_Merkezi_Sunucu_Izleme_ve_Alarm_Mimarisi_Kurmalisiniz\">Neden Merkezi Sunucu \u0130zleme ve Alarm Mimarisi Kurmal\u0131s\u0131n\u0131z?<\/span><\/h2>\n<p>Bir noktadan sonra tek tek sunuculara SSH ile ba\u011flan\u0131p <strong>htop, df, journalctl<\/strong> bakarak sistem y\u00f6netmek m\u00fcmk\u00fcn olmuyor. Ajans taraf\u0131nda onlarca m\u00fc\u015fterinin sitesini, SaaS taraf\u0131nda y\u00fczlerce kirac\u0131y\u0131, e-ticaret taraf\u0131nda da trafik dalgalanmalar\u0131n\u0131 y\u00f6netirken ihtiyac\u0131n\u0131z olan \u015fey; metriklerin, loglar\u0131n ve alarmlar\u0131n tek bir merkezde topland\u0131\u011f\u0131, iyi tasarlanm\u0131\u015f bir <strong>merkezi izleme ve alarm mimarisi<\/strong> oluyor.<\/p>\n<p>Bu yaz\u0131da, DCHost altyap\u0131s\u0131nda s\u0131k\u00e7a kurdu\u011fumuz mimariler \u00fczerinden giderek <strong>Prometheus + Alertmanager + Grafana<\/strong>, <strong>Zabbix<\/strong> ve <strong>hosted (SaaS) izleme \u00e7\u00f6z\u00fcmlerini<\/strong> ayn\u0131 \u00e7er\u00e7evede ele alaca\u011f\u0131z. Hangi bile\u015fen ne i\u015f yapar, kim hangi durumda daha mant\u0131kl\u0131d\u0131r, \u00e7ok kirac\u0131l\u0131 yap\u0131larda g\u00fcvenli\u011fi ve eri\u015fimi nas\u0131l tasarlars\u0131n\u0131z, g\u00fcr\u00fclt\u00fc yapan alarmlar\u0131 nas\u0131l susturup ger\u00e7ekten kritik olan\u0131 \u00f6ne \u00e7\u0131kar\u0131rs\u0131n\u0131z; hepsini ad\u0131m ad\u0131m konu\u015faca\u011f\u0131z.<\/p>\n<p>Daha \u00f6nce payla\u015ft\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/vps-izleme-ve-alarm-kurulumu-prometheus-grafana-ve-uptime-kuma-ile-baslangic\/\">VPS izleme ve alarm kurulumu i\u00e7in ba\u015flang\u0131\u00e7 rehberinde<\/a> tek <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> \u00f6l\u00e7e\u011finde odaklanm\u0131\u015ft\u0131k. Bu yaz\u0131 ise, \u00e7ok say\u0131da VPS, <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> ve hatta <strong>colocation<\/strong> sunucular\u0131n\u0131z\u0131 kapsayan, kurumsal \u00f6l\u00e7ekte bir <strong>merkezi izleme platformu<\/strong> kurmak isteyenler i\u00e7in daha mimari seviyede bir yol haritas\u0131 olacak.<\/p>\n<h2><span id=\"Mimari_Temeller_Izleme_Loglama_ve_Izlenebilirlik_Ucgeni\">Mimari Temeller: \u0130zleme, Loglama ve \u0130zlenebilirlik \u00dc\u00e7geni<\/span><\/h2>\n<p>Merkezi izleme mimarisi kurarken \u00f6nce neyi nereye koyaca\u011f\u0131n\u0131z\u0131 netle\u015ftirmeniz gerekiyor. Genel kabul g\u00f6rm\u00fc\u015f pratik, altyap\u0131y\u0131 \u00fc\u00e7 katmana ay\u0131rmak:<\/p>\n<ul>\n<li><strong>Metrikler:<\/strong> CPU, RAM, disk, network, HTTP istek say\u0131s\u0131, hata oran\u0131 gibi say\u0131sal, zaman serisi veriler.<\/li>\n<li><strong>Loglar:<\/strong> Uygulama ve sistem loglar\u0131, Nginx\/Apache access.log, error.log, uygulama hatalar\u0131.<\/li>\n<li><strong>\u0130zler (traces):<\/strong> \u00d6zellikle mikroservis ve API tabanl\u0131 yap\u0131larda, bir iste\u011fin u\u00e7tan uca yolculu\u011funun izlenmesi.<\/li>\n<\/ul>\n<p>Bu yaz\u0131n\u0131n oda\u011f\u0131 <strong>metrik ve alarm<\/strong> katman\u0131; ancak ger\u00e7ek hayatta log ve iz katman\u0131n\u0131 da d\u00fczg\u00fcn kurmadan sadece metriklerle s\u00fcrprizleri yakalamak zor olur. \u00d6rne\u011fin <a href=\"https:\/\/www.dchost.com\/blog\/vps-log-yonetimi-nasil-rayina-oturur-grafana-loki-promtail-ile-merkezi-loglama-tutma-sureleri-ve-alarm-kurallari\/\">Grafana Loki + Promtail ile merkezi loglama rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z log mimarisi ile bu yaz\u0131daki metrik mimarisini birle\u015ftirdi\u011finizde, ger\u00e7ekten i\u015f g\u00f6ren bir <strong>observability<\/strong> katman\u0131na yakla\u015fm\u0131\u015f olursunuz.<\/p>\n<h2><span id=\"Prometheus_Tabanli_Izleme_Mimarisi\">Prometheus Tabanl\u0131 \u0130zleme Mimarisi<\/span><\/h2>\n<p><strong>Prometheus<\/strong>, \u00f6zellikle modern Linux altyap\u0131lar\u0131nda fiili standart haline gelmi\u015f, zaman serisi veritaban\u0131 ve \u00e7ekme (pull) tabanl\u0131 metrik toplay\u0131c\u0131s\u0131d\u0131r. En b\u00fcy\u00fck g\u00fcc\u00fc, basit veri modeli, esnek etiketleme (labels) sistemi ve <strong>Alertmanager<\/strong> ile alarm taraf\u0131nda sundu\u011fu esnekliktir.<\/p>\n<h3><span id=\"Prometheusun_Temel_Bilesenleri\">Prometheus\u2019un Temel Bile\u015fenleri<\/span><\/h3>\n<ul>\n<li><strong>Prometheus server:<\/strong> Metrikleri toplayan, saklayan ve sorgulayan ana bile\u015fen.<\/li>\n<li><strong>Exporters:<\/strong> Sunucu ve servislerden metrikleri HTTP endpoint olarak sunan k\u00fc\u00e7\u00fck ajanlar (Node Exporter, MySQL exporter, Nginx exporter vb.).<\/li>\n<li><strong>Alertmanager:<\/strong> Prometheus kurallar\u0131na g\u00f6re \u00fcretilen alarmlar\u0131 toplayan, gruplayan, bast\u0131ran ve e-posta, webhook, chat kanallar\u0131na ileten bile\u015fen.<\/li>\n<li><strong>Grafana:<\/strong> Prometheus\u2019u veri kayna\u011f\u0131 olarak kullan\u0131p g\u00f6rsel dashboard ve ek alarm tabakas\u0131 sunan aray\u00fcz.<\/li>\n<\/ul>\n<p>Prometheus, default yakla\u015f\u0131m olarak <strong>pull (\u00e7ekme)<\/strong> modeli kullan\u0131r; yani her sunucuda \u00e7al\u0131\u015fan exporter\u2019lardan belirli aral\u0131klarla metrik \u00e7eker. Bu, firewall ve g\u00fcvenlik mimarisi a\u00e7\u0131s\u0131ndan hem avantaj hem dezavantaj olabilir; birazdan buna da de\u011finece\u011fiz.<\/p>\n<h3><span id=\"DCHost_Uzerinde_Tipik_Prometheus_Yerlesimi\">DCHost \u00dczerinde Tipik Prometheus Yerle\u015fimi<\/span><\/h3>\n<p>DCHost\u2019ta s\u0131k kulland\u0131\u011f\u0131m\u0131z basit ama \u00f6l\u00e7eklenebilir yerle\u015fim \u015f\u00f6yle:<\/p>\n<ul>\n<li><strong>\u0130zleme sunucusu:<\/strong> Ayr\u0131 bir VPS veya dedicated sunucu; Prometheus + Alertmanager + Grafana burada \u00e7al\u0131\u015f\u0131r.<\/li>\n<li><strong>\u0130zlenen sunucular:<\/strong> Di\u011fer VPS\/dedicated\/colocation sunucular\u0131n\u0131z; her birinde <strong>Node Exporter<\/strong> ve ihtiya\u00e7 varsa uygulama\/DB exporter\u2019lar\u0131 (MySQL, PostgreSQL, Redis vb.).<\/li>\n<li><strong>\u0130leti\u015fim:<\/strong> \u0130zleme sunucusu \u2192 \u0130zlenen sunuculardaki exporter\u2019lara 9100, 9104 vb. portlardan HTTP istek atar.<\/li>\n<\/ul>\n<p>Burada kritik nokta, <strong>g\u00fcvenlik duvar\u0131 (firewall)<\/strong> kurallar\u0131n\u0131 sadece izleme sunucusunun exporter portlar\u0131na eri\u015febilecek \u015fekilde ayarlamak. \u00d6rne\u011fin DCHost VPS\u2019inizde <code>ufw<\/code> veya <code>firewalld<\/code> ile sadece izleme sunucusunun IP\u2019sine 9100 portunu a\u00e7mak iyi bir ba\u015flang\u0131\u00e7t\u0131r. Firewall sertle\u015ftirme konusunda deste\u011fe ihtiya\u00e7 duyarsan\u0131z, daha \u00f6nce payla\u015ft\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/vps-guvenlik-sertlestirme-kontrol-listesi-sshd_config-fail2ban-ve-root-erisimini-kapatmak\/\">VPS g\u00fcvenlik sertle\u015ftirme kontrol listesi<\/a> de i\u015finize yarayacakt\u0131r.<\/p>\n<h3><span id=\"Metrik_Tasarimi_Sadece_CPU_ve_RAM_Yeterli_Degil\">Metrik Tasar\u0131m\u0131: Sadece CPU ve RAM Yeterli De\u011fil<\/span><\/h3>\n<p>Prometheus ile neredeyse <em>her \u015feyi<\/em> \u00f6l\u00e7ebilirsiniz; ama \u00f6l\u00e7mek ayr\u0131, anlaml\u0131 alarm \u00fcretmek ayr\u0131 konu. DCHost\u2019ta pratikte i\u015fe yarayan temel metrik setini \u015f\u00f6yle \u00f6zetleyebiliriz:<\/p>\n<ul>\n<li><strong>Altyap\u0131 metrikleri:<\/strong> CPU kullan\u0131m\u0131, load average, RAM kullan\u0131m\u0131, disk doluluk, disk IO bekleme s\u00fcresi, network trafik ve hata oranlar\u0131.<\/li>\n<li><strong>Servis metrikleri:<\/strong> HTTP 5xx oran\u0131, response time (p95\/p99), active connections, queue length, database connection count, replication lag.<\/li>\n<li><strong>\u0130\u015f metrikleri:<\/strong> Sipari\u015f say\u0131s\u0131, \u00f6deme hata oran\u0131, sepete eklemeden sat\u0131n almaya d\u00f6n\u00fc\u015f\u00fcm gibi KPI\u2019lar.<\/li>\n<\/ul>\n<p>\u00d6zellikle e-ticaret ve SaaS taraf\u0131nda, sadece &#8220;CPU %90 oldu&#8221; diye de\u011fil, &#8220;<strong>\u00f6deme ba\u015far\u0131s\u0131zl\u0131k oran\u0131 5 dakikad\u0131r normalin 3 kat\u0131na \u00e7\u0131kt\u0131<\/strong>&#8221; diye alarm alman\u0131z gerekir. \u0130\u015f metriklerini Prometheus\u2019a push eden basit bir endpoint ekleyerek bunu sa\u011flayabilirsiniz.<\/p>\n<h3><span id=\"Alertmanager_ile_Alarm_Gurultusunu_Kontrol_Altina_Almak\">Alertmanager ile Alarm G\u00fcr\u00fclt\u00fcs\u00fcn\u00fc Kontrol Alt\u0131na Almak<\/span><\/h3>\n<p>Merkezi izleme mimarilerinin s\u0131k yap\u0131lan hatas\u0131, her metrik i\u00e7in ayr\u0131 ayr\u0131 alarm kurmak ve ekibi s\u00fcrekli bildirim bombard\u0131man\u0131na tutmak. Alertmanager taraf\u0131nda \u015fu prensipleri uygulad\u0131\u011f\u0131n\u0131zda hayat \u00e7ok kolayla\u015f\u0131yor:<\/p>\n<ul>\n<li><strong>Grup bazl\u0131 alarmlar:<\/strong> \u00d6rne\u011fin ayn\u0131 uygulama k\u00fcmesindeki 3 sunucuda da CPU y\u00fcksekse tek alarm \u00fcretmek.<\/li>\n<li><strong>Silencing (susturma):<\/strong> Planl\u0131 bak\u0131m, deploy, migration esnas\u0131nda ilgili alarmlar\u0131 etiket bazl\u0131 susturmak.<\/li>\n<li><strong>Routing:<\/strong> Veritaban\u0131 alarmlar\u0131n\u0131 DB ekibine, uygulama alarmlar\u0131n\u0131 web ekibine, altyap\u0131 alarmlar\u0131n\u0131 SRE ekibine y\u00f6nlendirmek.<\/li>\n<li><strong>Inhibit (bast\u0131rma):<\/strong> \u00d6rne\u011fin b\u00fct\u00fcn cluster down oldu\u011funda tek tek node down alarmlar\u0131n\u0131 bast\u0131rmak.<\/li>\n<\/ul>\n<p>Bu seviyede tasar\u0131m yapmak i\u00e7in PromQL ve Alertmanager konfig\u00fcrasyonuna h\u00e2kim olmak \u00f6nemli. Daha operasyonel bir ba\u015flang\u0131\u00e7 yapmak isterseniz, <a href=\"https:\/\/www.dchost.com\/blog\/vps-izleme-ve-uyari-nasil-kurulur-prometheus-grafana-ve-node-exporter-ile-sessiz-alarmlari-konusturmak\/\">Prometheus ve Node Exporter ile sessiz alarmlar\u0131 konu\u015fturdu\u011fumuz rehbere<\/a> g\u00f6z atman\u0131z iyi bir haz\u0131rl\u0131k olur.<\/p>\n<h3><span id=\"Prometheusun_Olceklenmesi_Onlarca_Sunucudan_Yuzlerce_Sunucuya\">Prometheus\u2019un \u00d6l\u00e7eklenmesi: Onlarca Sunucudan Y\u00fczlerce Sunucuya<\/span><\/h3>\n<p>Ba\u015flang\u0131\u00e7ta tek bir Prometheus sunucusu i\u015finizi g\u00f6r\u00fcr. Ancak DCHost \u00fczerinde \u00e7ok say\u0131da VPS, dedicated ve colocation sunucusunu ayn\u0131 merkezde izlemeye ba\u015flay\u0131nca iki konu g\u00fcndeme gelir:<\/p>\n<ul>\n<li><strong>Performans:<\/strong> Scrape s\u00fcresi artar, Prometheus\u2019un kendi CPU ve disk kullan\u0131m\u0131 y\u00fckselir.<\/li>\n<li><strong>Saklama s\u00fcresi:<\/strong> 30\u201390 g\u00fcnl\u00fck metrik tutulmak istendi\u011finde disk kapasitesi h\u0131zla dolar.<\/li>\n<\/ul>\n<p>Burada \u00fc\u00e7 temel strateji vard\u0131r:<\/p>\n<ol>\n<li><strong>Federasyon:<\/strong> B\u00f6lgesel veya proje bazl\u0131 Prometheus instancelar\u0131 kurup, \u00fcst seviye bir Prometheus ile \u00f6zet metrikleri toplamak.<\/li>\n<li><strong>Sharding:<\/strong> Hedef listelerini b\u00f6lerek birden fazla Prometheus sunucusuna payla\u015ft\u0131rmak.<\/li>\n<li><strong>Uzun s\u00fcreli saklama:<\/strong> Metrikleri uzun vadede saklamak i\u00e7in ek bir zaman serisi deposu (\u00f6rne\u011fin Thanos \/ Cortex benzeri \u00e7\u00f6z\u00fcmler) eklemek.<\/li>\n<\/ol>\n<p>K\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli yap\u0131larda federasyon + disk planlamas\u0131 genellikle yeterli olur. \u00c7ok b\u00fcy\u00fck yap\u0131larda ise mimariyi ba\u015ftan \u00e7ok b\u00f6lgeli \u015fekilde tasarlamak gerekir; bu da <a href=\"https:\/\/www.dchost.com\/blog\/cok-bolgeli-mimariler-nasil-kurulur-dns-geo%e2%80%91routing-ve-veritabani-replikasyonu-ile-korkusuz-felaket-dayanikliligi\/\">\u00e7ok b\u00f6lgeli mimari rehberimizde<\/a> de\u011findi\u011fimiz konularla g\u00fczel \u00f6rt\u00fc\u015f\u00fcr.<\/p>\n<h2><span id=\"Zabbix_ile_Agent_Tabanli_Izleme_Mimarisi\">Zabbix ile Agent Tabanl\u0131 \u0130zleme Mimarisi<\/span><\/h2>\n<p><strong>Zabbix<\/strong>, daha klasik anlamda &#8220;hepsi bir arada&#8221; izleme ve alarm \u00e7\u00f6z\u00fcm\u00fc olarak \u00f6ne \u00e7\u0131kar. Agent tabanl\u0131 yap\u0131s\u0131, SNMP deste\u011fi, otomatik ke\u015fif (low-level discovery) ve haz\u0131r \u015fablonlar\u0131yla \u00f6zellikle karma\u015f\u0131k network cihazlar\u0131 ve Windows\/Linux karmas\u0131 ortamlarda h\u00e2l\u00e2 \u00e7ok g\u00fc\u00e7l\u00fc bir oyuncu.<\/p>\n<h3><span id=\"Zabbix_Mimarisi_Nasil_Calisir\">Zabbix Mimarisi Nas\u0131l \u00c7al\u0131\u015f\u0131r?<\/span><\/h3>\n<ul>\n<li><strong>Zabbix Server:<\/strong> T\u00fcm konfig\u00fcrasyonun, alarmlar\u0131n ve metriklerin tutuldu\u011fu ana bile\u015fen.<\/li>\n<li><strong>Zabbix Agent:<\/strong> \u0130zlenecek sunucuya kurulan ajan; CPU, RAM, disk, process, log vb. bilgileri aktif\/pasif modda server\u2019a iletir.<\/li>\n<li><strong>Zabbix Proxy:<\/strong> Uzak networkler veya \u00e7ok say\u0131da host i\u00e7in arac\u0131 katman; veriyi toplay\u0131p Zabbix server\u2019a iletir.<\/li>\n<li><strong>Database + Web UI:<\/strong> MySQL\/PostgreSQL \u00fczerinde \u00e7al\u0131\u015fan konfig\u00fcrasyon veritaban\u0131 ve PHP tabanl\u0131 aray\u00fcz.<\/li>\n<\/ul>\n<p>Prometheus\u2019tan farkl\u0131 olarak Zabbix, hem <strong>agent push\/pull<\/strong> hem de <strong>SNMP<\/strong> ile \u00e7al\u0131\u015fabilir. Bu da \u00f6zellikle switch, router, firewall gibi network cihazlar\u0131n\u0131n izlenmesinde b\u00fcy\u00fck avantaj sa\u011flar.<\/p>\n<h3><span id=\"Prometheus_mu_Zabbix_mi\">Prometheus mu, Zabbix mi?<\/span><\/h3>\n<p>DCHost\u2019ta g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ger\u00e7ek senaryolarda, se\u00e7im genelde \u015fu kriterlere g\u00f6re \u015fekilleniyor:<\/p>\n<ul>\n<li><strong>Modern Linux + container a\u011f\u0131rl\u0131kl\u0131 ortamlar:<\/strong> Prometheus + Grafana \u00e7o\u011fu zaman daha esnek, \u00f6l\u00e7eklenebilir ve geli\u015ftirici dostu.<\/li>\n<li><strong>A\u011f cihazlar\u0131 yo\u011fun, Windows sunucular\u0131n a\u011f\u0131rl\u0131kta oldu\u011fu karma ortamlarda:<\/strong> Zabbix\u2019in agent + SNMP yetenekleri daha h\u0131zl\u0131 devreye al\u0131nabiliyor.<\/li>\n<li><strong>Mevcut ekip yetkinli\u011fi:<\/strong> Linux ve PromQL bilen bir SRE ekibi varsa Prometheus; daha klasik izleme d\u00fcnyas\u0131na al\u0131\u015fk\u0131n bir ekip varsa Zabbix ile ba\u015flamak daha konforlu.<\/li>\n<\/ul>\n<p>Ger\u00e7ekte pek \u00e7ok kurumda hibrit yakla\u015f\u0131m da g\u00f6r\u00fcyoruz: Altyap\u0131 metrikleri Prometheus ile, network ve baz\u0131 legacy sunucular Zabbix ile izleniyor; \u00fcstte ise <strong>Grafana<\/strong> hepsini tek ekranda birle\u015ftiriyor.<\/p>\n<h3><span id=\"Zabbixte_Pratik_Alarm_Ornekleri\">Zabbix\u2019te Pratik Alarm \u00d6rnekleri<\/span><\/h3>\n<p>Zabbix\u2019in haz\u0131r \u015fablonlar\u0131yla gelen ama \u00e7o\u011fu zaman ince ayar gerektiren baz\u0131 tipik alarmlar:<\/p>\n<ul>\n<li><strong>Disk doluluk:<\/strong> %80\u2019de uyar\u0131, %90\u2019da kritik; ama data diski ile log diski i\u00e7in ayr\u0131 e\u015fikler belirlemek.<\/li>\n<li><strong>Ping \/ agent down:<\/strong> \u00d6zellikle DCHost d\u0131\u015f\u0131 ofis\/\u015fube cihazlar\u0131 i\u00e7in ba\u011flant\u0131 problemlerini erken yakalamak.<\/li>\n<li><strong>Log trigger\u2019lar\u0131:<\/strong> Belirli hata mesajlar\u0131n\u0131 log i\u00e7inde aray\u0131p alarm \u00fcretmek (\u00f6rne\u011fin \u00f6deme altyap\u0131s\u0131 hatalar\u0131).<\/li>\n<li><strong>Servis kontrol\u00fc:<\/strong> Nginx, PHP-FPM, MySQL gibi servislerin \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 periyodik olarak test etmek.<\/li>\n<\/ul>\n<p>Zabbix\u2019in en b\u00fcy\u00fck avantajlar\u0131ndan biri, bu t\u00fcr kontroller i\u00e7in <strong>haz\u0131r template ekosisteminin<\/strong> zengin olmas\u0131. Ancak yine de kendi ortam\u0131n\u0131za uyarlarken e\u015fik de\u011ferlerini, s\u00fcreleri ve ba\u011f\u0131ml\u0131l\u0131klar\u0131 iyi d\u00fc\u015f\u00fcnmek gerekiyor.<\/p>\n<h2><span id=\"Grafana_ile_Tek_Merkezden_Gorunurluk_ve_Alarm_Katmani\">Grafana ile Tek Merkezden G\u00f6r\u00fcn\u00fcrl\u00fck ve Alarm Katman\u0131<\/span><\/h2>\n<p>\u0130ster Prometheus, ister Zabbix, ister hosted izleme kullan\u0131yor olun; i\u015f sonunda ekiplerin bakt\u0131\u011f\u0131 yer \u00e7o\u011fu zaman <strong>Grafana dashboard\u2019lar\u0131<\/strong> oluyor. \u00c7\u00fcnk\u00fc Grafana:<\/p>\n<ul>\n<li>Pek \u00e7ok veri kayna\u011f\u0131n\u0131 (Prometheus, Zabbix, Loki, MySQL, Elastic vb.) tek ekranda birle\u015ftirebilir.<\/li>\n<li>Uygulama, veritaban\u0131, altyap\u0131 ve i\u015f metriklerini tek panelde g\u00f6sterebilir.<\/li>\n<li>Kendi alarm mekanizmas\u0131na sahip oldu\u011fu i\u00e7in baz\u0131 durumlarda Alertmanager\/Zabbix trigger\u2019lar\u0131n\u0131 tamamlayabilir.<\/li>\n<\/ul>\n<p>\u00d6rne\u011fin bir WooCommerce sitesi i\u00e7in \u015funlar\u0131 ayn\u0131 ekranda g\u00f6rmek isteyebilirsiniz:<\/p>\n<ul>\n<li>CPU, RAM, disk IO (Node Exporter\/Prometheus)<\/li>\n<li>MySQL query per second ve slow query say\u0131s\u0131 (MySQL exporter)<\/li>\n<li>HTTP 5xx oran\u0131 ve responce time percentiles (Nginx\/Load balancer metrikleri)<\/li>\n<li>Sepete ekleme \u2192 \u00f6deme ak\u0131\u015f\u0131nda d\u00f6n\u00fc\u015f\u00fcm oran\u0131 (i\u015f metrikleri)<\/li>\n<\/ul>\n<p>Bu yap\u0131y\u0131 kurarken, daha \u00f6nce detayl\u0131 inceledi\u011fimiz <a href=\"https:\/\/www.dchost.com\/blog\/e-ticaret-siteleri-icin-log-analizi-donusum-kaybi-4xx-5xx-ve-odeme-hatalarini-yakalamak\/\">e-ticaret siteleri i\u00e7in log analizi rehberindeki \u00f6deme hatas\u0131 yakalama taktikleri<\/a> ile metrik ve alarm taraf\u0131n\u0131 birle\u015ftirmek, hem teknik hem i\u015f ekipleri i\u00e7in \u00e7ok de\u011ferli oluyor.<\/p>\n<h2><span id=\"Hosted_Izleme_Cozumleri_Avantajlar_Dezavantajlar_ve_Hibrit_Model\">Hosted \u0130zleme \u00c7\u00f6z\u00fcmleri: Avantajlar, Dezavantajlar ve Hibrit Model<\/span><\/h2>\n<p>Kendi Prometheus veya Zabbix altyap\u0131n\u0131z\u0131 kurmak yerine, <strong>hosted (SaaS) izleme servisleri<\/strong> kullanmak da bir se\u00e7enek. Bu t\u00fcr \u00e7\u00f6z\u00fcmler genellikle a\u015fa\u011f\u0131daki avantajlar\u0131 sunar:<\/p>\n<ul>\n<li>Altyap\u0131 y\u00f6netimi, \u00f6l\u00e7eklendirme ve yedeklemenin servis sa\u011flay\u0131c\u0131 taraf\u0131ndan yap\u0131lmas\u0131.<\/li>\n<li>Haz\u0131r dashboard \u015fablonlar\u0131, entegrasyonlar ve geli\u015fmi\u015f uyar\u0131 kanallar\u0131.<\/li>\n<li>Tak\u0131m y\u00f6netimi, yetkilendirme ve audit log gibi kurumsal \u00f6zellikler.<\/li>\n<\/ul>\n<p>Ancak baz\u0131 dezavantajlar\u0131 da vard\u0131r:<\/p>\n<ul>\n<li>Verinin \u00fclke d\u0131\u015f\u0131na \u00e7\u0131kmas\u0131 durumunda <strong>KVKK\/GDPR<\/strong> a\u00e7\u0131s\u0131ndan de\u011ferlendirme gerekebilir.<\/li>\n<li>\u00c7ok yo\u011fun metrik hacminde <strong>ayl\u0131k maliyet<\/strong> h\u0131zla artabilir.<\/li>\n<li>\u0130nternet ba\u011flant\u0131s\u0131na ba\u011f\u0131ml\u0131l\u0131k; i\u00e7 network\u2019teki baz\u0131 sistemleri izlemek zorla\u015fabilir.<\/li>\n<\/ul>\n<p>Bu nedenle DCHost taraf\u0131nda s\u0131k\u00e7a g\u00f6rd\u00fc\u011f\u00fcm\u00fcz model, <strong>hibrit yakla\u015f\u0131md\u0131r<\/strong>:<\/p>\n<ul>\n<li>Kritik altyap\u0131 metrikleri (CPU, RAM, disk, network, veritaban\u0131) i\u00e7in <strong>self-hosted Prometheus\/Zabbix<\/strong>.<\/li>\n<li>Uptime, SSL s\u00fcresi, domain sona erme tarihi gibi d\u0131\u015far\u0131dan izlenmesi gereken bile\u015fenler i\u00e7in <strong>hosted uptime\/website monitoring<\/strong> servisleri.<\/li>\n<\/ul>\n<p>Web sitenizin d\u0131\u015far\u0131dan eri\u015filebilirli\u011fini, SSL ve domain alarm sistemlerini kurmak i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/web-sitesi-uptime-izleme-ve-alarm-kurma-rehberi\/\">uptime izleme rehberimiz<\/a> ve ajanslar i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-musteri-sitelerini-izleme-mimarisi-uptime-ssl-ve-domain-alarm-sistemi\/\">m\u00fc\u015fteri sitelerini izleme mimarisi yaz\u0131m\u0131z<\/a>, bu hibrit yakla\u015f\u0131m\u0131 prati\u011fe d\u00f6kmek i\u00e7in iyi bir tamamlay\u0131c\u0131d\u0131r.<\/p>\n<h2><span id=\"Cok_Kiracili_Multi-Tenant_Izleme_Mimarisi_Ajanslar_ve_SaaS_Icin\">\u00c7ok Kirac\u0131l\u0131 (Multi-Tenant) \u0130zleme Mimarisi: Ajanslar ve SaaS \u0130\u00e7in<\/span><\/h2>\n<p>Ajanslar, SaaS sa\u011flay\u0131c\u0131lar\u0131 ve \u00e7ok markal\u0131 gruplar i\u00e7in izleme sisteminin en zor k\u0131sm\u0131, <strong>izin ve ayr\u0131\u015ft\u0131rma<\/strong> mimarisi oluyor. \u0130\u015fte burada etiketler (labels), klas\u00f6r yap\u0131lar\u0131 ve proje bazl\u0131 izolasyon kritik hale geliyor.<\/p>\n<h3><span id=\"PrometheusGrafana_Tarafinda_Cok_Kiracili_Yapi\">Prometheus\/Grafana Taraf\u0131nda \u00c7ok Kirac\u0131l\u0131 Yap\u0131<\/span><\/h3>\n<ul>\n<li>Her m\u00fc\u015fteri veya \u00fcr\u00fcn i\u00e7in <strong>label stratejisi<\/strong> belirleyin: <code>customer=\"musteriA\"<\/code>, <code>env=\"prod\"<\/code>, <code>service=\"web\"<\/code> gibi.<\/li>\n<li>Grafana\u2019da <strong>folder ve team<\/strong> yap\u0131s\u0131n\u0131 kullanarak dashboard\u2019lar\u0131 m\u00fc\u015fteri veya \u00fcr\u00fcn bazl\u0131 ay\u0131r\u0131n.<\/li>\n<li>Data source\u2019lar\u0131 ortak tutup dashboard seviyesinde <strong>de\u011fi\u015fkenler (variables)<\/strong> ile filtreleme yap\u0131n.<\/li>\n<li>Alertmanager taraf\u0131nda <strong>routing rules<\/strong> ile m\u00fc\u015fteriye \u00f6zel alarm e-posta\/kanal tan\u0131mlay\u0131n.<\/li>\n<\/ul>\n<p>B\u00f6ylece hem tek bir merkezi izleme altyap\u0131s\u0131 y\u00f6netir, hem de farkl\u0131 m\u00fc\u015fterilerin verilerini mant\u0131ksal olarak ayr\u0131\u015ft\u0131rm\u0131\u015f olursunuz. Gerekti\u011finde fiziksel veya sanal olarak da ay\u0131rmak (ayr\u0131 Prometheus instancelar\u0131) m\u00fcmk\u00fcn.<\/p>\n<h3><span id=\"Zabbix_Tarafinda_Cok_Kiracili_Yapi\">Zabbix Taraf\u0131nda \u00c7ok Kirac\u0131l\u0131 Yap\u0131<\/span><\/h3>\n<ul>\n<li>Her m\u00fc\u015fteri i\u00e7in ayr\u0131 <strong>host group<\/strong> ve m\u00fcmk\u00fcnse ayr\u0131 <strong>proxy<\/strong> kullanmak, network ve yetki izolasyonu sa\u011flar.<\/li>\n<li>Kullan\u0131c\u0131 gruplar\u0131n\u0131 host group bazl\u0131 yetkilendirerek, her m\u00fc\u015fterinin sadece kendi sunucular\u0131n\u0131 g\u00f6rmesini sa\u011flayabilirsiniz.<\/li>\n<li>Trigger ve alarm kurallar\u0131n\u0131 host template\u2019ler \u00fczerinden y\u00f6neterek, m\u00fc\u015fteri bazl\u0131 ince ayarlar\u0131 kopyalamadan uygulayabilirsiniz.<\/li>\n<\/ul>\n<p>Hem Prometheus hem Zabbix taraf\u0131nda, \u00e7ok kirac\u0131l\u0131 mimariyi kurarken <strong>log taraf\u0131n\u0131 da unutmamak<\/strong> \u00f6nemli. \u00d6rne\u011fin <a href=\"https:\/\/www.dchost.com\/blog\/merkezi-loglama-ve-gozlemlenebilirlik-vpste-loki-promtail-grafana-ile-sakin-kalan-bir-zihin\/\">Loki + Promtail + Grafana ile merkezi loglama rehberimizde<\/a> anlatt\u0131\u011f\u0131m\u0131z label stratejisini, Prometheus\u2019taki label yap\u0131n\u0131zla uyumlu kurarsan\u0131z, hem metrik hem log taraf\u0131nda ayn\u0131 filtrelerle \u00e7al\u0131\u015fabilirsiniz.<\/p>\n<h2><span id=\"DCHost_Uzerinde_Ornek_Mimariler\">DCHost \u00dczerinde \u00d6rnek Mimariler<\/span><\/h2>\n<h3><span id=\"1_Orta_Olcekli_E-Ticaret_Kumesi\">1) Orta \u00d6l\u00e7ekli E-Ticaret K\u00fcmesi<\/span><\/h3>\n<p>Senaryo: DCHost \u00fczerinde 3 web VPS\u2019i, 2 veritaban\u0131 VPS\u2019i, 1 Redis sunucusu ve bir de arka plan i\u015fleri i\u00e7in ayr\u0131 bir VPS \u00e7al\u0131\u015f\u0131yor.<\/p>\n<ul>\n<li>Merkezi izleme i\u00e7in ayr\u0131 bir DCHost VPS \u00fczerinde <strong>Prometheus + Alertmanager + Grafana<\/strong>.<\/li>\n<li>T\u00fcm uygulama ve veritaban\u0131 sunucular\u0131nda <strong>Node Exporter<\/strong>, DB\/Redis exporter\u2019lar\u0131.<\/li>\n<li>Nginx\/Apache access loglar\u0131, ayr\u0131 bir DCHost VPS\u2019inde \u00e7al\u0131\u015fan <strong>Loki<\/strong>\u2019ye Promtail ile ak\u0131yor.<\/li>\n<li>Uptime, SSL s\u00fcresi ve domain biti\u015f tarihleri, harici uptime izleme + DNS\/WHOIS monitoring ile takip ediliyor.<\/li>\n<\/ul>\n<p>Bu mimaride, sepet veya \u00f6deme ad\u0131m\u0131nda hata art\u0131\u015f\u0131 oldu\u011funda hem <strong>Prometheus metriklerinden<\/strong> (HTTP 5xx, response time) hem de <strong>Loki loglar\u0131ndan<\/strong> (belirli \u00f6deme hatas\u0131 kodlar\u0131) tetiklenen alarmlar ile birka\u00e7 dakika i\u00e7inde sorunu fark etmek m\u00fcmk\u00fcn.<\/p>\n<h3><span id=\"2_Ajanslar_Icin_Onlarca_Musteri_Sitesini_Izleme\">2) Ajanslar \u0130\u00e7in Onlarca M\u00fc\u015fteri Sitesini \u0130zleme<\/span><\/h3>\n<p>Senaryo: Ajans olarak DCHost \u00fczerinde reseller, shared hosting ve birka\u00e7 VPS\/dedicated ile 50+ WordPress\/WooCommerce sitesi y\u00f6netiyorsunuz.<\/p>\n<ul>\n<li>Merkezi izleme i\u00e7in tek bir DCHost VPS\u2019inde <strong>Prometheus + Grafana<\/strong>.<\/li>\n<li>Y\u00fcksek trafikli veya kritik sitelerin bulundu\u011fu VPS\/dedicated sunucularda Node Exporter.<\/li>\n<li>T\u00fcm siteler i\u00e7in harici <strong>uptime + SSL + domain izleme<\/strong> (hibrit model).<\/li>\n<li>Grafana\u2019da m\u00fc\u015fteri bazl\u0131 klas\u00f6rler, ajans i\u00e7i ekipler i\u00e7in farkl\u0131 dashboard ve alarm kanallar\u0131.<\/li>\n<\/ul>\n<p>B\u00f6yle bir yap\u0131da, uptime ve SSL taraf\u0131 i\u00e7in ajanslara \u00f6zel haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-icin-musteri-sitelerini-izleme-mimarisi-uptime-ssl-ve-domain-alarm-sistemi\/\">m\u00fc\u015fteri sitelerini izleme mimarisi rehberi<\/a> ile bu yaz\u0131daki metrik tabanl\u0131 izlemeyi birle\u015ftirmek, ajans\u0131n operasyon y\u00fck\u00fcn\u00fc ciddi bi\u00e7imde hafifletiyor.<\/p>\n<h3><span id=\"3_Colocation_Sunucular_Icin_Veri_Merkezi_Ici_Izleme\">3) Colocation Sunucular \u0130\u00e7in Veri Merkezi \u0130\u00e7i \u0130zleme<\/span><\/h3>\n<p>Senaryo: Kendi fiziksel sunucular\u0131n\u0131z\u0131 DCHost veri merkezinde <strong>colocation<\/strong> ile bar\u0131nd\u0131r\u0131yor, \u00fczerinde hem web uygulamalar\u0131 hem de kurumsal servisler (ERP, CRM vb.) \u00e7al\u0131\u015ft\u0131r\u0131yorsunuz.<\/p>\n<ul>\n<li>Veri merkezi i\u00e7inde izole bir <strong>izleme VLAN\u2019\u0131<\/strong> olu\u015fturarak Prometheus\/Zabbix sunucusunu bu VLAN\u2019a koymak.<\/li>\n<li>T\u00fcm colocation sunucular\u0131nda Node Exporter\/Zabbix Agent \u00e7al\u0131\u015ft\u0131rmak.<\/li>\n<li>Gerekirse Zabbix Proxy veya ek Prometheus instancelar\u0131 ile segmentasyon yapmak.<\/li>\n<li>Uygulama loglar\u0131n\u0131 yine veri merkezi i\u00e7indeki merkezi bir Loki\/ELK k\u00fcmesine toplamak.<\/li>\n<\/ul>\n<p>B\u00f6ylece hem internet ba\u011f\u0131ml\u0131l\u0131\u011f\u0131n\u0131z azal\u0131r, hem de veri merkezinin sa\u011flad\u0131\u011f\u0131 d\u00fc\u015f\u00fck gecikme ve y\u00fcksek bant geni\u015fli\u011fi ile izleme trafi\u011fini d\u0131\u015far\u0131 \u00e7\u0131karmadan y\u00f6netmi\u015f olursunuz.<\/p>\n<h2><span id=\"Sonuc_ve_Yol_Haritasi_Kucuk_Baslayin_Merkezilestirerek_Buyutun\">Sonu\u00e7 ve Yol Haritas\u0131: K\u00fc\u00e7\u00fck Ba\u015flay\u0131n, Merkezile\u015ftirerek B\u00fcy\u00fct\u00fcn<\/span><\/h2>\n<p>Merkezi sunucu izleme ve alarm mimarisi, bir g\u00fcnde kurup bitecek bir proje de\u011fil; daha \u00e7ok ad\u0131m ad\u0131m in\u015fa edilen, b\u00fcy\u00fcd\u00fck\u00e7e olgunla\u015fan bir altyap\u0131. Burada en sa\u011fl\u0131kl\u0131 yakla\u015f\u0131m, \u00f6nce <strong>kritik birka\u00e7 sistemden<\/strong> ba\u015flay\u0131p, mimariyi oturttuk\u00e7a kapsam\u0131 geni\u015fletmek:<\/p>\n<ol>\n<li>DCHost \u00fczerindeki 1\u20132 kritik VPS\/dedicated sunucunuz i\u00e7in <strong>Node Exporter + Prometheus + Grafana<\/strong> \u00fc\u00e7l\u00fcs\u00fcn\u00fc aya\u011fa kald\u0131r\u0131n.<\/li>\n<li>CPU, RAM, disk, HTTP 5xx ve SSL biti\u015f s\u00fcresi gibi birka\u00e7 <strong>net alarm kural\u0131<\/strong> tan\u0131mlay\u0131n.<\/li>\n<li>Daha sonra veritaban\u0131, queue, cache ve i\u015f metriklerini ekleyin.<\/li>\n<li>\u0130htiya\u00e7 olduk\u00e7a Zabbix veya hosted izleme \u00e7\u00f6z\u00fcmlerini hibrit bir modelde devreye al\u0131n.<\/li>\n<\/ol>\n<p>DCHost olarak hem <strong>VPS<\/strong>, <strong>dedicated sunucu<\/strong> hem de <strong>colocation<\/strong> altyap\u0131lar\u0131nda bu t\u00fcr merkezi izleme mimarilerini ger\u00e7ek projeler \u00fczerinde kurup y\u00f6netiyoruz. Kendi altyap\u0131n\u0131z i\u00e7in uygun yakla\u015f\u0131m\u0131 netle\u015ftirmek, kapasite plan\u0131 \u00e7\u0131karmak veya Prometheus\/Zabbix kurulumunu DCHost \u00fczerinde konumland\u0131rmak isterseniz, ekibimizle birlikte somut bir yol haritas\u0131 \u00e7\u0131karmaktan memnuniyet duyar\u0131z.<\/p>\n<p>\u0130zleme mimarinizi kurdu\u011funuzda, sadece kesintileri daha h\u0131zl\u0131 fark etmeyecek; ayn\u0131 zamanda <strong>kapasite planlama<\/strong>, <strong>maliyet optimizasyonu<\/strong> ve <strong>g\u00fcvenlik denetimleri<\/strong> i\u00e7in de \u00e7ok g\u00fc\u00e7l\u00fc bir veri kayna\u011f\u0131 elde etmi\u015f olacaks\u0131n\u0131z. Bir sonraki ad\u0131mda log ve iz katman\u0131n\u0131 da bu yap\u0131ya ekleyerek, ger\u00e7ekten b\u00fct\u00fcnl\u00fckl\u00fc bir <em>observability<\/em> platformuna ge\u00e7mek i\u00e7in rehberlerimizi takip etmeye devam edebilirsiniz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Neden Merkezi Sunucu \u0130zleme ve Alarm Mimarisi Kurmal\u0131s\u0131n\u0131z?2 Mimari Temeller: \u0130zleme, Loglama ve \u0130zlenebilirlik \u00dc\u00e7geni3 Prometheus Tabanl\u0131 \u0130zleme Mimarisi3.1 Prometheus\u2019un Temel Bile\u015fenleri3.2 DCHost \u00dczerinde Tipik Prometheus Yerle\u015fimi3.3 Metrik Tasar\u0131m\u0131: Sadece CPU ve RAM Yeterli De\u011fil3.4 Alertmanager ile Alarm G\u00fcr\u00fclt\u00fcs\u00fcn\u00fc Kontrol Alt\u0131na Almak3.5 Prometheus\u2019un \u00d6l\u00e7eklenmesi: Onlarca Sunucudan Y\u00fczlerce Sunucuya4 Zabbix ile Agent Tabanl\u0131 \u0130zleme Mimarisi4.1 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4801,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4800","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4800","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=4800"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4800\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4801"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4800"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4800"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4800"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}