{"id":3532,"date":"2025-12-27T20:18:11","date_gmt":"2025-12-27T17:18:11","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/e-ticaret-siteleri-icin-log-analizi-donusum-kaybi-4xx-5xx-ve-odeme-hatalarini-yakalamak\/"},"modified":"2026-09-21T18:06:48","modified_gmt":"2026-09-21T15:06:48","slug":"e-ticaret-siteleri-icin-log-analizi-donusum-kaybi-4xx-5xx-ve-odeme","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/e-ticaret-siteleri-icin-log-analizi-donusum-kaybi-4xx-5xx-ve-odeme\/","title":{"rendered":"E\u2011Ticaret Siteleri \u0130\u00e7in Log Analizi: D\u00f6n\u00fc\u015f\u00fcm Kayb\u0131, 4xx\/5xx ve \u00d6deme Hatalar\u0131n\u0131 Yakalamak"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" role=\"navigation\" aria-label=\"Table of Contents\" data-nosnippet class=\"toc_transparent no_bullets toc_numbered toc_title_center\"><p class=\"toc_title\">\u0130\u00e7indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Eticarette_Log_Analizi_Neden_Bu_Kadar_Onemli\"><span class=\"toc_number toc_depth_1\">1.<\/span> E\u2011ticarette Log Analizi Neden Bu Kadar \u00d6nemli?<\/a><\/li><li><a href=\"#Donusum_Kaybini_Anlamak_Icin_Hangi_Loglara_Bakmalisiniz\"><span class=\"toc_number toc_depth_1\">2.<\/span> D\u00f6n\u00fc\u015f\u00fcm Kayb\u0131n\u0131 Anlamak \u0130\u00e7in Hangi Loglara Bakmal\u0131s\u0131n\u0131z?<\/a><ul><li><a href=\"#1_Web_sunucu_erisim_loglari_accesslog\"><span class=\"toc_number toc_depth_2\">2.1.<\/span> 1. Web sunucu eri\u015fim loglar\u0131 (access.log)<\/a><\/li><li><a href=\"#2_Web_sunucu_hata_loglari_errorlog\"><span class=\"toc_number toc_depth_2\">2.2.<\/span> 2. Web sunucu hata loglar\u0131 (error.log)<\/a><\/li><li><a href=\"#3_Uygulama_ve_framework_loglari\"><span class=\"toc_number toc_depth_2\">2.3.<\/span> 3. Uygulama ve framework loglar\u0131<\/a><\/li><li><a href=\"#4_Odeme_saglayici_ve_banka_loglari\"><span class=\"toc_number toc_depth_2\">2.4.<\/span> 4. \u00d6deme sa\u011flay\u0131c\u0131 ve banka loglar\u0131<\/a><\/li><li><a href=\"#5_Veritabani_ve_kuyruk_loglari\"><span class=\"toc_number toc_depth_2\">2.5.<\/span> 5. Veritaban\u0131 ve kuyruk loglar\u0131<\/a><\/li><li><a href=\"#6_Log_saklama_sureleri_ve_disk_yonetimi\"><span class=\"toc_number toc_depth_2\">2.6.<\/span> 6. Log saklama s\u00fcreleri ve disk y\u00f6netimi<\/a><\/li><\/ul><\/li><li><a href=\"#4xx_ve_5xx_Hatalarindan_Donusum_Kaybi_Nasil_Yakalanir\"><span class=\"toc_number toc_depth_1\">3.<\/span> 4xx ve 5xx Hatalar\u0131ndan D\u00f6n\u00fc\u015f\u00fcm Kayb\u0131 Nas\u0131l Yakalan\u0131r?<\/a><ul><li><a href=\"#4xx_hatalari_Kullanici_veya_istemci_kaynakli_gorunen_sorunlar\"><span class=\"toc_number toc_depth_2\">3.1.<\/span> 4xx hatalar\u0131: Kullan\u0131c\u0131 veya istemci kaynakl\u0131 g\u00f6r\u00fcnen sorunlar<\/a><\/li><li><a href=\"#5xx_hatalari_Sunucu_tarafli_gercek_problemler\"><span class=\"toc_number toc_depth_2\">3.2.<\/span> 5xx hatalar\u0131: Sunucu tarafl\u0131 ger\u00e7ek problemler<\/a><\/li><li><a href=\"#Basit_komutlarla_4xx5xx_istatistikleri_cikarmak\"><span class=\"toc_number toc_depth_2\">3.3.<\/span> Basit komutlarla 4xx\/5xx istatistikleri \u00e7\u0131karmak<\/a><\/li><li><a href=\"#Kritik_funnel_sayfalarina_ayri_gozle_bakmak\"><span class=\"toc_number toc_depth_2\">3.4.<\/span> Kritik funnel sayfalar\u0131na ayr\u0131 g\u00f6zle bakmak<\/a><\/li><\/ul><\/li><li><a href=\"#Sepet_ve_Odeme_Adimlarinda_Log_Tabanli_Funnel_Analizi\"><span class=\"toc_number toc_depth_1\">4.<\/span> Sepet ve \u00d6deme Ad\u0131mlar\u0131nda Log Tabanl\u0131 Funnel Analizi<\/a><ul><li><a href=\"#URL_desenleriyle_adimlari_tanimlamak\"><span class=\"toc_number toc_depth_2\">4.1.<\/span> URL desenleriyle ad\u0131mlar\u0131 tan\u0131mlamak<\/a><\/li><li><a href=\"#Uygulama_loglarina_olay_bazli_kayit_eklemek\"><span class=\"toc_number toc_depth_2\">4.2.<\/span> Uygulama loglar\u0131na olay bazl\u0131 kay\u0131t eklemek<\/a><\/li><li><a href=\"#Oturum_bazli_funnel_ve_korelasyon\"><span class=\"toc_number toc_depth_2\">4.3.<\/span> Oturum bazl\u0131 funnel ve korelasyon<\/a><\/li><\/ul><\/li><li><a href=\"#Odeme_Hatalarini_Sunucu_Loglarindan_Yakalamak\"><span class=\"toc_number toc_depth_1\">5.<\/span> \u00d6deme Hatalar\u0131n\u0131 Sunucu Loglar\u0131ndan Yakalamak<\/a><ul><li><a href=\"#Odeme_saglayici_hata_kodlarini_normallestirmek\"><span class=\"toc_number toc_depth_2\">5.1.<\/span> \u00d6deme sa\u011flay\u0131c\u0131 hata kodlar\u0131n\u0131 normalle\u015ftirmek<\/a><\/li><li><a href=\"#Timeout_ve_performans_kaynakli_odeme_problemleri\"><span class=\"toc_number toc_depth_2\">5.2.<\/span> Timeout ve performans kaynakl\u0131 \u00f6deme problemleri<\/a><\/li><li><a href=\"#Callback_ve_webhook_sorunlarini_loglardan_yakalamak\"><span class=\"toc_number toc_depth_2\">5.3.<\/span> Callback ve webhook sorunlar\u0131n\u0131 loglardan yakalamak<\/a><\/li><\/ul><\/li><li><a href=\"#Alarm_Rapor_ve_Otomasyon_Log_Analizini_Gunluk_Rutine_Cevirmek\"><span class=\"toc_number toc_depth_1\">6.<\/span> Alarm, Rapor ve Otomasyon: Log Analizini G\u00fcnl\u00fck Rutine \u00c7evirmek<\/a><ul><li><a href=\"#Anlik_alarm_kurallari\"><span class=\"toc_number toc_depth_2\">6.1.<\/span> Anl\u0131k alarm kurallar\u0131<\/a><\/li><li><a href=\"#Gosterge_panelleri_dashboard_ile_buyuk_resmi_gormek\"><span class=\"toc_number toc_depth_2\">6.2.<\/span> G\u00f6sterge panelleri (dashboard) ile b\u00fcy\u00fck resmi g\u00f6rmek<\/a><\/li><li><a href=\"#Crontab_ile_duzenli_raporlar_uretmek\"><span class=\"toc_number toc_depth_2\">6.3.<\/span> Crontab ile d\u00fczenli raporlar \u00fcretmek<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Altyapisinda_Log_Analizi_Icin_Pratik_Oneriler\"><span class=\"toc_number toc_depth_1\">7.<\/span> DCHost Altyap\u0131s\u0131nda Log Analizi \u0130\u00e7in Pratik \u00d6neriler<\/a><\/li><li><a href=\"#Sonuc_ve_Yol_Haritasi_Loglari_Okuyan_ETicaret_Kazanir\"><span class=\"toc_number toc_depth_1\">8.<\/span> Sonu\u00e7 ve Yol Haritas\u0131: Loglar\u0131 Okuyan E\u2011Ticaret Kazan\u0131r<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Eticarette_Log_Analizi_Neden_Bu_Kadar_Onemli\">E\u2011ticarette Log Analizi Neden Bu Kadar \u00d6nemli?<\/span><\/h2>\n<p>E\u2011ticaret taraf\u0131nda b\u00fcy\u00fcme konu\u015fulan her toplant\u0131da mutlaka iki kelime ge\u00e7er: <strong>d\u00f6n\u00fc\u015f\u00fcm oran\u0131<\/strong> ve <strong>kaybolan sepetler<\/strong>. Trafik sat\u0131n al\u0131r, kampanyalar kurgular, tasar\u0131m\u0131 iyile\u015ftirirsiniz; fakat baz\u0131 kullan\u0131c\u0131lar tam \u00f6deme ad\u0131m\u0131nda sessizce kaybolur. Analytics ara\u00e7lar\u0131 size belli bir seviyeye kadar yol g\u00f6sterir, ancak teknik sorunlar ba\u015flad\u0131\u011f\u0131nda ger\u00e7ekten ne oldu\u011funu s\u00f6yleyen tek yer <strong>sunucu loglar\u0131<\/strong>d\u0131r.<\/p>\n<p>Sunucunun g\u00f6z\u00fcnden bak\u0131nca her \u015fey \u00e7ok nettir: hangi URL ka\u00e7 milisaniyede yan\u0131t verdi, hangi istekte 4xx\/5xx d\u00f6nd\u00fc, hangi kullan\u0131c\u0131 \u00f6deme callback \u00e7a\u011fr\u0131s\u0131nda 500 hatas\u0131 ald\u0131, hangi \u00f6deme iste\u011fi gateway&#8217;e hi\u00e7 ula\u015famad\u0131\u2026 D\u00f6n\u00fc\u015f\u00fcm kayb\u0131n\u0131n \u00f6nemli bir k\u0131sm\u0131 asl\u0131nda bu loglarda sakl\u0131d\u0131r. Sorun \u015fu ki, bir\u00e7ok e\u2011ticaret ekibi bu alt\u0131n madeniyle sistematik olarak \u00e7al\u0131\u015fm\u0131yor.<\/p>\n<p>Bu yaz\u0131da DCHost ekibi olarak, e\u2011ticaret sitelerinde <strong>sunucu loglar\u0131ndan d\u00f6n\u00fc\u015f\u00fcm kayb\u0131n\u0131, 4xx\/5xx ve \u00f6deme hatalar\u0131n\u0131 nas\u0131l yakalayabilece\u011finizi<\/strong> ad\u0131m ad\u0131m anlataca\u011f\u0131z. Apache\/Nginx eri\u015fim loglar\u0131ndan, uygulama ve \u00f6deme loglar\u0131na; basit komutlarla h\u0131zl\u0131 analizden merkezi loglama ve alarm kurallar\u0131na kadar pratik, sahada defalarca denenmi\u015f bir yol haritas\u0131 payla\u015faca\u011f\u0131z.<\/p>\n<h2><span id=\"Donusum_Kaybini_Anlamak_Icin_Hangi_Loglara_Bakmalisiniz\">D\u00f6n\u00fc\u015f\u00fcm Kayb\u0131n\u0131 Anlamak \u0130\u00e7in Hangi Loglara Bakmal\u0131s\u0131n\u0131z?<\/span><\/h2>\n<p>\u00d6nce resme yukar\u0131dan bakal\u0131m: E\u2011ticaret sitenizde kullan\u0131c\u0131 yolculu\u011fu kabaca \u015f\u00f6yle i\u015fler:<\/p>\n<ul>\n<li>\u00dcr\u00fcn listeleme ve detay sayfalar\u0131<\/li>\n<li>Sepete ekleme<\/li>\n<li>Sepet g\u00f6r\u00fcnt\u00fcleme<\/li>\n<li>\u00d6deme\/checkout ad\u0131mlar\u0131<\/li>\n<li>\u00d6deme sonucu (ba\u015far\u0131l\u0131\/ba\u015far\u0131s\u0131z)<\/li>\n<\/ul>\n<p>Bu yolculu\u011fun her ad\u0131m\u0131nda farkl\u0131 loglar devreye girer. D\u00f6n\u00fc\u015f\u00fcm kayb\u0131n\u0131n k\u00f6k nedenini bulmak i\u00e7in bu loglar\u0131 birlikte okumak gerekir.<\/p>\n<h3><span id=\"1_Web_sunucu_erisim_loglari_accesslog\">1. Web sunucu eri\u015fim loglar\u0131 (access.log)<\/span><\/h3>\n<p>Apache veya Nginx eri\u015fim loglar\u0131, her HTTP iste\u011fini sat\u0131r sat\u0131r kaydeder. Tipik bir sat\u0131rda \u015funlar bulunur:<\/p>\n<ul>\n<li>IP adresi<\/li>\n<li>Tarih ve saat<\/li>\n<li>HTTP metodu (GET\/POST vb.)<\/li>\n<li>\u0130stenen URL ve query string<\/li>\n<li>HTTP durum kodu (200, 301, 404, 500 vb.)<\/li>\n<li>Cevap boyutu<\/li>\n<li>Referer (hangi sayfadan gelmi\u015f)<\/li>\n<li>Kullan\u0131c\u0131 ajan\u0131 (taray\u0131c\u0131 bilgisi)<\/li>\n<\/ul>\n<p>Bu loglar sayesinde:<\/p>\n<ul>\n<li>Sepet ve \u00f6deme URL&#8217;lerinde ka\u00e7 istek yap\u0131ld\u0131\u011f\u0131n\u0131,<\/li>\n<li>Bu URL&#8217;lerin ne kadar\u0131n\u0131n 4xx\/5xx ile sonu\u00e7land\u0131\u011f\u0131n\u0131,<\/li>\n<li>Hangi saatlerde hata oran\u0131n\u0131n y\u00fckseldi\u011fini<\/li>\n<\/ul>\n<p>h\u0131zl\u0131ca g\u00f6rebilirsiniz. Apache\/Nginx formatlar\u0131n\u0131 ve 4xx\/5xx okumay\u0131 daha temelden \u00f6\u011frenmek istiyorsan\u0131z, ayr\u0131nt\u0131l\u0131 bir ba\u015flang\u0131\u00e7 i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/hosting-sunucu-loglarini-okumayi-ogrenin-apache-ve-nginx-ile-4xx-5xx\/\">Apache ve Nginx ile 4xx\u20135xx hatalar\u0131n\u0131 te\u015fhis rehberi<\/a> yaz\u0131m\u0131za da mutlaka g\u00f6z at\u0131n.<\/p>\n<h3><span id=\"2_Web_sunucu_hata_loglari_errorlog\">2. Web sunucu hata loglar\u0131 (error.log)<\/span><\/h3>\n<p>Eri\u015fim loglar\u0131 bize \u201cne oldu\u201dyu s\u00f6yler; hata loglar\u0131 ise \u00e7o\u011fu zaman \u201cneden oldu\u201dyu g\u00f6sterir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>PHP fatal error nedeniyle patlayan \u00f6deme sayfas\u0131<\/li>\n<li>3. parti \u00f6deme API&#8217;sine ba\u011flanamayan cURL \u00e7a\u011fr\u0131lar\u0131<\/li>\n<li>Veritaban\u0131 ba\u011flant\u0131 hatalar\u0131 (too many connections, timeout vb.)<\/li>\n<\/ul>\n<p>\u00d6deme ad\u0131m\u0131nda kullan\u0131c\u0131 500 hatas\u0131 g\u00f6r\u00fcyorsa, genellikle detayl\u0131 neden <strong>error.log<\/strong> dosyas\u0131nda kay\u0131tl\u0131d\u0131r. Bu y\u00fczden d\u00f6n\u00fc\u015f\u00fcm kayb\u0131 analizi yaparken access.log ile error.log&#8217;u mutlaka birlikte incelemek gerekir.<\/p>\n<h3><span id=\"3_Uygulama_ve_framework_loglari\">3. Uygulama ve framework loglar\u0131<\/span><\/h3>\n<p>E\u011fer WooCommerce, Laravel, Symfony, custom PHP veya Node.js tabanl\u0131 bir e\u2011ticaret uygulaman\u0131z varsa, uygulama seviyesi loglar i\u015fin r\u00f6ntgeni gibidir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>&#8220;cart_add&#8221;, &#8220;checkout_started&#8221;, &#8220;payment_initiated&#8221;, &#8220;payment_success&#8221;, &#8220;payment_failed&#8221; gibi olay loglar\u0131<\/li>\n<li>Hata detaylar\u0131 (exception mesajlar\u0131, stack trace)<\/li>\n<li>Kullan\u0131c\u0131 veya sepet ID&#8217;si, sipari\u015f numaras\u0131 gibi korelasyon alanlar\u0131<\/li>\n<\/ul>\n<p>Bu loglar\u0131 yap\u0131land\u0131r\u0131lm\u0131\u015f (JSON gibi) formatta tutarsan\u0131z, daha sonra merkezi bir log sistemi ile (ELK, Loki vb.) \u00e7ok g\u00fc\u00e7l\u00fc sorgular ve paneller kurabilirsiniz. Bu konuyu daha ileri ta\u015f\u0131mak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/vps-log-yonetimi-nasil-rayina-oturur-grafana-loki-promtail-ile-merkezi\/\">Grafana Loki + Promtail ile merkezi loglama rehberimizi<\/a> \u00f6zellikle tavsiye ederim.<\/p>\n<h3><span id=\"4_Odeme_saglayici_ve_banka_loglari\">4. \u00d6deme sa\u011flay\u0131c\u0131 ve banka loglar\u0131<\/span><\/h3>\n<p>\u00d6deme s\u00fcrecinde genellikle \u015fu ad\u0131mlar vard\u0131r:<\/p>\n<ul>\n<li>\u00d6deme iste\u011fi: Sitenizden banka\/\u00f6deme kurulu\u015funa istek g\u00f6nderilir.<\/li>\n<li>3D Secure veya kart do\u011frulama ekran\u0131 (kullan\u0131c\u0131 bankan\u0131n sayfas\u0131na gider).<\/li>\n<li>Callback\/Webhook: Banka, son sonucu sizin siteye bildirir.<\/li>\n<\/ul>\n<p>Burada iki t\u00fcr log kritik:<\/p>\n<ul>\n<li><strong>Sizin uygulaman\u0131zdaki \u00f6deme loglar\u0131:<\/strong> \u00f6deme iste\u011fi, d\u00f6nen hata kodlar\u0131, sipari\u015f ID&#8217;leri.<\/li>\n<li><strong>\u00d6deme sa\u011flay\u0131c\u0131n\u0131n loglar\u0131:<\/strong> genelde dashboard \u00fczerinden raporlar veya .csv export olarak al\u0131rs\u0131n\u0131z.<\/li>\n<\/ul>\n<p>Sunucu loglar\u0131n\u0131 bu \u00f6deme raporlar\u0131 ile birle\u015ftirdi\u011finizde, hangi teknik sorunlar\u0131n reddedilen veya yar\u0131m kalan \u00f6demelere neden oldu\u011funu daha net g\u00f6r\u00fcrs\u00fcn\u00fcz.<\/p>\n<h3><span id=\"5_Veritabani_ve_kuyruk_loglari\">5. Veritaban\u0131 ve kuyruk loglar\u0131<\/span><\/h3>\n<p>Orta ve b\u00fcy\u00fck \u00f6l\u00e7ekli e\u2011ticaret sitelerinde s\u0131k\u00e7a g\u00f6rd\u00fc\u011f\u00fcm\u00fcz bir model var: sipari\u015f olu\u015fturma ve e\u2011posta\/entegrasyon i\u015fleri, kuyruk (queue) sistemleriyle asenkron \u00e7al\u0131\u015f\u0131yor. Bu durumda:<\/p>\n<ul>\n<li>Veritaban\u0131 hata loglar\u0131 ve slow query loglar\u0131<\/li>\n<li>Queue worker loglar\u0131 (\u00f6rne\u011fin Laravel Queue, Horizon vb.)<\/li>\n<\/ul>\n<p>\u00f6zellikle kampanya d\u00f6nemlerinde kritik hale gelir. Veritaban\u0131 yava\u015flad\u0131\u011f\u0131nda ya da queue t\u00fcketemez hale geldi\u011finde, \u00f6deme alman\u0131z m\u00fcmk\u00fcn olsa bile sipari\u015finiz &#8220;beklemede&#8221; kalabilir. Bu da kullan\u0131c\u0131 taraf\u0131nda g\u00fcven kayb\u0131 ve destek y\u00fck\u00fc demektir.<\/p>\n<h3><span id=\"6_Log_saklama_sureleri_ve_disk_yonetimi\">6. Log saklama s\u00fcreleri ve disk y\u00f6netimi<\/span><\/h3>\n<p>Log analizi konu\u015furken g\u00f6zden ka\u00e7an ama \u00fcretimde en \u00e7ok sorun \u00e7\u0131karan ba\u015fl\u0131k: disk dolmas\u0131. Loglar\u0131 uzun s\u00fcre saklamak istersiniz, ancak bu defa da disk doldu\u011fu i\u00e7in site hata vermeye ba\u015flar. Bu dengeyi do\u011fru kurabilmek i\u00e7in:<\/p>\n<ul>\n<li><strong>logrotate<\/strong> ile g\u00fcnl\u00fck\/haftal\u0131k d\u00f6nd\u00fcrme ve s\u0131k\u0131\u015ft\u0131rma<\/li>\n<li>\u0130\u015fletme olarak ihtiya\u00e7 duydu\u011funuz log saklama s\u00fcrelerini (\u00f6rne\u011fin 90 g\u00fcn, 6 ay) belirleme<\/li>\n<li>Gerekirse eski loglar\u0131 daha ucuz bir depolama alan\u0131na ta\u015f\u0131ma<\/li>\n<\/ul>\n<p>gibi \u00f6nlemleri mutlaka planlamal\u0131s\u0131n\u0131z. Bu konuda pratik ad\u0131mlar\u0131 g\u00f6rmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/vps-disk-kullanimi-ve-logrotate-ayarlariyla-no-space-left-on-device-hatasini-onlemek\/\">logrotate ile disk dolma hatas\u0131n\u0131 \u00f6nleme rehberimize<\/a> bakabilirsiniz. Ayr\u0131ca <a href=\"https:\/\/www.dchost.com\/blog\/hosting-ve-e-posta-altyapisinda-log-saklama-sureleri\/\">hosting ve e\u2011posta altyap\u0131s\u0131nda log saklama s\u00fcreleri<\/a> yaz\u0131m\u0131z, hangi logu ne kadar tutman\u0131z gerekti\u011fi konusunda iyi bir \u00e7er\u00e7eve sunuyor.<\/p>\n<h2><span id=\"4xx_ve_5xx_Hatalarindan_Donusum_Kaybi_Nasil_Yakalanir\">4xx ve 5xx Hatalar\u0131ndan D\u00f6n\u00fc\u015f\u00fcm Kayb\u0131 Nas\u0131l Yakalan\u0131r?<\/span><\/h2>\n<p>HTTP durum kodlar\u0131, log analizinde ilk bakman\u0131z gereken yer. D\u00f6n\u00fc\u015f\u00fcm kay\u0131plar\u0131n\u0131n \u00f6nemli bir b\u00f6l\u00fcm\u00fc kullan\u0131c\u0131ya yans\u0131mayan ama loglara d\u00fc\u015fen bu kodlar\u0131n arkas\u0131na saklan\u0131r.<\/p>\n<h3><span id=\"4xx_hatalari_Kullanici_veya_istemci_kaynakli_gorunen_sorunlar\">4xx hatalar\u0131: Kullan\u0131c\u0131 veya istemci kaynakl\u0131 g\u00f6r\u00fcnen sorunlar<\/span><\/h3>\n<p>En s\u0131k g\u00f6rece\u011finiz 4xx kodlar\u0131:<\/p>\n<ul>\n<li><strong>404 Not Found:<\/strong> Kaynak bulunamad\u0131. S\u0131k rastlan\u0131yorsa yanl\u0131\u015f linkler, bozuk butonlar veya eksik y\u00f6nlendirmeler olabilir.<\/li>\n<li><strong>403 Forbidden:<\/strong> Yetkisiz eri\u015fim. Do\u011fru kullan\u0131c\u0131lar yanl\u0131\u015fl\u0131kla engelleniyorsa g\u00fcvenlik kurallar\u0131 (WAF, firewall) agresif olabilir.<\/li>\n<li><strong>429 Too Many Requests:<\/strong> Rate limiting devrede. Kampanya d\u00f6nemlerinde \u00f6deme veya sepet ad\u0131mlar\u0131nda 429 art\u0131\u015f\u0131 g\u00f6r\u00fcyorsan\u0131z, limitleri g\u00f6zden ge\u00e7irmek gerekir.<\/li>\n<\/ul>\n<p>\u00d6zellikle sepet ve \u00f6deme URL&#8217;lerinde 4xx oran\u0131n\u0131n artmas\u0131, direkt d\u00f6n\u00fc\u015f\u00fcm kayb\u0131 demektir. \u00d6rne\u011fin \/sepet, \/checkout, \/odeme gibi URL&#8217;ler i\u00e7in 404 ve 403&#8217;leri g\u00fcnl\u00fck olarak takip etmenizi \u00f6neririz.<\/p>\n<h3><span id=\"5xx_hatalari_Sunucu_tarafli_gercek_problemler\">5xx hatalar\u0131: Sunucu tarafl\u0131 ger\u00e7ek problemler<\/span><\/h3>\n<p>5xx kodlar\u0131 do\u011frudan sizin altyap\u0131n\u0131zla ilgilidir:<\/p>\n<ul>\n<li><strong>500 Internal Server Error:<\/strong> Genelde uygulama hatalar\u0131 (PHP exception, kod bug&#8217;\u0131).<\/li>\n<li><strong>502 Bad Gateway:<\/strong> PHP-FPM, Node.js veya upstream servis yan\u0131t veremedi\/yanl\u0131\u015f yan\u0131tlad\u0131.<\/li>\n<li><strong>503 Service Unavailable:<\/strong> Servis ge\u00e7ici olarak kullan\u0131lam\u0131yor; bak\u0131m, limit a\u015f\u0131m\u0131 veya a\u015f\u0131r\u0131 y\u00fck alt\u0131nda.<\/li>\n<li><strong>504 Gateway Timeout:<\/strong> Arkadaki servis belirlenen s\u00fcrede yan\u0131t veremedi (genelde yava\u015f DB veya API).<\/li>\n<\/ul>\n<p>Bu kodlar\u0131 <strong>zaman<\/strong>, <strong>URL<\/strong> ve <strong>kullan\u0131c\u0131 ak\u0131\u015f\u0131<\/strong> ile birlikte analiz etti\u011finizde, d\u00f6n\u00fc\u015f\u00fcm kay\u0131plar\u0131n\u0131 nokta at\u0131\u015f\u0131 yakalayabilirsiniz.<\/p>\n<h3><span id=\"Basit_komutlarla_4xx5xx_istatistikleri_cikarmak\">Basit komutlarla 4xx\/5xx istatistikleri \u00e7\u0131karmak<\/span><\/h3>\n<p>K\u00fc\u00e7\u00fck ve orta \u00f6l\u00e7ekli sitelerde, SSH eri\u015fiminiz varsa basit komutlarla bile h\u0131zla i\u00e7g\u00f6r\u00fc elde edebilirsiniz. \u00d6rne\u011fin Nginx access.log i\u00e7in:<\/p>\n<ul>\n<li>En \u00e7ok g\u00f6r\u00fclen 5xx hatalar\u0131:<br \/> <code>grep \" 5\" access.log | awk '{print $9}' | sort | uniq -c | sort -nr | head<\/code><\/li>\n<li>En \u00e7ok 404 d\u00f6nen ilk 10 URL:<br \/> <code>awk '$9 == 404 {print $7}' access.log | sort | uniq -c | sort -nr | head<\/code><\/li>\n<li>Sepet sayfas\u0131nda son bir saatte olu\u015fan 5xx say\u0131s\u0131:<br \/> <code>grep \"\/sepet\" access.log | grep \" 5\" | tail -n 2000 | wc -l<\/code><\/li>\n<\/ul>\n<p>Bu temel analiz bile, tasar\u0131mda g\u00f6r\u00fcnmeyen k\u0131r\u0131k linkleri, yanl\u0131\u015f y\u00f6nlendirmeleri ve \u00f6deme ad\u0131m\u0131ndaki ani hata art\u0131\u015flar\u0131n\u0131 ortaya \u00e7\u0131karabilir.<\/p>\n<h3><span id=\"Kritik_funnel_sayfalarina_ayri_gozle_bakmak\">Kritik funnel sayfalar\u0131na ayr\u0131 g\u00f6zle bakmak<\/span><\/h3>\n<p>T\u00fcm sitenin hata oran\u0131na de\u011fil, <strong>sat\u0131\u015f hunisinin kritik ad\u0131mlar\u0131na<\/strong> odaklanmal\u0131s\u0131n\u0131z. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>\u00dcr\u00fcn detay sayfalar\u0131: \/urun\/, \/product\/ vb.<\/li>\n<li>Sepet: \/sepet, \/cart<\/li>\n<li>Checkout: \/odeme, \/checkout, \/payment<\/li>\n<li>Sonu\u00e7 sayfas\u0131: \/siparis-tamam, \/order-success vb.<\/li>\n<\/ul>\n<p>Her bir ad\u0131m i\u00e7in ayr\u0131 ayr\u0131:<\/p>\n<ul>\n<li>Toplam istek say\u0131s\u0131<\/li>\n<li>4xx oran\u0131<\/li>\n<li>5xx oran\u0131<\/li>\n<\/ul>\n<p>\u00e7\u0131kard\u0131\u011f\u0131n\u0131zda, \u00f6rne\u011fin checkout sayfas\u0131n\u0131n genel siteye g\u00f6re 5 kat fazla 500 hatas\u0131 verdi\u011fini g\u00f6r\u00fcp do\u011frudan oraya odaklanabilirsiniz.<\/p>\n<h2><span id=\"Sepet_ve_Odeme_Adimlarinda_Log_Tabanli_Funnel_Analizi\">Sepet ve \u00d6deme Ad\u0131mlar\u0131nda Log Tabanl\u0131 Funnel Analizi<\/span><\/h2>\n<p>Log analizi sadece hatalar\u0131 saymak de\u011fildir; ayn\u0131 zamanda <strong>kullan\u0131c\u0131 yolculu\u011funu a\u015fama a\u015fama takip etmektir<\/strong>. Bunu e\u2011ticaret \u00f6zelinde basit bir funnel kurgusuyla yapabilirsiniz.<\/p>\n<h3><span id=\"URL_desenleriyle_adimlari_tanimlamak\">URL desenleriyle ad\u0131mlar\u0131 tan\u0131mlamak<\/span><\/h3>\n<p>\u0130lk ad\u0131m, access.log i\u00e7inde sepet ve \u00f6deme s\u00fcrecine ait URL&#8217;leri netle\u015ftirmektir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Ad\u0131m 1 \u2013 Sepet g\u00f6r\u00fcnt\u00fcleme: \/sepet<\/li>\n<li>Ad\u0131m 2 \u2013 Adres\/fatura bilgileri: \/odeme\/adres<\/li>\n<li>Ad\u0131m 3 \u2013 \u00d6deme y\u00f6ntemi se\u00e7imi: \/odeme\/yontem<\/li>\n<li>Ad\u0131m 4 \u2013 \u00d6deme sonucu: \/odeme\/sonuc<\/li>\n<\/ul>\n<p>Ard\u0131ndan loglarda bu URL&#8217;leri filtreleyerek, belirli bir zaman aral\u0131\u011f\u0131nda:<\/p>\n<ul>\n<li>Ka\u00e7 benzersiz kullan\u0131c\u0131 (IP+user agent\/oturum) bu ad\u0131mlara girdi?<\/li>\n<li>Hangi ad\u0131mda ka\u00e7 ki\u015fi kayboldu?<\/li>\n<li>Hangi ad\u0131mda 4xx\/5xx oran\u0131 anormal y\u00fcksek?<\/li>\n<\/ul>\n<p>sorular\u0131na yan\u0131t arars\u0131n\u0131z. Daha detayl\u0131 \u00f6rnek funnel kurgular\u0131 ve alarm senaryolar\u0131 i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/e-ticaret-sepet-ve-odeme-adimlarini-izlemek-sunucu-loglari-ve-alarm-kurallari\/\">e\u2011ticaret sepet ve \u00f6deme ad\u0131mlar\u0131n\u0131 izleme rehberimizi<\/a> inceleyebilirsiniz.<\/p>\n<h3><span id=\"Uygulama_loglarina_olay_bazli_kayit_eklemek\">Uygulama loglar\u0131na olay bazl\u0131 kay\u0131t eklemek<\/span><\/h3>\n<p>Sadece URL ile \u00e7al\u0131\u015fmak bir yere kadar g\u00f6t\u00fcr\u00fcr. Daha derin analiz i\u00e7in, uygulama seviyesinde \u015fu tip olay loglar\u0131 \u00fcretmenizi tavsiye ediyoruz:<\/p>\n<ul>\n<li>cart_viewed, cart_updated, checkout_started<\/li>\n<li>payment_initiated, payment_redirected, payment_callback_received<\/li>\n<li>payment_success, payment_failed<\/li>\n<\/ul>\n<p>Bu olaylar\u0131 tek sat\u0131rl\u0131k JSON loglar\u0131 olarak yazarsan\u0131z, \u00f6rne\u011fin:<\/p>\n<pre>{\"event\":\"payment_failed\",\"order_id\":12345,\"reason\":\"3d_auth_failed\",\"user_id\":678}<\/pre>\n<p>sonradan merkezi log sisteminizde \u015fu tip sorgular yapabilirsiniz:<\/p>\n<ul>\n<li>Son 24 saatte payment_failed oran\u0131 nedir?<\/li>\n<li>Hangi bankalarda veya kart t\u00fcrlerinde hata oran\u0131 daha y\u00fcksek?<\/li>\n<li>Hangi saat aral\u0131\u011f\u0131nda teknik nedenli \u00f6deme hatalar\u0131 artm\u0131\u015f?<\/li>\n<\/ul>\n<h3><span id=\"Oturum_bazli_funnel_ve_korelasyon\">Oturum bazl\u0131 funnel ve korelasyon<\/span><\/h3>\n<p>\u0130\u015fin ideal hali, her kullan\u0131c\u0131ya veya sepete \u00f6zel bir korelasyon ID&#8217;si kullanmakt\u0131r (\u00f6rne\u011fin session_id, cart_id, order_id). Bu ID&#8217;yi:<\/p>\n<ul>\n<li>access.log&#8217;taki her iste\u011fe (\u00f6rne\u011fin cookie arac\u0131l\u0131\u011f\u0131yla),<\/li>\n<li>uygulama loglar\u0131na,<\/li>\n<li>\u00f6deme loglar\u0131na<\/li>\n<\/ul>\n<p>ekledi\u011finizde, tek bir kullan\u0131c\u0131n\u0131n sepetten \u00f6demeye kadar ya\u015fad\u0131klar\u0131n\u0131 u\u00e7tan uca takip edebilirsiniz. Bu sayede, belirli bir hata tipinin ger\u00e7ekten ka\u00e7 kullan\u0131c\u0131y\u0131 ve ne kadar ciroyu etkiledi\u011fini hesaplamak \u00e7ok kolay hale gelir.<\/p>\n<h2><span id=\"Odeme_Hatalarini_Sunucu_Loglarindan_Yakalamak\">\u00d6deme Hatalar\u0131n\u0131 Sunucu Loglar\u0131ndan Yakalamak<\/span><\/h2>\n<p>\u00d6deme ad\u0131m\u0131, d\u00f6n\u00fc\u015f\u00fcm kayb\u0131n\u0131n en can ac\u0131tan noktas\u0131d\u0131r. Burada ka\u00e7\u0131r\u0131lan her sipari\u015f, do\u011frudan ciro kayb\u0131 demektir. \u00d6deme hatalar\u0131 kabaca ikiye ayr\u0131l\u0131r:<\/p>\n<ul>\n<li><strong>Kullan\u0131c\u0131\/banka kaynakl\u0131 hatalar:<\/strong> yetersiz bakiye, kart\u0131n reddedilmesi, 3D \u015fifre hatas\u0131 vb.<\/li>\n<li><strong>Teknik hatalar:<\/strong> timeout, 5xx, yanl\u0131\u015f imza, callback&#8217;in i\u015flenememesi vb.<\/li>\n<\/ul>\n<p>\u0130\u015fin g\u00fczel taraf\u0131, teknik hatalar\u0131n neredeyse tamam\u0131n\u0131 do\u011fru log stratejisiyle yakalayabilirsiniz.<\/p>\n<h3><span id=\"Odeme_saglayici_hata_kodlarini_normallestirmek\">\u00d6deme sa\u011flay\u0131c\u0131 hata kodlar\u0131n\u0131 normalle\u015ftirmek<\/span><\/h3>\n<p>Farkl\u0131 bankalar ve \u00f6deme sa\u011flay\u0131c\u0131lar farkl\u0131 hata kodlar\u0131 ve mesajlar kullan\u0131r. Bunlar\u0131 uygulama taraf\u0131nda birka\u00e7 kategoriye indirgemek, log analizi i\u00e7in hayat kurtar\u0131c\u0131d\u0131r. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>technical_error (timeout, 5xx, network, imza do\u011frulama hatas\u0131)<\/li>\n<li>bank_decline (banka reddi, limit yetersiz vb.)<\/li>\n<li>user_canceled (kullan\u0131c\u0131 iptali, 3D sayfas\u0131ndan geri d\u00f6nme)<\/li>\n<\/ul>\n<p>Uygulama logunuza, her \u00f6deme giri\u015fimi i\u00e7in bu normalle\u015ftirilmi\u015f bir alan eklerseniz, log taraf\u0131nda \u015fu tip sorgular yapabilirsiniz:<\/p>\n<ul>\n<li>Son 1 saatte technical_error oran\u0131nda ani art\u0131\u015f var m\u0131?<\/li>\n<li>Hangi kampanya veya trafik kayna\u011f\u0131nda bank_decline oran\u0131 daha y\u00fcksek?<\/li>\n<\/ul>\n<h3><span id=\"Timeout_ve_performans_kaynakli_odeme_problemleri\">Timeout ve performans kaynakl\u0131 \u00f6deme problemleri<\/span><\/h3>\n<p>\u00d6deme s\u00fcrecinde en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz teknik problemlerden biri timeout&#8217;lard\u0131r. Senaryolar genelde \u015f\u00f6yle geli\u015fir:<\/p>\n<ul>\n<li>Kampanya d\u00f6neminde trafik artar.<\/li>\n<li>Veritaban\u0131 yava\u015flar veya kilitlenir.<\/li>\n<li>\u00d6deme iste\u011finin i\u015flendi\u011fi PHP\/uygulama kodu zaman\u0131nda yan\u0131t veremez.<\/li>\n<li>Kullan\u0131c\u0131 ya hata g\u00f6r\u00fcr ya da banka sayfas\u0131nda tak\u0131l\u0131 kal\u0131r.<\/li>\n<\/ul>\n<p>Bu tip problemleri loglardan yakalamak i\u00e7in:<\/p>\n<ul>\n<li>access.log&#8217;da uzun s\u00fcren istekleri (\u00f6rne\u011fin &gt; 2 sn) i\u015faretlemek,<\/li>\n<li>error.log&#8217;da gateway timeout veya connection timeout mesajlar\u0131n\u0131 filtrelemek,<\/li>\n<li>uygulama loglar\u0131nda \u00f6deme fonksiyonlar\u0131n\u0131n \u00e7al\u0131\u015fma s\u00fcrelerini \u00f6l\u00e7mek<\/li>\n<\/ul>\n<p>\u00e7ok i\u015fe yarar. Altyap\u0131 taraf\u0131nda performans optimizasyonu gerekiyorsa, <a href=\"https:\/\/www.dchost.com\/blog\/woocommerce-ve-buyuk-katalog-siteleri-icin-mysql-indeksleme-ve-sorgu\/\">WooCommerce ve b\u00fcy\u00fck katalog siteleri i\u00e7in MySQL indeksleme rehberi<\/a> veya <a href=\"https:\/\/www.dchost.com\/blog\/php-ayarlarini-dogru-yapmak-memory-limit-max-execution-time\/\">PHP taraf\u0131nda do\u011fru memory_limit ve max_execution_time ayarlar\u0131<\/a> gibi yaz\u0131lar\u0131m\u0131zdan da faydalanabilirsiniz.<\/p>\n<h3><span id=\"Callback_ve_webhook_sorunlarini_loglardan_yakalamak\">Callback ve webhook sorunlar\u0131n\u0131 loglardan yakalamak<\/span><\/h3>\n<p>\u00d6deme s\u00fcre\u00e7lerinde belki de en az fark edilen ama en kritik ad\u0131m, banka\/\u00f6deme kurulu\u015funun sizin sitenize g\u00f6nderdi\u011fi <strong>callback\/webhook<\/strong> istekleridir. Bu isteklerde ya\u015fanan problemler:<\/p>\n<ul>\n<li>Kullan\u0131c\u0131 kart\u0131ndan para \u00e7ekilmi\u015f olsa bile sipari\u015fin sisteminizde olu\u015fmamas\u0131na,<\/li>\n<li>Sipari\u015fin &#8220;beklemede&#8221; kalmas\u0131na,<\/li>\n<li>Stok ve muhasebe kay\u0131tlar\u0131n\u0131n tutmamas\u0131na<\/li>\n<\/ul>\n<p>neden olabilir. Callback sorunlar\u0131n\u0131 loglardan yakalamak i\u00e7in:<\/p>\n<ul>\n<li>Callback URL&#8217;sine gelen t\u00fcm istekleri ayr\u0131 bir log dosyas\u0131nda toplamak,<\/li>\n<li>Bu istekler i\u00e7in HTTP durum kodlar\u0131n\u0131 (200, 400, 500) d\u00fczenli izlemek,<\/li>\n<li>Ba\u015far\u0131s\u0131z callback&#8217;ler i\u00e7in otomatik alarm \u00fcretmek<\/li>\n<\/ul>\n<p>olmazsa olmazd\u0131r. \u00d6zellikle 500 ve 4xx kodlar\u0131 art\u0131yorsa, \u00e7o\u011fu zaman uygulama validasyon kurallar\u0131 veya g\u00fcvenlik ayarlar\u0131 (\u00f6rne\u011fin WAF) callback&#8217;leri yanl\u0131\u015fl\u0131kla engelliyor demektir.<\/p>\n<h2><span id=\"Alarm_Rapor_ve_Otomasyon_Log_Analizini_Gunluk_Rutine_Cevirmek\">Alarm, Rapor ve Otomasyon: Log Analizini G\u00fcnl\u00fck Rutine \u00c7evirmek<\/span><\/h2>\n<p>Log analizi bir kerelik bir \u00e7al\u0131\u015fma de\u011fil, ya\u015fayan bir s\u00fcre\u00e7 olmal\u0131d\u0131r. Bunu ger\u00e7ekten faydal\u0131 hale getirmek i\u00e7in \u00fc\u00e7 katmanl\u0131 bir yap\u0131 \u00f6neriyoruz: <strong>alarm<\/strong>, <strong>g\u00f6sterge paneli<\/strong> ve <strong>d\u00fczenli raporlar<\/strong>.<\/p>\n<h3><span id=\"Anlik_alarm_kurallari\">Anl\u0131k alarm kurallar\u0131<\/span><\/h3>\n<p>Anl\u0131k alarm i\u00e7in hedefiniz, &#8220;yang\u0131n \u00e7\u0131kt\u0131\u011f\u0131nda telefona bildirim d\u00fc\u015fs\u00fcn&#8221; noktas\u0131d\u0131r. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Son 5 dakikada checkout URL&#8217;lerinde 5xx oran\u0131 %3&#8217;\u00fc ge\u00e7tiyse alarm.<\/li>\n<li>Son 10 dakikada payment_failed i\u00e7eren log sat\u0131r\u0131 say\u0131s\u0131 normalin 2 kat\u0131na \u00e7\u0131kt\u0131ysa alarm.<\/li>\n<li>Callback URL&#8217;sinde \u00fcst \u00fcste 10 adet 500 hatas\u0131 olu\u015ftuysa alarm.<\/li>\n<\/ul>\n<p>Merkezi loglama (Loki, ELK vb.) ve metrik sistemleri (Prometheus, Netdata) burada devreye giriyor. Daha \u00f6nce bahsetti\u011fimiz <a href=\"https:\/\/www.dchost.com\/blog\/vps-log-yonetimi-nasil-rayina-oturur-grafana-loki-promtail-ile-merkezi\/\">Grafana Loki + Promtail ile log y\u00f6netimi<\/a> yaz\u0131m\u0131zda, bu t\u00fcr alarm kurallar\u0131n\u0131n nas\u0131l tan\u0131mlanabilece\u011fine dair somut \u00f6rnekler bulabilirsiniz.<\/p>\n<h3><span id=\"Gosterge_panelleri_dashboard_ile_buyuk_resmi_gormek\">G\u00f6sterge panelleri (dashboard) ile b\u00fcy\u00fck resmi g\u00f6rmek<\/span><\/h3>\n<p>G\u00fcnl\u00fck i\u015flerin i\u00e7inde kaybolmamak i\u00e7in, loglardan beslenen birka\u00e7 temel g\u00f6sterge paneli kurman\u0131z\u0131 \u00f6neriyoruz:<\/p>\n<ul>\n<li>Genel hata oran\u0131 (4xx\/5xx) \u2013 zaman serisi<\/li>\n<li>Sepet ve \u00f6deme funnel&#8217;\u0131 \u2013 ad\u0131m ad\u0131m d\u00f6n\u00fc\u015f\u00fcm oran\u0131<\/li>\n<li>\u00d6deme hata kategorileri (technical_error, bank_decline, user_canceled) da\u011f\u0131l\u0131m\u0131<\/li>\n<li>En \u00e7ok hata \u00fcreten ilk 10 URL<\/li>\n<\/ul>\n<p>Bu paneller, ekip toplant\u0131lar\u0131nda &#8220;hissiyat&#8221; yerine <strong>veriye dayal\u0131<\/strong> konu\u015fman\u0131z\u0131 sa\u011flar. \u00d6rne\u011fin, yeni bir tema g\u00fcncellemesinden sonra checkout sayfas\u0131nda 500 hata oran\u0131n\u0131n artt\u0131\u011f\u0131n\u0131 net bi\u00e7imde g\u00f6rebilirsiniz.<\/p>\n<h3><span id=\"Crontab_ile_duzenli_raporlar_uretmek\">Crontab ile d\u00fczenli raporlar \u00fcretmek<\/span><\/h3>\n<p>Her ekibin merkezi log sistemi veya geli\u015fmi\u015f dashboard altyap\u0131s\u0131 olmayabilir. B\u00f6yle durumlarda bile, basit bash script&#8217;leri ve cron job&#8217;lar ile g\u00fcnl\u00fck \u00f6zet raporlar \u00fcretmek m\u00fcmk\u00fcnd\u00fcr. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>G\u00fcn sonunda son 24 saate ait 4xx\/5xx istatistiklerini \u00e7\u0131karan bir script<\/li>\n<li>Sepet ve \u00f6deme URL&#8217;leri i\u00e7in hata oranlar\u0131n\u0131 hesaplayan k\u00fc\u00e7\u00fck bir ara\u00e7<\/li>\n<li>Bu \u00e7\u0131kt\u0131lar\u0131 e\u2011posta ile teknik ekibe g\u00f6nderen bir yap\u0131<\/li>\n<\/ul>\n<p>Bu tarz otomasyonlar i\u00e7in cron taraf\u0131nda dikkat etmeniz gereken noktalar hakk\u0131nda, <a href=\"https:\/\/www.dchost.com\/blog\/linux-crontab-en-iyi-uygulamalar-rehberi-yedek-rapor-ve-bakim-isleri\/\">Linux crontab en iyi uygulamalar rehberimizde<\/a> bolca pratik \u00f6neri bulursunuz.<\/p>\n<h2><span id=\"DCHost_Altyapisinda_Log_Analizi_Icin_Pratik_Oneriler\">DCHost Altyap\u0131s\u0131nda Log Analizi \u0130\u00e7in Pratik \u00d6neriler<\/span><\/h2>\n<p>DCHost olarak hem payla\u015f\u0131ml\u0131 e\u2011ticaret hosting paketlerinde hem de <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>\/dedicated ve colocation altyap\u0131lar\u0131m\u0131zda log analizi yapmay\u0131 kolayla\u015ft\u0131racak baz\u0131 pratik \u00f6nerilerimiz var:<\/p>\n<ul>\n<li><strong>Ayr\u0131 log dizini ve yeterli disk alan\u0131:<\/strong> \u00d6zellikle y\u00fcksek trafikli ma\u011fazalar i\u00e7in loglar ayr\u0131 bir disk b\u00f6l\u00fcm\u00fcnde tutulmal\u0131 ve b\u00fcy\u00fcme h\u0131z\u0131 izlenmelidir.<\/li>\n<li><strong>Standart log format\u0131:<\/strong> T\u00fcm web sunucular\u0131n\u0131zda (Nginx\/Apache) ayn\u0131 log format\u0131n\u0131 kullan\u0131n ki merkezi analizde zorlanmay\u0131n.<\/li>\n<li><strong>Merkezi loglama:<\/strong> Birden fazla web, uygulama ve veritaban\u0131 sunucunuz varsa, loglar\u0131 merkezi bir sisteme (Loki\/ELK tarz\u0131) ak\u0131tmak, e\u2011ticaret ekipleri i\u00e7in ciddi zaman kazand\u0131r\u0131r. Bu mimari i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/birden-fazla-sunucuda-log-yonetimi-elk-ve-loki-stack-ile-merkezi-hosting-loglama\/\">birden fazla sunucuda log y\u00f6netimi rehberimiz<\/a> iyi bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r.<\/li>\n<li><strong>Test\/staging ortam\u0131nda da loglamak:<\/strong> Canl\u0131ya \u00e7\u0131kmadan \u00f6nce staging ortam\u0131nda sepet ve \u00f6deme ak\u0131\u015f\u0131n\u0131 ayn\u0131 log yap\u0131s\u0131yla test etmek, hatalar\u0131n prod&#8217;a yans\u0131madan yakalanmas\u0131n\u0131 sa\u011flar.<\/li>\n<li><strong>Destek ekibi ile ortak dil:<\/strong> DCHost taraf\u0131ndaki destek ekibimizle konu\u015furken eri\u015fim logu, hata logu, zaman aral\u0131\u011f\u0131 ve \u00f6rnek URL&#8217;leri net verirseniz, sorun tespit s\u00fcresi dramatik \u015fekilde k\u0131sal\u0131r.<\/li>\n<\/ul>\n<h2><span id=\"Sonuc_ve_Yol_Haritasi_Loglari_Okuyan_ETicaret_Kazanir\">Sonu\u00e7 ve Yol Haritas\u0131: Loglar\u0131 Okuyan E\u2011Ticaret Kazan\u0131r<\/span><\/h2>\n<p>D\u00f6n\u00fc\u015f\u00fcm kayb\u0131 \u00e7o\u011fu zaman &#8220;kullan\u0131c\u0131 al\u0131\u015fkanl\u0131klar\u0131&#8221; veya &#8220;pazarlama performans\u0131&#8221; gibi ba\u015fl\u0131klara y\u0131k\u0131l\u0131r. Oysa <strong>sunucu loglar\u0131<\/strong> bize ba\u015fka bir hik\u00e2ye anlat\u0131r: 5 dakika boyunca checkout sayfas\u0131nda 500 hatas\u0131 alan kullan\u0131c\u0131lar, 404 d\u00f6nen \u00fcr\u00fcn sayfalar\u0131, timeout nedeniyle yar\u0131m kalan \u00f6demeler, callback&#8217;i i\u015flenemedi\u011fi i\u00e7in sistemde g\u00f6r\u00fcnmeyen sipari\u015fler\u2026 Bunlar sadece pazarlama de\u011fil, do\u011frudan <strong>altyap\u0131 ve uygulama kalitesi<\/strong> problemidir.<\/p>\n<p>Bu yaz\u0131da DCHost ekibi olarak, e\u2011ticaret siteniz i\u00e7in:<\/p>\n<ul>\n<li>Hangi loglar\u0131n kritik oldu\u011funu,<\/li>\n<li>4xx\/5xx hatalar\u0131ndan d\u00f6n\u00fc\u015f\u00fcm kayb\u0131n\u0131 nas\u0131l yakalayabilece\u011finizi,<\/li>\n<li>\u00d6deme hatalar\u0131n\u0131 loglardan nas\u0131l ayr\u0131\u015ft\u0131rabilece\u011finizi,<\/li>\n<li>Alarm, dashboard ve cron raporlar\u0131yla bu s\u00fcreci nas\u0131l otomatikle\u015ftirebilece\u011finizi<\/li>\n<\/ul>\n<p>\u00f6zetledik. Bundan sonraki ad\u0131m, siteniz i\u00e7in k\u00fc\u00e7\u00fck ama somut bir plan yapmak olabilir: bug\u00fcn access.log ve error.log&#8217;unuzu kontrol edip sepet\/\u00f6deme URL&#8217;lerinizin hata oranlar\u0131n\u0131 \u00e7\u0131kar\u0131n; sonraki hafta uygulama loglar\u0131na event bazl\u0131 kay\u0131t ekleyin; ard\u0131ndan da basit bir alarm kural\u0131 kurun.<\/p>\n<p>E\u011fer DCHost \u00fczerinde \u00e7al\u0131\u015fan bir e\u2011ticaret siteniz varsa veya yeni bir VPS\/dedicated\/colocation mimarisi planl\u0131yorsan\u0131z, log stratejinizi projelendirme a\u015famas\u0131nda birlikte tasarlayabiliriz. B\u00f6ylece sepetlerin ve \u00f6demelerin kayboldu\u011fu anlar\u0131 yaln\u0131zca hissederek de\u011fil, <strong>loglarla kan\u0131tlayarak<\/strong> g\u00f6rebilir; sorunlar\u0131 dakikalar i\u00e7inde yakalay\u0131p saatlerce, hatta g\u00fcnlerce s\u00fcrecek ciro kayb\u0131n\u0131n \u00f6n\u00fcne ge\u00e7ebilirsiniz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>E\u2011ticarette Log Analizi Neden Bu Kadar \u00d6nemli? E\u2011ticaret taraf\u0131nda b\u00fcy\u00fcme konu\u015fulan her toplant\u0131da mutlaka iki kelime ge\u00e7er: d\u00f6n\u00fc\u015f\u00fcm oran\u0131 ve kaybolan sepetler. Trafik sat\u0131n al\u0131r, kampanyalar kurgular, tasar\u0131m\u0131 iyile\u015ftirirsiniz; fakat baz\u0131 kullan\u0131c\u0131lar tam \u00f6deme ad\u0131m\u0131nda sessizce kaybolur. Analytics ara\u00e7lar\u0131 size belli bir seviyeye kadar yol g\u00f6sterir, ancak teknik sorunlar ba\u015flad\u0131\u011f\u0131nda ger\u00e7ekten ne oldu\u011funu s\u00f6yleyen tek [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3533,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3532","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\/3532","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=3532"}],"version-history":[{"count":2,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3532\/revisions"}],"predecessor-version":[{"id":5612,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3532\/revisions\/5612"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3533"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3532"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3532"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3532"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}