{"id":43,"date":"2026-10-04T18:22:00","date_gmt":"2026-10-04T18:22:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/04\/observability-logs-metrics-traces\/"},"modified":"2026-10-04T18:22:00","modified_gmt":"2026-10-04T18:22:00","slug":"observability-logs-metrics-traces","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/04\/observability-logs-metrics-traces\/","title":{"rendered":"Log Basmak G\u00f6zlemlenebilirlik De\u011fildir"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Bir incident s\u0131ras\u0131nda ya\u015fanan tipik sahne:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir m\u00fc\u015fteri \u00f6deme ekran\u0131n\u0131n \u00e7ok yava\u015f oldu\u011funu s\u00f6yl\u00fcyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Log sistemini a\u00e7\u0131yorsunuz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Son bir saatte 4 milyon sat\u0131r log var.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Hangisinin o m\u00fc\u015fteriye ait oldu\u011funu bilmiyorsunuz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bulsan\u0131z bile iste\u011fin hangi servislerden ge\u00e7ti\u011fini ve zaman\u0131n nerede harcand\u0131\u011f\u0131n\u0131 g\u00f6rmek i\u00e7in be\u015f farkl\u0131 servisin loglar\u0131n\u0131 zaman damgas\u0131yla elle e\u015fle\u015ftirmeye \u00e7al\u0131\u015f\u0131yorsunuz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sistem log \u00fcretiyor. Ama g\u00f6zlemlenebilir de\u011fil.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u00dc\u00e7 sinyal, \u00fc\u00e7 farkl\u0131 soru<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Log, metric ve trace genellikle ayn\u0131 c\u00fcmlede an\u0131l\u0131r ama farkl\u0131 sorular\u0131 cevaplar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Metric:<\/strong> Bir \u015feyler ters gidiyor mu? Hata oran\u0131, latency y\u00fczdelikleri, kuyruk uzunlu\u011fu. Ucuzdur, uzun s\u00fcre saklanabilir, alarm kurmak i\u00e7in idealdir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Trace:<\/strong> Ters giden \u015fey nerede? Tek bir iste\u011fin servisler aras\u0131ndaki yolculu\u011funu ve her ad\u0131m\u0131n s\u00fcresini g\u00f6sterir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Log:<\/strong> Tam olarak ne oldu? Belirli bir an\u0131n detay\u0131n\u0131, hata mesaj\u0131n\u0131, i\u015f ba\u011flam\u0131n\u0131 anlat\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sa\u011fl\u0131kl\u0131 bir inceleme genellikle bu s\u0131rayla ilerler. Metric problemi g\u00f6sterir, trace yerini daralt\u0131r, log nedenini a\u00e7\u0131klar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sadece log ile ba\u015flamak samanl\u0131kta i\u011fne aramakt\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Correlation ID her \u015feyi ba\u011flar<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bu \u00fc\u00e7 sinyali birbirine ba\u011flayan \u015fey ortak bir kimliktir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">W3C Trace Context standard\u0131 bunun i\u00e7in <code>traceparent<\/code> header&#8217;\u0131n\u0131 tan\u0131ml\u0131yor:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>traceparent: 00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Gateway&#8217;e gelen her istek bir trace ID al\u0131r. Bu ID her servis \u00e7a\u011fr\u0131s\u0131nda, her mesaj kuyru\u011fu event&#8217;inde ta\u015f\u0131n\u0131r. Loglara da yaz\u0131l\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130ncident an\u0131nda yava\u015f bir trace buldu\u011funuzda, ayn\u0131 trace ID ile o iste\u011fe ait b\u00fct\u00fcn loglar\u0131 tek sorguda g\u00f6rebilirsiniz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Asenkron ak\u0131\u015flarda bu ba\u011flam en kolay kaybolan \u015feydir. Kafka veya RabbitMQ mesajlar\u0131n\u0131n header&#8217;\u0131na trace context eklenmezse, trace kuyru\u011fun \u00f6n\u00fcnde biter.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Structured logging<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u015eu log sat\u0131r\u0131 insan i\u00e7in okunabilir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Payment failed for order 1842 after 3 retries<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Ama makine i\u00e7in okunamaz. &#8220;Son bir saatte 3 retry sonras\u0131 ba\u015far\u0131s\u0131z olan \u00f6demeler&#8221; gibi bir sorgu yazmak zordur.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ayn\u0131 bilgi structured olarak \u015f\u00f6yle yaz\u0131labilir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>{\n  \"level\": \"warn\",\n  \"event\": \"payment_failed\",\n  \"orderId\": 1842,\n  \"retries\": 3,\n  \"provider\": \"bank-x\",\n  \"traceId\": \"4bf92f35...\"\n}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Mesaj k\u0131sa ve sabittir. De\u011fi\u015fken bilgiler alanlarda durur. Filtreleme, gruplama ve dashboard olu\u015fturma art\u0131k m\u00fcmk\u00fcnd\u00fcr.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ne kadar log?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Daha fazla log daha fazla g\u00f6r\u00fcn\u00fcrl\u00fck demek de\u011fildir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Her metot giri\u015finde ve \u00e7\u0131k\u0131\u015f\u0131nda log basan bir sistemde \u00f6nemli sat\u0131rlar g\u00fcr\u00fclt\u00fc i\u00e7inde kaybolur. \u00dcstelik log saklama maliyeti bir noktadan sonra altyap\u0131 faturas\u0131n\u0131n ciddi bir kalemi haline gelir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kendime sordu\u011fum soru \u015fu: bu log sat\u0131r\u0131n\u0131 bir incident s\u0131ras\u0131nda okursam karar vermeme yard\u0131m eder mi?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Etmiyorsa ya silinmeli ya da debug seviyesine indirilmeli.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kardinalite tuza\u011f\u0131<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Metric taraf\u0131nda en s\u0131k yap\u0131lan hata, label olarak y\u00fcksek kardinaliteli de\u011ferler kullanmakt\u0131r:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>http_requests_total{userId=\"42\"}<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Her kullan\u0131c\u0131 i\u00e7in ayr\u0131 bir time series olu\u015fur. Bir milyon kullan\u0131c\u0131, bir milyon seri demektir. Prometheus gibi sistemler bu y\u00fck\u00fc ta\u015f\u0131yamaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">User ID, order ID gibi de\u011ferler trace ve log&#8217;a aittir. Metric&#8217;lerde endpoint, status code ve servis ad\u0131 gibi s\u0131n\u0131rl\u0131 de\u011ferler kullan\u0131lmal\u0131d\u0131r.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">OpenTelemetry<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Bug\u00fcn bu \u00fc\u00e7 sinyali tek bir standart alt\u0131nda toplamak i\u00e7in en yayg\u0131n tercih OpenTelemetry. Instrumentation kodunu belirli bir vendor&#8217;a ba\u011flamadan yazman\u0131z\u0131 sa\u011fl\u0131yor. Backend olarak Jaeger, Tempo, Datadog veya ba\u015fka bir \u015fey se\u00e7mek sonradan verilebilecek bir karar haline geliyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Java taraf\u0131nda agent ile ba\u015flamak \u00e7o\u011fu framework i\u00e7in otomatik instrumentation sa\u011fl\u0131yor. Sonra i\u015f a\u00e7\u0131s\u0131ndan \u00f6nemli noktalara manuel span eklemek yeterli oluyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">G\u00f6zlemlenebilirlik production&#8217;a \u00e7\u0131kt\u0131ktan sonra eklenen bir \u00f6zellik de\u011fil.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Sistemi tasarlarken sorulmas\u0131 gereken bir soru:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Bu sistem bozuldu\u011funda, nedenini kodu a\u00e7madan anlayabilecek miyim?<\/strong><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Gigabaytlarca log var ama &#8220;bu istek neden yava\u015ft\u0131?&#8221; sorusuna cevap yok. Log, metric ve trace&#8217;i ne zaman, nas\u0131l birlikte kullanmal\u0131; correlation ID neden kritik?<\/p>\n","protected":false},"author":1,"featured_media":42,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-43","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\/43","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=43"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/43\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/42"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=43"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=43"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=43"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}