{"id":245,"date":"2026-11-15T16:07:00","date_gmt":"2026-11-15T16:07:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/?p=245"},"modified":"2026-11-15T16:07:00","modified_gmt":"2026-11-15T16:07:00","slug":"slo-sli-error-budget","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/15\/slo-sli-error-budget\/","title":{"rendered":"SLO, SLI ve Error Budget: G\u00fcvenilirli\u011fi \u00d6l\u00e7\u00fclebilir Hale Getirmek"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><strong>SLO (Service Level Objective)<\/strong>, bir servisin belirli bir s\u00fcre boyunca ula\u015fmas\u0131 hedeflenen g\u00fcvenilirlik seviyesidir. &#8220;Son 30 g\u00fcnde ba\u015far\u0131l\u0131 isteklerin oran\u0131 en az y\u00fczde 99,9 olmal\u0131&#8221; gibi \u00f6l\u00e7\u00fclebilir bir c\u00fcmleyle ifade edilir. &#8220;Sistem h\u0131zl\u0131 ve g\u00fcvenilir olsun&#8221; gibi belirsiz hedeflerin yerine, ekiplerin \u00fczerinde anla\u015fabilece\u011fi somut bir say\u0131 koyar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google&#8217;\u0131n Site Reliability Engineering yakla\u015f\u0131m\u0131yla yayg\u0131nla\u015fan bu kavram, bence sadece b\u00fcy\u00fck \u015firketler i\u00e7in de\u011fil. Birka\u00e7 servisi olan k\u00fc\u00e7\u00fck bir ekip i\u00e7in de &#8220;ne zaman yeni \u00f6zellik geli\u015ftirmeli, ne zaman g\u00fcvenilirli\u011fe odaklanmal\u0131?&#8221; sorusuna net bir cevap veriyor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">SLI, SLO ve SLA aras\u0131ndaki fark nedir?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu \u00fc\u00e7 kavram s\u0131k kar\u0131\u015ft\u0131r\u0131l\u0131yor.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Kavram<\/th><th>Ne<\/th><th>\u00d6rnek<\/th><\/tr><\/thead><tbody><tr><td>SLI<\/td><td>\u00d6l\u00e7\u00fclen g\u00f6sterge<\/td><td>Ba\u015far\u0131l\u0131 isteklerin toplam isteklere oran\u0131<\/td><\/tr><tr><td>SLO<\/td><td>G\u00f6sterge i\u00e7in i\u00e7 hedef<\/td><td>30 g\u00fcnde y\u00fczde 99,9<\/td><\/tr><tr><td>SLA<\/td><td>M\u00fc\u015fteriyle yap\u0131lan s\u00f6zle\u015fme<\/td><td>Y\u00fczde 99,5&#8217;in alt\u0131nda iade<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>SLI (Service Level Indicator)<\/strong> \u00f6l\u00e7t\u00fc\u011f\u00fcn\u00fcz \u015feydir. Bir oran olarak ifade edilmesi en kullan\u0131\u015fl\u0131 halidir: iyi olaylar\u0131n toplam olaylara oran\u0131.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>SLO<\/strong> bu g\u00f6stergeye koydu\u011funuz hedeftir. Ekibin kendi i\u00e7 hedefidir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>SLA<\/strong> ise m\u00fc\u015fteriye verilen, ihlali halinde yapt\u0131r\u0131m\u0131 olan bir s\u00f6zd\u00fcr. SLA her zaman SLO&#8217;dan daha gev\u015fek olmal\u0131. \u0130\u00e7 hedefinizi ka\u00e7\u0131rd\u0131\u011f\u0131n\u0131zda m\u00fc\u015fteriye verdi\u011finiz s\u00f6z\u00fc h\u00e2l\u00e2 tutabiliyor olman\u0131z gerekir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u0130yi bir SLI nas\u0131l se\u00e7ilir?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SLI, kullan\u0131c\u0131n\u0131n deneyimini yans\u0131tmal\u0131. Sunucunun CPU kullan\u0131m\u0131 bir SLI de\u011fildir. Kullan\u0131c\u0131 CPU&#8217;yu g\u00f6rmez, sayfan\u0131n a\u00e7\u0131l\u0131p a\u00e7\u0131lmad\u0131\u011f\u0131n\u0131 g\u00f6r\u00fcr.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">En s\u0131k kullan\u0131lan SLI t\u00fcrleri:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Eri\u015filebilirlik:<\/strong> ba\u015far\u0131l\u0131 cevaplar\u0131n oran\u0131. <code>5xx<\/code> d\u00f6nmeyen isteklerin toplam isteklere oran\u0131 gibi.<\/li>\n\n\n<li><strong>Gecikme:<\/strong> belirli bir s\u00fcrenin alt\u0131nda tamamlanan isteklerin oran\u0131. &#8220;\u0130steklerin y\u00fczde 95&#8217;i 300 ms&#8217;nin alt\u0131nda.&#8221;<\/li>\n\n\n<li><strong>Do\u011fruluk:<\/strong> do\u011fru sonu\u00e7 \u00fcreten i\u015flemlerin oran\u0131. Bir veri i\u015fleme hatt\u0131 i\u00e7in \u00f6nemli.<\/li>\n\n\n<li><strong>Tazelik:<\/strong> belirli bir s\u00fcreden daha eski olmayan verinin oran\u0131. Bir raporun veya arama index&#8217;inin g\u00fcncelli\u011fi i\u00e7in.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Gecikme SLI&#8217;\u0131n\u0131 ortalama yerine e\u015fik alt\u0131ndaki isteklerin oran\u0131 olarak tan\u0131mlamak \u00f6nemli. Ortalama, yava\u015f isteklerin varl\u0131\u011f\u0131n\u0131 gizler. Bu konuyu <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/11\/latency-percentiles-load-testing\/\">yan\u0131t s\u00fcresi y\u00fczdelikleri<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">SLI&#8217;\u0131n nerede \u00f6l\u00e7\u00fcld\u00fc\u011f\u00fc de \u00f6nemli. Uygulama sunucusunda \u00f6l\u00e7\u00fclen ba\u015far\u0131 oran\u0131, load balancer&#8217;da reddedilen veya hi\u00e7 sunucuya ula\u015famayan istekleri g\u00f6remez. Load balancer veya API gateway seviyesinde \u00f6l\u00e7mek, kullan\u0131c\u0131n\u0131n g\u00f6rd\u00fc\u011f\u00fcne daha yak\u0131nd\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">SLO hedefi nas\u0131l belirlenir?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130lk refleks y\u00fczde 100 hedeflemektir. Ama y\u00fczde 100 g\u00fcvenilirlik hem imkans\u0131z hem de istenmeyen bir hedeftir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130mkans\u0131zd\u0131r, \u00e7\u00fcnk\u00fc kullan\u0131c\u0131 ile servis aras\u0131ndaki a\u011f, kullan\u0131c\u0131n\u0131n cihaz\u0131 ve ba\u011flant\u0131s\u0131 sizin kontrol\u00fcn\u00fczde de\u011fildir. Kullan\u0131c\u0131 mobil ba\u011flant\u0131s\u0131nda zaten y\u00fczde 99,5 eri\u015filebilirlik ya\u015f\u0131yorsa, servisinizin y\u00fczde 99,99 olmas\u0131 deneyimini fark edilir \u015fekilde de\u011fi\u015ftirmez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130stenmeyen bir hedeftir, \u00e7\u00fcnk\u00fc her ek dokuz, katlanarak artan bir maliyet getirir.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>SLO<\/th><th>30 g\u00fcnde izin verilen kesinti<\/th><\/tr><\/thead><tbody><tr><td>%99<\/td><td>7 saat 12 dakika<\/td><\/tr><tr><td>%99,5<\/td><td>3 saat 36 dakika<\/td><\/tr><tr><td>%99,9<\/td><td>43 dakika 12 saniye<\/td><\/tr><tr><td>%99,95<\/td><td>21 dakika 36 saniye<\/td><\/tr><tr><td>%99,99<\/td><td>4 dakika 19 saniye<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Y\u00fczde 99,99 hedefi, ayda 4 dakikal\u0131k bir kesinti b\u00fct\u00e7esi demek. Tek bir hatal\u0131 deploy&#8217;u fark edip geri almak bile bu s\u00fcreyi a\u015fabilir. Bu seviye, otomatik geri alma, \u00e7oklu b\u00f6lge ve s\u00fcrekli n\u00f6bet gerektirir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ben hedefi belirlerken ge\u00e7mi\u015f veriden ba\u015flamay\u0131 \u00f6neriyorum. Son \u00fc\u00e7 ayda servis ger\u00e7ekte ne kadar g\u00fcvenilirdi? Kullan\u0131c\u0131lar bu seviyeden \u015fikayet ediyor muydu? E\u011fer etmiyorsa, hedefi mevcut seviyenin biraz alt\u0131na koymak ger\u00e7ek\u00e7i bir ba\u015flang\u0131\u00e7t\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Error budget nedir?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Error budget<\/strong>, SLO&#8217;nun izin verdi\u011fi hata miktar\u0131d\u0131r. Y\u00fczde 99,9 SLO, isteklerin y\u00fczde 0,1&#8217;inin ba\u015far\u0131s\u0131z olabilece\u011fi anlam\u0131na gelir. Ayda 10 milyon istek alan bir servis i\u00e7in bu, 10.000 ba\u015far\u0131s\u0131z istek demektir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu b\u00fct\u00e7e kavram\u0131, SLO&#8217;yu sadece bir \u00f6l\u00e7\u00fcm olmaktan \u00e7\u0131kar\u0131p bir karar arac\u0131na d\u00f6n\u00fc\u015ft\u00fcr\u00fcyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">B\u00fct\u00e7e varsa, ekip risk alabilir. Yeni \u00f6zellikler h\u0131zl\u0131ca deploy edilir, deneyler yap\u0131l\u0131r, b\u00fcy\u00fck refactoring&#8217;ler production&#8217;a \u00e7\u0131kar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">B\u00fct\u00e7e t\u00fckendiyse, \u00f6ncelik de\u011fi\u015fir. Yeni \u00f6zellik deploy&#8217;lar\u0131 yava\u015flar veya durur. Ekip g\u00fcvenilirli\u011fi art\u0131racak i\u015flere, testlere ve otomasyona odaklan\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu mekanizman\u0131n en de\u011ferli yan\u0131, geli\u015ftirme h\u0131z\u0131 ile g\u00fcvenilirlik aras\u0131ndaki klasik tart\u0131\u015fmay\u0131 veriye dayal\u0131 hale getirmesi. &#8220;Bu hafta deploy yapabilir miyiz?&#8221; sorusu art\u0131k bir g\u00f6r\u00fc\u015f meselesi de\u011fil, kalan b\u00fct\u00e7eye bak\u0131larak cevaplanan bir soru.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Error budget politikas\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">B\u00fct\u00e7enin ne zaman ve nas\u0131l uygulanaca\u011f\u0131 \u00f6nceden yaz\u0131l\u0131 olarak kararla\u015ft\u0131r\u0131lmal\u0131. Aksi halde b\u00fct\u00e7e t\u00fckendi\u011finde ilk deadline bask\u0131s\u0131nda g\u00f6rmezden gelinir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Basit bir politika \u015f\u00f6yle olabilir:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>B\u00fct\u00e7enin y\u00fczde 50&#8217;si harcand\u0131\u011f\u0131nda ekip uyar\u0131l\u0131r ve son olaylar g\u00f6zden ge\u00e7irilir.<\/li>\n\n\n<li>B\u00fct\u00e7e t\u00fckendi\u011finde, g\u00fcvenlik d\u00fczeltmeleri ve g\u00fcvenilirlik iyile\u015ftirmeleri d\u0131\u015f\u0131nda deploy yap\u0131lmaz.<\/li>\n\n\n<li>Tek bir olay b\u00fct\u00e7enin y\u00fczde 20&#8217;sinden fazlas\u0131n\u0131 t\u00fckettiyse, bir postmortem yaz\u0131l\u0131r.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Bu politikan\u0131n \u00fcr\u00fcn y\u00f6netimi taraf\u0131ndan da kabul edilmesi \u015fart. Aksi halde m\u00fchendislik ekibinin tek tarafl\u0131 karar\u0131 olarak kal\u0131r ve uygulanmaz. G\u00fcvenilirlik yat\u0131r\u0131m\u0131n\u0131n i\u015f taraf\u0131na nas\u0131l anlat\u0131labilece\u011fini <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/11\/04\/technical-debt-product-conversation\/\">teknik borcu \u00fcr\u00fcn ekibine anlatmak<\/a> yaz\u0131s\u0131nda ele alm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00d6rnek: bir \u00f6deme API&#8217;si i\u00e7in SLO<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Soyut kalmas\u0131n diye bir \u00f6rnek \u00fczerinden gideyim. Bir \u00f6deme API&#8217;si ayda yakla\u015f\u0131k 6 milyon istek al\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130ki SLI tan\u0131ml\u0131yoruz. Eri\u015filebilirlik i\u00e7in, load balancer&#8217;da \u00f6l\u00e7\u00fclen ve <code>5xx<\/code> ile sonu\u00e7lanmayan isteklerin oran\u0131. Gecikme i\u00e7in, 800 ms&#8217;nin alt\u0131nda tamamlanan isteklerin oran\u0131. \u00d6deme sa\u011flay\u0131c\u0131s\u0131na yap\u0131lan d\u0131\u015f \u00e7a\u011fr\u0131 dahil oldu\u011fu i\u00e7in gecikme e\u015fi\u011fi bilerek c\u00f6mert tutuldu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Son \u00fc\u00e7 ay\u0131n verisi eri\u015filebilirli\u011fin y\u00fczde 99,93, gecikme hedefinin ise y\u00fczde 99,4 civar\u0131nda ger\u00e7ekle\u015fti\u011fini g\u00f6steriyor. Buna g\u00f6re hedefleri \u015f\u00f6yle koyuyoruz:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>SLI<\/th><th>SLO<\/th><th>30 g\u00fcnl\u00fck b\u00fct\u00e7e<\/th><\/tr><\/thead><tbody><tr><td>Eri\u015filebilirlik<\/td><td>%99,9<\/td><td>~6.000 ba\u015far\u0131s\u0131z istek<\/td><\/tr><tr><td>Gecikme (&lt; 800 ms)<\/td><td>%99<\/td><td>~60.000 yava\u015f istek<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Ay\u0131n ortas\u0131nda hatal\u0131 bir deploy, 25 dakika boyunca isteklerin neredeyse tamam\u0131nda hata \u00fcretiyor. Dakikada ortalama 140 istekle bu, kabaca 3.500 ba\u015far\u0131s\u0131z istek ve eri\u015filebilirlik b\u00fct\u00e7esinin y\u00fczde 58&#8217;i demek. Politika gere\u011fi olay i\u00e7in bir postmortem yaz\u0131l\u0131yor ve ay\u0131n geri kalan\u0131nda b\u00fcy\u00fck de\u011fi\u015fiklikler, daha dikkatli bir canary s\u00fcreciyle \u00e7\u0131kar\u0131l\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Burada \u00f6nemli olan, karar\u0131n kimsenin hissiyat\u0131na dayanmamas\u0131. B\u00fct\u00e7enin ne kadar\u0131n\u0131n harcand\u0131\u011f\u0131 herkesin g\u00f6rebildi\u011fi bir say\u0131. Deploy h\u0131z\u0131n\u0131n ne zaman d\u00fc\u015f\u00fcr\u00fclece\u011fi de \u00f6nceden yaz\u0131lm\u0131\u015f.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">SLO dashboard&#8217;unda neler olmal\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bir SLO&#8217;nun etkili olmas\u0131 i\u00e7in g\u00f6r\u00fcn\u00fcr olmas\u0131 gerekir. \u0130yi bir dashboard birka\u00e7 soruyu tek bak\u0131\u015fta cevaplar:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Mevcut d\u00f6nemde SLI&#8217;\u0131n de\u011feri ne ve hedefin neresinde?<\/li>\n\n\n<li>B\u00fct\u00e7enin ne kadar\u0131 harcand\u0131, ne kadar\u0131 kald\u0131?<\/li>\n\n\n<li>B\u00fct\u00e7e hangi h\u0131zla t\u00fckeniyor? Bu h\u0131zla d\u00f6nem sonuna ula\u015fabilecek mi?<\/li>\n\n\n<li>B\u00fct\u00e7eyi en \u00e7ok hangi olaylar veya hangi zaman aral\u0131klar\u0131 t\u00fcketti?<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Son madde \u00f6zellikle faydal\u0131. B\u00fct\u00e7enin b\u00fcy\u00fck k\u0131sm\u0131 her gece ayn\u0131 saatte \u00e7al\u0131\u015fan bir toplu i\u015flem s\u0131ras\u0131nda t\u00fckeniyorsa, problem rastgele de\u011fil, sistematiktir.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Burn rate ile alarm kurmak<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">SLO&#8217;lar\u0131n en pratik faydalar\u0131ndan biri, alarmlar\u0131 daha anlaml\u0131 hale getirmeleri.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Klasik alarmlar e\u015fik bazl\u0131d\u0131r: hata oran\u0131 y\u00fczde 1&#8217;i ge\u00e7erse alarm \u00e7al. Bu yakla\u015f\u0131m iki y\u00f6nde hata yapar. K\u0131sa ve zarars\u0131z s\u0131\u00e7ramalarda gereksiz yere uyand\u0131r\u0131r, uzun s\u00fcren d\u00fc\u015f\u00fck seviyeli problemleri ise hi\u00e7 fark etmez.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Burn rate, b\u00fct\u00e7enin hangi h\u0131zla t\u00fckendi\u011fini \u00f6l\u00e7er. Burn rate 1, b\u00fct\u00e7enin tam d\u00f6nem sonunda bitece\u011fi h\u0131zd\u0131r. Burn rate 14,4 ise, 30 g\u00fcnl\u00fck b\u00fct\u00e7e yakla\u015f\u0131k 2 g\u00fcnde biter.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Google&#8217;\u0131n SRE \u00e7al\u0131\u015fma kitab\u0131, farkl\u0131 pencereler ve burn rate e\u015fikleriyle kurulan \u00e7ok pencereli alarmlar\u0131 \u00f6neriyor. \u00d6rne\u011fin son 1 saatte burn rate 14,4&#8217;\u00fc ge\u00e7erse sayfa g\u00f6nder, son 6 saatte 6&#8217;y\u0131 ge\u00e7erse yine sayfa g\u00f6nder, son 3 g\u00fcnde 1&#8217;i ge\u00e7erse bilet a\u00e7. Bu yakla\u015f\u0131m\u0131n ayr\u0131nt\u0131lar\u0131 <a href=\"https:\/\/sre.google\/workbook\/alerting-on-slos\/\" target=\"_blank\" rel=\"noopener\">SLO tabanl\u0131 alarm rehberinde<\/a> anlat\u0131l\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sonu\u00e7, kullan\u0131c\u0131lar\u0131 ger\u00e7ekten etkileyen problemlerde h\u0131zl\u0131, zarars\u0131z dalgalanmalarda sessiz bir alarm sistemi.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">K\u00fc\u00e7\u00fck bir ekip SLO&#8217;ya nereden ba\u015flamal\u0131?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">B\u00fct\u00fcn servisler i\u00e7in kapsaml\u0131 SLO&#8217;lar tan\u0131mlamaya \u00e7al\u0131\u015fmak, genellikle hi\u00e7 ba\u015flamamakla sonu\u00e7lan\u0131yor. Benim \u00f6nerdi\u011fim s\u0131ra \u015fu:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Kullan\u0131c\u0131lar i\u00e7in en kritik bir veya iki ak\u0131\u015f\u0131 se\u00e7. \u00d6rne\u011fin giri\u015f ve \u00f6deme.<\/li>\n\n\n<li>Her biri i\u00e7in bir eri\u015filebilirlik ve bir gecikme SLI&#8217;\u0131 tan\u0131mla.<\/li>\n\n\n<li>Son \u00fc\u00e7 ay\u0131n verisine bakarak ger\u00e7ek\u00e7i bir hedef koy.<\/li>\n\n\n<li>Bir dashboard ile SLO&#8217;yu ve kalan b\u00fct\u00e7eyi g\u00f6r\u00fcn\u00fcr yap.<\/li>\n\n\n<li>Burn rate tabanl\u0131 tek bir alarm kur.<\/li>\n\n\n<li>Bir ay sonra hedefi ve SLI tan\u0131m\u0131n\u0131 g\u00f6zden ge\u00e7ir.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">SLI&#8217;lar\u0131 \u00f6l\u00e7mek i\u00e7in ayr\u0131 bir altyap\u0131ya gerek yok. Prometheus&#8217;ta HTTP istek saya\u00e7lar\u0131 ve histogramlar\u0131 zaten varsa, SLO hesab\u0131 birka\u00e7 sorgudan ibaret. Bu metriklerin nas\u0131l topland\u0131\u011f\u0131n\u0131 <a href=\"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/04\/observability-logs-metrics-traces\/\">log, metric ve trace<\/a> yaz\u0131s\u0131nda anlatm\u0131\u015ft\u0131m.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">S\u0131k yap\u0131lan hatalar<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u00c7ok fazla SLO tan\u0131mlamak. Her servis i\u00e7in onlarca hedef, hi\u00e7birinin takip edilmemesiyle sonu\u00e7lan\u0131r.<\/li>\n\n\n<li>Kullan\u0131c\u0131y\u0131 yans\u0131tmayan SLI&#8217;lar se\u00e7mek. Veritaban\u0131 CPU&#8217;su veya pod say\u0131s\u0131 gibi.<\/li>\n\n\n<li>Hedefi bir kez koyup hi\u00e7 g\u00f6zden ge\u00e7irmemek.<\/li>\n\n\n<li>B\u00fct\u00e7e t\u00fckendi\u011finde hi\u00e7bir \u015feyin de\u011fi\u015fmemesi. Politika uygulanm\u0131yorsa SLO sadece bir rapordur.<\/li>\n\n\n<li>SLO&#8217;yu ekibi cezaland\u0131rmak i\u00e7in kullanmak. Ama\u00e7 su\u00e7lu bulmak de\u011fil, risk hakk\u0131nda ortak bir dil olu\u015fturmak.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Kavramlar\u0131n orijinal ve en kapsaml\u0131 anlat\u0131m\u0131 Google&#8217;\u0131n \u00fccretsiz yay\u0131nlad\u0131\u011f\u0131 <a href=\"https:\/\/sre.google\/sre-book\/service-level-objectives\/\" target=\"_blank\" rel=\"noopener\">Site Reliability Engineering kitab\u0131n\u0131n SLO b\u00f6l\u00fcm\u00fcnde<\/a> yer al\u0131yor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">G\u00fcvenilirlik her zaman daha fazlas\u0131 istenebilecek bir \u015fey. SLO&#8217;nun as\u0131l de\u011feri, &#8220;yeterince g\u00fcvenilir&#8221; seviyesini a\u00e7\u0131k\u00e7a tan\u0131mlayarak, ekibin geri kalan zaman\u0131n\u0131 kullan\u0131c\u0131lar i\u00e7in de\u011fer \u00fcreten i\u015flere ay\u0131rabilmesini sa\u011flamas\u0131nda.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>SLO, bir servisin ne kadar g\u00fcvenilir olmas\u0131 gerekti\u011fini say\u0131yla ifade eder. SLI se\u00e7imi, hedef belirleme, error budget hesab\u0131 ve h\u0131z ile g\u00fcvenilirlik dengesi.<\/p>\n","protected":false},"author":1,"featured_media":244,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-245","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-mimari"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/245","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=245"}],"version-history":[{"count":1,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/245\/revisions"}],"predecessor-version":[{"id":280,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/245\/revisions\/280"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/244"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=245"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=245"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=245"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}