{"id":4728,"date":"2026-02-07T20:44:13","date_gmt":"2026-02-07T17:44:13","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/cpanel-ve-vpste-log-arsivleme-stratejisi-gzip-s3-ve-saklama-sureleri\/"},"modified":"2026-02-07T20:44:13","modified_gmt":"2026-02-07T17:44:13","slug":"cpanel-ve-vpste-log-arsivleme-stratejisi-gzip-s3-ve-saklama-sureleri","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/cpanel-ve-vpste-log-arsivleme-stratejisi-gzip-s3-ve-saklama-sureleri\/","title":{"rendered":"cPanel ve VPS\u2019te Log Ar\u015fivleme Stratejisi: gzip, S3 ve Saklama S\u00fcreleri"},"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=\"#Neden_cPanel_ve_VPSte_Log_Arsivleme_Stratejisi_Sart\"><span class=\"toc_number toc_depth_1\">1.<\/span> Neden cPanel ve VPS\u2019te Log Ar\u015fivleme Stratejisi \u015eart?<\/a><\/li><li><a href=\"#cPanel_Ortaminda_Log_Turleri_ve_Varsayilan_Davranis\"><span class=\"toc_number toc_depth_1\">2.<\/span> cPanel Ortam\u0131nda Log T\u00fcrleri ve Varsay\u0131lan Davran\u0131\u015f<\/a><ul><li><a href=\"#Baslica_log_turleri\"><span class=\"toc_number toc_depth_2\">2.1.<\/span> Ba\u015fl\u0131ca log t\u00fcrleri<\/a><\/li><li><a href=\"#WHM_tarafinda_log_ayarlari\"><span class=\"toc_number toc_depth_2\">2.2.<\/span> WHM taraf\u0131nda log ayarlar\u0131<\/a><\/li><li><a href=\"#cPanel_loglari_icin_ilk_yapilmasi_gerekenler\"><span class=\"toc_number toc_depth_2\">2.3.<\/span> cPanel loglar\u0131 i\u00e7in ilk yap\u0131lmas\u0131 gerekenler<\/a><\/li><\/ul><\/li><li><a href=\"#VPS_Uzerinde_Loglar_Nginx_Apache_Uygulama_ve_Sistem\"><span class=\"toc_number toc_depth_1\">3.<\/span> VPS \u00dczerinde Loglar: Nginx, Apache, Uygulama ve Sistem<\/a><\/li><li><a href=\"#gzip_ile_Log_Sikistirma_Temel_Ilkeler_ve_logrotate_Ornekleri\"><span class=\"toc_number toc_depth_1\">4.<\/span> gzip ile Log S\u0131k\u0131\u015ft\u0131rma: Temel \u0130lkeler ve logrotate \u00d6rnekleri<\/a><ul><li><a href=\"#gzip_sikistirma_seviyeleri\"><span class=\"toc_number toc_depth_2\">4.1.<\/span> gzip s\u0131k\u0131\u015ft\u0131rma seviyeleri<\/a><\/li><li><a href=\"#Nginx_icin_ornek_logrotate_konfigurasyonu\"><span class=\"toc_number toc_depth_2\">4.2.<\/span> Nginx i\u00e7in \u00f6rnek logrotate konfig\u00fcrasyonu<\/a><\/li><li><a href=\"#Custom_uygulama_loglari_icin_logrotate\"><span class=\"toc_number toc_depth_2\">4.3.<\/span> Custom uygulama loglar\u0131 i\u00e7in logrotate<\/a><\/li><\/ul><\/li><li><a href=\"#S3Object_Storagea_Log_Offload_Mimarisi\"><span class=\"toc_number toc_depth_1\">5.<\/span> S3\/Object Storage\u2019a Log Offload Mimarisi<\/a><ul><li><a href=\"#Hedef_mimari\"><span class=\"toc_number toc_depth_2\">5.1.<\/span> Hedef mimari<\/a><\/li><li><a href=\"#rclone_ile_log_offload_ornegi\"><span class=\"toc_number toc_depth_2\">5.2.<\/span> rclone ile log offload \u00f6rne\u011fi<\/a><\/li><li><a href=\"#Cron_ile_otomasyon\"><span class=\"toc_number toc_depth_2\">5.3.<\/span> Cron ile otomasyon<\/a><\/li><li><a href=\"#Guvenlik_ve_erisim_kontrolleri\"><span class=\"toc_number toc_depth_2\">5.4.<\/span> G\u00fcvenlik ve eri\u015fim kontrolleri<\/a><\/li><\/ul><\/li><li><a href=\"#Saklama_Suresi_Politikalari_Operasyon_Guvenlik_ve_KVKK_Dengesi\"><span class=\"toc_number toc_depth_1\">6.<\/span> Saklama S\u00fcresi Politikalar\u0131: Operasyon, G\u00fcvenlik ve KVKK Dengesi<\/a><ul><li><a href=\"#Log_turune_gore_onerilen_saklama_seviyeleri\"><span class=\"toc_number toc_depth_2\">6.1.<\/span> Log t\u00fcr\u00fcne g\u00f6re \u00f6nerilen saklama seviyeleri<\/a><\/li><li><a href=\"#Object_storage_tarafinda_Lifecycle_Policy_kullanimi\"><span class=\"toc_number toc_depth_2\">6.2.<\/span> Object storage taraf\u0131nda Lifecycle Policy kullan\u0131m\u0131<\/a><\/li><li><a href=\"#KVKKGDPR_boyutu_ve_anonimlestirme\"><span class=\"toc_number toc_depth_2\">6.3.<\/span> KVKK\/GDPR boyutu ve anonimle\u015ftirme<\/a><\/li><\/ul><\/li><li><a href=\"#cPanelde_Uygulanabilir_Log_Arsivleme_Senaryosu_Adim_Adim\"><span class=\"toc_number toc_depth_1\">7.<\/span> cPanel\u2019de Uygulanabilir Log Ar\u015fivleme Senaryosu (Ad\u0131m Ad\u0131m)<\/a><ul><li><a href=\"#1_Envanter_ve_hedefler\"><span class=\"toc_number toc_depth_2\">7.1.<\/span> 1. Envanter ve hedefler<\/a><\/li><li><a href=\"#2_WHM_log_ayarlarini_guncelleyin\"><span class=\"toc_number toc_depth_2\">7.2.<\/span> 2. WHM log ayarlar\u0131n\u0131 g\u00fcncelleyin<\/a><\/li><li><a href=\"#3_logrotate_yapilarini_gozden_gecirin\"><span class=\"toc_number toc_depth_2\">7.3.<\/span> 3. logrotate yap\u0131lar\u0131n\u0131 g\u00f6zden ge\u00e7irin<\/a><\/li><li><a href=\"#4_rclone_ile_object_storage_senkronizasyonu_kurun\"><span class=\"toc_number toc_depth_2\">7.4.<\/span> 4. rclone ile object storage senkronizasyonu kurun<\/a><\/li><li><a href=\"#5_Cron_ile_zamanlama_ve_lokal_temizlik\"><span class=\"toc_number toc_depth_2\">7.5.<\/span> 5. Cron ile zamanlama ve lokal temizlik<\/a><\/li><li><a href=\"#6_Geri_donus_restore_senaryosunu_test_edin\"><span class=\"toc_number toc_depth_2\">7.6.<\/span> 6. Geri d\u00f6n\u00fc\u015f (restore) senaryosunu test edin<\/a><\/li><\/ul><\/li><li><a href=\"#VPSte_Gelismis_Log_Arsivleme_Merkezi_ve_Cok_Sunuculu_Yapilar\"><span class=\"toc_number toc_depth_1\">8.<\/span> VPS\u2019te Geli\u015fmi\u015f Log Ar\u015fivleme: Merkezi ve \u00c7ok Sunuculu Yap\u0131lar<\/a><\/li><li><a href=\"#Sik_Yapilan_Hatalar_ve_DCHost_Tarafinda_Onerdigimiz_Ipuclari\"><span class=\"toc_number toc_depth_1\">9.<\/span> S\u0131k Yap\u0131lan Hatalar ve DCHost Taraf\u0131nda \u00d6nerdi\u011fimiz \u0130pu\u00e7lar\u0131<\/a><\/li><li><a href=\"#Sonuc_ve_DCHost_ile_Yol_Haritanizi_Netlestirin\"><span class=\"toc_number toc_depth_1\">10.<\/span> Sonu\u00e7 ve DCHost ile Yol Haritan\u0131z\u0131 Netle\u015ftirin<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Neden_cPanel_ve_VPSte_Log_Arsivleme_Stratejisi_Sart\">Neden cPanel ve <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>\u2019te Log Ar\u015fivleme Stratejisi \u015eart?<\/span><\/h2>\n<p>Loglar, bir sunucunun kara kutusudur: Performans sorunlar\u0131n\u0131, g\u00fcvenlik ihlallerini, e\u2011posta teslim problemlerini ve uygulama hatalar\u0131n\u0131 geriye d\u00f6n\u00fck olarak analiz etmenin tek somut kayna\u011f\u0131d\u0131r. Ancak plans\u0131z loglama, birka\u00e7 ay i\u00e7inde diski dolduran, arand\u0131\u011f\u0131nda bulunamayan ve KVKK\/GDPR taraf\u0131nda ba\u015f\u0131n\u0131z\u0131 a\u011fr\u0131tabilecek bir veri y\u0131\u011f\u0131n\u0131na d\u00f6n\u00fc\u015f\u00fcr. \u00d6zellikle cPanel kullanan <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a> ortamlar\u0131nda ve kendi y\u00f6netti\u011finiz VPS sunucularda, loglar\u0131n <strong>nas\u0131l s\u0131k\u0131\u015ft\u0131r\u0131ld\u0131\u011f\u0131<\/strong>, <strong>nereye ar\u015fivlendi\u011fi<\/strong> ve <strong>ne kadar s\u00fcre sakland\u0131\u011f\u0131<\/strong> net tan\u0131mlanmad\u0131\u011f\u0131nda, bir g\u00fcn ans\u0131z\u0131n \u201cNo space left on device\u201d veya \u201c\u015fu tarihteki eri\u015fimleri g\u00f6sterebilir misiniz?\u201d sorusuyla kar\u015f\u0131la\u015fman\u0131z an meselesidir.<\/p>\n<p>Bu yaz\u0131da DCHost ekibi olarak, cPanel ve VPS ortamlar\u0131nda g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ger\u00e7ek senaryolardan yola \u00e7\u0131karak log ar\u015fivleme i\u00e7in uygulanabilir bir yol haritas\u0131 \u00e7\u0131karaca\u011f\u0131z. <strong>gzip ile s\u0131k\u0131\u015ft\u0131rma seviyeleri<\/strong>, <strong>S3\/object storage offload mimarisi<\/strong> ve <strong>KVKK\/GDPR ile uyumlu saklama s\u00fcresi politikalar\u0131<\/strong> \u00fczerinden gidece\u011fiz. Yaz\u0131y\u0131 bitirdi\u011finizde, ister tek bir cPanel hesab\u0131n\u0131z olsun ister onlarca VPS y\u00f6netin, loglar i\u00e7in <strong>tutarl\u0131, otomasyona ba\u011flanm\u0131\u015f ve test edilmi\u015f<\/strong> bir ar\u015fivleme stratejisini nas\u0131l kuraca\u011f\u0131n\u0131z\u0131 net \u015fekilde kafan\u0131zda canland\u0131rm\u0131\u015f olacaks\u0131n\u0131z.<\/p>\n<h2><span id=\"cPanel_Ortaminda_Log_Turleri_ve_Varsayilan_Davranis\">cPanel Ortam\u0131nda Log T\u00fcrleri ve Varsay\u0131lan Davran\u0131\u015f<\/span><\/h2>\n<p>cPanel sunucularda loglar bir\u00e7ok farkl\u0131 klas\u00f6re da\u011f\u0131lm\u0131\u015f durumdad\u0131r ve varsay\u0131lan ayarlar\u0131n ne yapt\u0131\u011f\u0131n\u0131 bilmezseniz, baz\u0131 kritik kay\u0131tlar\u0131 gere\u011finden k\u0131sa, baz\u0131lar\u0131n\u0131 ise gereksiz yere uzun s\u00fcre saklayabilirsiniz.<\/p>\n<h3><span id=\"Baslica_log_turleri\">Ba\u015fl\u0131ca log t\u00fcrleri<\/span><\/h3>\n<ul>\n<li><strong>Apache eri\u015fim loglar\u0131 (domlogs)<\/strong>: Genellikle <code>\/usr\/local\/apache\/domlogs\/<\/code> alt\u0131nda tutulur. Her domain i\u00e7in ayr\u0131 dosyalar vard\u0131r.<\/li>\n<li><strong>Apache hata logu<\/strong>: \u00d6rne\u011fin <code>\/usr\/local\/apache\/logs\/error_log<\/code>. PHP hatalar\u0131, 500 hatalar\u0131 vb. burada g\u00f6r\u00fcn\u00fcr.<\/li>\n<li><strong>cPanel kullan\u0131c\u0131 loglar\u0131<\/strong>: Her hesab\u0131n <code>cPanel &gt; Metrics &gt; Errors<\/code> ve <code>Raw Access<\/code> men\u00fclerinden indirebildi\u011fi loglar.<\/li>\n<li><strong>Mail loglar\u0131<\/strong>: Exim i\u00e7in <code>\/var\/log\/exim_mainlog<\/code>, <code>exim_rejectlog<\/code>; Dovecot\/IMAP i\u00e7in ayr\u0131 loglar.<\/li>\n<li><strong>FTP, cPHulk, eri\u015fim loglar\u0131<\/strong>: Giri\u015f denemeleri, brute-force tespitleri, panel eri\u015fimleri vb. i\u00e7in.<\/li>\n<li><strong>Sistem loglar\u0131<\/strong>: <code>\/var\/log\/messages<\/code>, <code>\/var\/log\/secure<\/code> gibi \u00e7ekirdek ve servis loglar\u0131.<\/li>\n<\/ul>\n<h3><span id=\"WHM_tarafinda_log_ayarlari\">WHM taraf\u0131nda log ayarlar\u0131<\/span><\/h3>\n<p>cPanel\/WHM\u2019de <strong>Tweak Settings &gt; Stats and Logs<\/strong> b\u00f6l\u00fcm\u00fcnde birka\u00e7 kritik ayar bulunur:<\/p>\n<ul>\n<li><strong>\u201cArchive logs in \/usr\/local\/apache\/domlogs too?\u201d<\/strong> \u2013 Eri\u015fim loglar\u0131n\u0131 ar\u015fivleyip s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f \u015fekilde domlogs alt\u0131nda biriktirir.<\/li>\n<li><strong>\u201cKeep log files at least X days\u201d<\/strong> \u2013 Apache loglar\u0131n\u0131n minimum saklama s\u00fcresini belirler.<\/li>\n<li><strong>Stat programlar\u0131 (AWStats, Webalizer) i\u00e7in log saklama<\/strong> \u2013 \u0130statistik \u00fcretimi i\u00e7in ne kadar geriye d\u00f6n\u00fck log tutulaca\u011f\u0131n\u0131 belirler.<\/li>\n<\/ul>\n<p>Bu ayarlar\u0131 log ar\u015fivleme stratejinizle uyumlu hale getirmedi\u011finizde, cPanel kendi i\u00e7inde bir \u015feyler yaparken sizin harici otomatizasyonlar\u0131n\u0131z farkl\u0131 bir mant\u0131kla log silip b\u0131rakabilir. \u00d6zellikle <strong>raw access log<\/strong> dosyalar\u0131n\u0131n ne kadar s\u00fcre cPanel hesab\u0131 i\u00e7inde tutulaca\u011f\u0131n\u0131 belirlemek, hem diski hem de KVKK uyumunu do\u011frudan etkiler.<\/p>\n<h3><span id=\"cPanel_loglari_icin_ilk_yapilmasi_gerekenler\">cPanel loglar\u0131 i\u00e7in ilk yap\u0131lmas\u0131 gerekenler<\/span><\/h3>\n<ul>\n<li>Hangi log dosyalar\u0131n\u0131n <strong>uygulama hatas\u0131 debuggingi<\/strong> i\u00e7in, hangilerinin <strong>g\u00fcvenlik ve yasal ispat<\/strong> i\u00e7in kritik oldu\u011funu listeleyin.<\/li>\n<li>Apache, Exim ve sistem loglar\u0131 i\u00e7in <code>\/etc\/logrotate.d\/<\/code> alt\u0131ndaki dosyalar\u0131 inceleyin; rotasyon s\u0131kl\u0131\u011f\u0131n\u0131 ve saklama say\u0131s\u0131n\u0131 not al\u0131n.<\/li>\n<li>Paneldeki \u201carchive logs\u201d ayarlar\u0131n\u0131, planlad\u0131\u011f\u0131n\u0131z gzip + object storage offload stratejisiyle uyumlu olacak \u015fekilde g\u00fcncelleyin.<\/li>\n<\/ul>\n<h2><span id=\"VPS_Uzerinde_Loglar_Nginx_Apache_Uygulama_ve_Sistem\">VPS \u00dczerinde Loglar: Nginx, Apache, Uygulama ve Sistem<\/span><\/h2>\n<p>Kendi y\u00f6netti\u011finiz VPS\u2019lerde cPanel olmak zorunda de\u011fil; Nginx, Apache, Node.js, Laravel, Docker vb. birle\u015fik mimarilerde loglar\u0131n da\u011f\u0131n\u0131kl\u0131\u011f\u0131 daha da artar. DCHost \u00fczerinde y\u00f6netti\u011fimiz VPS ortamlar\u0131nda en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz log konumlar\u0131 \u015f\u00f6yle:<\/p>\n<ul>\n<li><strong>Nginx<\/strong>: <code>\/var\/log\/nginx\/access.log<\/code>, <code>\/var\/log\/nginx\/error.log<\/code><\/li>\n<li><strong>Apache<\/strong>: <code>\/var\/log\/httpd\/<\/code> veya <code>\/var\/log\/apache2\/<\/code> alt\u0131ndaki eri\u015fim ve hata loglar\u0131<\/li>\n<li><strong>PHP-FPM<\/strong>: <code>\/var\/log\/php-fpm\/error.log<\/code> veya havuz bazl\u0131 loglar<\/li>\n<li><strong>Uygulama loglar\u0131<\/strong>: Laravel i\u00e7in <code>storage\/logs\/laravel.log<\/code>, Node.js uygulamalar\u0131 i\u00e7in kendi olu\u015fturdu\u011funuz <code>logs\/<\/code> klas\u00f6rleri vb.<\/li>\n<li><strong>systemd \/ journald<\/strong>: <code>journalctl<\/code> \u00fczerinden eri\u015filen servis loglar\u0131, \/var\/log yerine binary journal format\u0131nda tutuluyor olabilir.<\/li>\n<\/ul>\n<p>E\u011fer log rotasyonu sadece Nginx ve Apache i\u00e7in kurulu, ancak Laravel veya Node.js loglar\u0131 hi\u00e7 rotate edilmiyorsa, <strong>disk dolma problemleri<\/strong> neredeyse her zaman bu custom loglardan \u00e7\u0131k\u0131yor. Bu konuyu daha \u00f6nce detayl\u0131 ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/vps-disk-kullanimi-ve-logrotate-ayarlariyla-no-space-left-on-device-hatasini-onlemek\/\">VPS disk kullan\u0131m\u0131 ve logrotate ile \u201cNo space left on device\u201d hatas\u0131n\u0131 \u00f6nleme rehberine<\/a> mutlaka g\u00f6z atman\u0131z\u0131 \u00f6neririm.<\/p>\n<h2><span id=\"gzip_ile_Log_Sikistirma_Temel_Ilkeler_ve_logrotate_Ornekleri\">gzip ile Log S\u0131k\u0131\u015ft\u0131rma: Temel \u0130lkeler ve logrotate \u00d6rnekleri<\/span><\/h2>\n<p>Log ar\u015fivleme stratejisinin ilk aya\u011f\u0131, <strong>do\u011fru s\u0131k\u0131\u015ft\u0131rma<\/strong>d\u0131r. Ama\u00e7; analiz i\u00e7in ihtiya\u00e7 duydu\u011funuz kadar detayl\u0131 logu saklarken, disk maliyetini minimumda tutmak ve s\u0131k\u0131\u015ft\u0131rma\/de-s\u0131k\u0131\u015ft\u0131rma s\u0131ras\u0131nda sunucuyu bo\u011fmamakt\u0131r.<\/p>\n<h3><span id=\"gzip_sikistirma_seviyeleri\">gzip s\u0131k\u0131\u015ft\u0131rma seviyeleri<\/span><\/h3>\n<p><code>gzip<\/code> komutu, 1\u20139 aras\u0131 s\u0131k\u0131\u015ft\u0131rma seviyelerine sahiptir:<\/p>\n<ul>\n<li><strong>-1, -2<\/strong>: Daha az CPU, daha b\u00fcy\u00fck dosyalar<\/li>\n<li><strong>-5, -6<\/strong>: \u00c7o\u011fu sunucu i\u00e7in dengeli; iyi s\u0131k\u0131\u015ft\u0131rma, makul CPU kullan\u0131m\u0131<\/li>\n<li><strong>-9<\/strong>: Maksimum s\u0131k\u0131\u015ft\u0131rma, ancak yo\u011fun CPU t\u00fcketimi; y\u00fcksek trafikli sunucularda \u00f6nerilmez<\/li>\n<\/ul>\n<p>Loglar genellikle <strong>tekrarl\u0131 metin<\/strong> i\u00e7erdi\u011fi i\u00e7in orta seviye bir gzip ayar\u0131 bile dosya boyutunu 5\u201310 kata kadar d\u00fc\u015f\u00fcrebilir. DCHost taraf\u0131nda pratikte, logrotate ile <strong>varsay\u0131lan gzip ayarlar\u0131<\/strong> \u00e7o\u011fu i\u015f y\u00fck\u00fc i\u00e7in yeterli; ekstra olarak <code>compressoptions -5<\/code> gibi bir ayarla CPU y\u00fck\u00fcn\u00fc biraz hafifletebilirsiniz.<\/p>\n<h3><span id=\"Nginx_icin_ornek_logrotate_konfigurasyonu\">Nginx i\u00e7in \u00f6rnek logrotate konfig\u00fcrasyonu<\/span><\/h3>\n<p>Tipik bir <code>\/etc\/logrotate.d\/nginx<\/code> dosyas\u0131 \u015f\u00f6yle olabilir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">\/var\/log\/nginx\/*.log {\n    daily\n    missingok\n    rotate 14\n    compress\n    compressoptions -5\n    delaycompress\n    notifempty\n    create 0640 www-data adm\n    sharedscripts\n    postrotate\n        [ -s \/run\/nginx.pid ] &amp;&amp; kill -USR1 $(cat \/run\/nginx.pid)\n    endscript\n}\n<\/code><\/pre>\n<ul>\n<li><strong>daily<\/strong>: G\u00fcnl\u00fck rotasyon<\/li>\n<li><strong>rotate 14<\/strong>: 14 g\u00fcn geriye d\u00f6n\u00fck log tutulur (toplam ~2 hafta)<\/li>\n<li><strong>compress<\/strong>: Eski log dosyalar\u0131 <code>.gz<\/code> uzant\u0131s\u0131yla s\u0131k\u0131\u015ft\u0131r\u0131l\u0131r<\/li>\n<li><strong>delaycompress<\/strong>: En son d\u00f6nen dosya bir sonraki rotasyonda s\u0131k\u0131\u015ft\u0131r\u0131l\u0131r; o g\u00fcne ait log dosyas\u0131n\u0131 hemen analiz etmek isterseniz i\u015finizi kolayla\u015ft\u0131r\u0131r.<\/li>\n<\/ul>\n<p>Benzer bir yap\u0131 Apache ve di\u011fer servisler i\u00e7in de kullan\u0131labilir. \u00d6nemli olan; <strong>lokal disk \u00fczerinde ne kadar s\u00fcre tutulaca\u011f\u0131<\/strong> ile <strong>object storage\u2019a ne zaman ta\u015f\u0131naca\u011f\u0131<\/strong> aras\u0131ndaki ili\u015fkiyi iyi kurman\u0131zd\u0131r.<\/p>\n<h3><span id=\"Custom_uygulama_loglari_icin_logrotate\">Custom uygulama loglar\u0131 i\u00e7in logrotate<\/span><\/h3>\n<p>Laravel, Node.js veya ba\u015fka bir framework ile \u00e7al\u0131\u015fan uygulamalar\u0131n\u0131z varsa, onlar\u0131n log klas\u00f6rlerini de logrotate\u2019e eklemelisiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">\/var\/www\/proje-1\/storage\/logs\/*.log {\n    daily\n    rotate 7\n    compress\n    missingok\n    notifempty\n    copytruncate\n}\n<\/code><\/pre>\n<p><strong>copytruncate<\/strong>, logu kesmeden dosyay\u0131 kopyalay\u0131p bo\u015falt\u0131r; uygulamay\u0131 yeniden ba\u015flatmak istemedi\u011finiz durumlarda kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n<h2><span id=\"S3Object_Storagea_Log_Offload_Mimarisi\">S3\/Object Storage\u2019a Log Offload Mimarisi<\/span><\/h2>\n<p>gzip ile lokal disk taraf\u0131n\u0131 rahatlatt\u0131ktan sonra ikinci ad\u0131m, loglar\u0131 <strong>d\u00fc\u015f\u00fck maliyetli ve \u00f6l\u00e7eklenebilir bir depoya ta\u015f\u0131mak<\/strong>t\u0131r. Bunun i\u00e7in en pratik ve esnek \u00e7\u00f6z\u00fcm, S3 uyumlu <strong>object storage<\/strong> kullanmakt\u0131r. DCHost altyap\u0131s\u0131nda sundu\u011fumuz S3 uyumlu depolama, log ar\u015fivleme senaryolar\u0131nda s\u0131k\u00e7a kulland\u0131\u011f\u0131m\u0131z yap\u0131 ta\u015flar\u0131ndan biri.<\/p>\n<p>Object storage\u2019\u0131n log ar\u015fivleme i\u00e7in neden ideal oldu\u011funu, daha geni\u015f bir bak\u0131\u015f a\u00e7\u0131s\u0131ndan <a href=\"https:\/\/www.dchost.com\/blog\/object-storage-vs-block-storage-vs-file-storage-web-uygulamalari\/\">Object Storage vs Block Storage vs File Storage rehberimizde<\/a> detayl\u0131ca anlatm\u0131\u015ft\u0131k. Burada do\u011frudan log \u00f6zelinde mimariye odaklanal\u0131m.<\/p>\n<h3><span id=\"Hedef_mimari\">Hedef mimari<\/span><\/h3>\n<ul>\n<li>cPanel sunucu veya VPS \u00fczerinde loglar g\u00fcnl\u00fck olarak rotate edilip gzip ile s\u0131k\u0131\u015ft\u0131r\u0131l\u0131r.<\/li>\n<li>Her gece (\u00f6rne\u011fin 03:00\u2019te) s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f loglar, rclone benzeri bir ara\u00e7la S3 uyumlu object storage\u2019a senkronize edilir.<\/li>\n<li>Bucket i\u00e7inde <code>proje-adi\/logs\/&lt;sunucu-ad\u0131&gt;\/&lt;y\u0131l&gt;\/&lt;ay&gt;\/&lt;g\u00fcn&gt;<\/code> gibi anlaml\u0131 klas\u00f6r hiyerar\u015fisi kullan\u0131l\u0131r.<\/li>\n<li>Object storage taraf\u0131nda <strong>Lifecycle Policy<\/strong> ile loglar belirli bir s\u00fcreden sonra so\u011fuk depolamaya ta\u015f\u0131n\u0131r veya tamamen silinir.<\/li>\n<\/ul>\n<h3><span id=\"rclone_ile_log_offload_ornegi\">rclone ile log offload \u00f6rne\u011fi<\/span><\/h3>\n<p>rclone ile object storage\u2019a otomatik yedek alma konusunu, uygulamal\u0131 olarak <a href=\"https:\/\/www.dchost.com\/blog\/object-storagea-otomatik-yedek-alma-rclone-restic-ve-cron-ile-cpanel-vps-yedekleri\/\">object storage\u2019a otomatik yedek alma rehberimizde<\/a> ayr\u0131nt\u0131l\u0131 anlatt\u0131k. Ayn\u0131 yakla\u015f\u0131m\u0131 log dosyalar\u0131n\u0131z i\u00e7in de kullanabilirsiniz.<\/p>\n<ol>\n<li><strong>rclone remote tan\u0131m\u0131<\/strong><br \/>\u00d6rne\u011fin <code>logs<\/code> ad\u0131nda bir remote:<\/li>\n<\/ol>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">rclone config\n# Yeni remote ekleyin, tip olarak S3 uyumlu depolamay\u0131 se\u00e7in,\n# DCHost taraf\u0131nda size verilen eri\u015fim anahtarlar\u0131n\u0131 girin.\n<\/code><\/pre>\n<ol start=\"2\">\n<li><strong>Senkranizasyon komutu<\/strong><br \/>cPanel veya VPS \u00fczerinde, s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f loglar\u0131 senkronize etmek i\u00e7in:<\/li>\n<\/ol>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">rclone sync \n  \/var\/log\/nginx\/ \n  logs:proje-1\/logs\/web01\/nginx\/ \n  --include &quot;*.gz&quot; \n  --max-age 30d \n  --transfers=4 --checkers=8\n<\/code><\/pre>\n<p>Burada:<\/p>\n<ul>\n<li><strong>&#8211;include &#8220;*.gz&#8221;<\/strong> sadece gzip\u2019lenmi\u015f dosyalar\u0131 ta\u015f\u0131r.<\/li>\n<li><strong>&#8211;max-age 30d<\/strong> son 30 g\u00fcnden eski dosyalar\u0131 senkronizasyon d\u0131\u015f\u0131nda b\u0131rak\u0131r; b\u00f6ylece gereksiz listeleme maliyetlerini azalt\u0131rs\u0131n\u0131z.<\/li>\n<\/ul>\n<h3><span id=\"Cron_ile_otomasyon\">Cron ile otomasyon<\/span><\/h3>\n<p>Her gece saat 03:15\u2019te log offload \u00e7al\u0131\u015ft\u0131rmak i\u00e7in basit bir cron girdisi yeterlidir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">15 3 * * * root \/usr\/local\/bin\/rclone sync \n    \/var\/log\/nginx\/ \n    logs:proje-1\/logs\/web01\/nginx\/ \n    --include &quot;*.gz&quot; --max-age 30d \n    --log-file \/var\/log\/rclone-logs-sync.log --log-level INFO\n<\/code><\/pre>\n<p>Ayn\u0131 yap\u0131y\u0131 Apache, mail ve uygulama loglar\u0131 i\u00e7in farkl\u0131 klas\u00f6rlerle \u00e7o\u011faltabilirsiniz. Kritik nokta, <strong>bucket i\u00e7inde okunabilir bir klas\u00f6r yap\u0131s\u0131<\/strong> kurmak ve her sunucuyu\/uygulamay\u0131 ay\u0131rt edilebilir hale getirmektir.<\/p>\n<h3><span id=\"Guvenlik_ve_erisim_kontrolleri\">G\u00fcvenlik ve eri\u015fim kontrolleri<\/span><\/h3>\n<ul>\n<li>Object storage eri\u015fim anahtarlar\u0131n\u0131 yaln\u0131zca log sync i\u015flemi i\u00e7in \u00f6zel bir kullan\u0131c\u0131yla s\u0131n\u0131rlay\u0131n.<\/li>\n<li>M\u00fcmk\u00fcnse bucket d\u00fczeyinde <strong>salt okunur<\/strong> ve <strong>salt yaz\u0131labilir<\/strong> ayr\u0131 politika tan\u0131mlay\u0131n.<\/li>\n<li>Ta\u015f\u0131ma s\u0131ras\u0131nda TLS kullan\u0131n; DCHost object storage u\u00e7 noktalar\u0131m\u0131zda HTTPS zorunludur.<\/li>\n<li>Bucket i\u00e7inde KVKK hassasiyeti olan loglar (IP adresi, e\u2011posta, kullan\u0131c\u0131 ID\u2019leri vb.) i\u00e7in <strong>\u015fifreleme<\/strong> ve <strong>eri\u015fim denetimi<\/strong> katmanlar\u0131n\u0131 daha s\u0131k\u0131 kurgulay\u0131n.<\/li>\n<\/ul>\n<h2><span id=\"Saklama_Suresi_Politikalari_Operasyon_Guvenlik_ve_KVKK_Dengesi\">Saklama S\u00fcresi Politikalar\u0131: Operasyon, G\u00fcvenlik ve KVKK Dengesi<\/span><\/h2>\n<p>Loglar\u0131 nereye koyaca\u011f\u0131n\u0131z\u0131 \u00e7\u00f6zmek tek ba\u015f\u0131na yeterli de\u011fil; as\u0131l kritik konu, <strong>ne kadar s\u00fcre saklayaca\u011f\u0131n\u0131z\u0131<\/strong> tan\u0131mlayan politika. Bu konuda daha genel \u00e7er\u00e7eveyi, <a href=\"https:\/\/www.dchost.com\/blog\/yedek-saklama-suresi-nasil-belirlenir-kvkk-gdpr-ve-maliyet-dengesi\/\">yedek saklama s\u00fcresi ve KVKK\/GDPR dengesini anlatt\u0131\u011f\u0131m\u0131z rehberde<\/a> ele alm\u0131\u015ft\u0131k. Log \u00f6zelinde ise biraz daha farkl\u0131 n\u00fcanslar var.<\/p>\n<h3><span id=\"Log_turune_gore_onerilen_saklama_seviyeleri\">Log t\u00fcr\u00fcne g\u00f6re \u00f6nerilen saklama seviyeleri<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki s\u00fcreler, sahada g\u00f6rd\u00fc\u011f\u00fcm\u00fcz makul de\u011ferlerdir; elbette sekt\u00f6r\u00fcn\u00fczdeki yasal gereksinimleri ayr\u0131ca kontrol etmelisiniz.<\/p>\n<ul>\n<li><strong>Web eri\u015fim loglar\u0131 (Apache\/Nginx)<\/strong>\n<ul>\n<li><strong>Lokal disk (s\u0131cak veri):<\/strong> 7\u201330 g\u00fcn<\/li>\n<li><strong>Object storage (s\u0131cak\/\u0131l\u0131k):<\/strong> 6\u201312 ay<\/li>\n<li><strong>So\u011fuk ar\u015fiv (gerekiyorsa):<\/strong> 1\u20132 y\u0131l<\/li>\n<\/ul>\n<\/li>\n<li><strong>G\u00fcvenlik ve sistem loglar\u0131 (ssh, sudo, firewall, cPHulk vb.)<\/strong>\n<ul>\n<li><strong>Lokal disk:<\/strong> 30\u201390 g\u00fcn<\/li>\n<li><strong>Object storage:<\/strong> 1\u20133 y\u0131l (siber olay incelemesi i\u00e7in)<\/li>\n<\/ul>\n<\/li>\n<li><strong>Mail loglar\u0131<\/strong>\n<ul>\n<li><strong>Lokal disk:<\/strong> 30\u201390 g\u00fcn<\/li>\n<li><strong>Object storage:<\/strong> 1\u20132 y\u0131l (kurumsal uyumluluk ihtiya\u00e7lar\u0131na g\u00f6re)<\/li>\n<\/ul>\n<\/li>\n<li><strong>Uygulama loglar\u0131 (Laravel, Node.js vb.)<\/strong>\n<ul>\n<li><strong>Lokal disk:<\/strong> 7\u201330 g\u00fcn<\/li>\n<li><strong>Object storage:<\/strong> 6\u201312 ay (hata analizi ve audit trail i\u00e7in)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Bu s\u00fcreler, <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\u0131zda anlatt\u0131\u011f\u0131m\u0131z prensiplerle uyumlu olacak \u015fekilde se\u00e7ilmi\u015ftir: Ne gere\u011finden k\u0131sa, ne de gereksiz yere uzun.<\/p>\n<h3><span id=\"Object_storage_tarafinda_Lifecycle_Policy_kullanimi\">Object storage taraf\u0131nda Lifecycle Policy kullan\u0131m\u0131<\/span><\/h3>\n<p>\u00c7o\u011fu S3 uyumlu depolama sisteminde bucket bazl\u0131 <strong>Lifecycle Policy<\/strong> tan\u0131mlayabilirsiniz. \u00d6rne\u011fin:<\/p>\n<ul>\n<li><strong>0\u201330 g\u00fcn:<\/strong> S\u0131cak depolama (standart klasmanda; s\u0131k sorgulanan loglar)<\/li>\n<li><strong>30\u2013365 g\u00fcn:<\/strong> Infrequent Access \/ Warm tier (daha d\u00fc\u015f\u00fck maliyetli, nadiren eri\u015filen loglar)<\/li>\n<li><strong>365+ g\u00fcn:<\/strong> Tamamen sil (veya \u00e7ok so\u011fuk ar\u015fiv s\u0131n\u0131f\u0131na ta\u015f\u0131)<\/li>\n<\/ul>\n<p>B\u00f6ylece, DCHost \u00fczerindeki VPS veya cPanel sunucunuzdan sadece <strong>g\u00fcnl\u00fck senkronizasyonu<\/strong> y\u00f6netirsiniz; hangi dosyan\u0131n ne zaman daha ucuz depoya ta\u015f\u0131naca\u011f\u0131n\u0131 ve ne zaman silinece\u011fini object storage otomatik halleder.<\/p>\n<h3><span id=\"KVKKGDPR_boyutu_ve_anonimlestirme\">KVKK\/GDPR boyutu ve anonimle\u015ftirme<\/span><\/h3>\n<p>IP adresleri, kullan\u0131c\u0131 ajanlar\u0131, cookie de\u011ferleri, e\u2011posta adresleri gibi bilgiler loglarda yer ald\u0131\u011f\u0131nda, bu kay\u0131tlar ki\u015fisel veri kapsam\u0131na girebilir. Bu noktada sadece saklama s\u00fcresi de\u011fil, <strong>maskeleme\/anomimle\u015ftirme<\/strong> stratejisi de devreye giriyor. Bu konuyu teknik \u00f6rneklerle anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/kvkk-ve-gdpr-icin-log-anonimlestirme-ip-maskeleme-ve-pseudonymization\/\">KVKK ve GDPR i\u00e7in log anonimle\u015ftirme rehberimizi<\/a> mutlaka incelemenizi tavsiye ederim.<\/p>\n<h2><span id=\"cPanelde_Uygulanabilir_Log_Arsivleme_Senaryosu_Adim_Adim\">cPanel\u2019de Uygulanabilir Log Ar\u015fivleme Senaryosu (Ad\u0131m Ad\u0131m)<\/span><\/h2>\n<p>\u015eimdi t\u00fcm bu par\u00e7alar\u0131 birle\u015ftirip, tek bir cPanel sunucusu i\u00e7in <strong>somut bir senaryo<\/strong> \u00fczerinden ilerleyelim. Varsayal\u0131m ki DCHost \u00fczerinde bir cPanel sunucunuz var ve \u00fczerinde 50 civar\u0131 site bar\u0131nd\u0131r\u0131yorsunuz.<\/p>\n<h3><span id=\"1_Envanter_ve_hedefler\">1. Envanter ve hedefler<\/span><\/h3>\n<ul>\n<li>Hangi loglar\u0131n kritik oldu\u011funu belirleyin: Apache eri\u015fim\/hata, Exim, Dovecot, cPHulk, sistem loglar\u0131, PHP error_log vb.<\/li>\n<li>Hangi loglar i\u00e7in <strong>analiz s\u00fcresi<\/strong> (\u00f6r. 30 g\u00fcn detayl\u0131 analiz), hangileri i\u00e7in <strong>hukuki ispat s\u00fcresi<\/strong> (\u00f6r. 1\u20132 y\u0131l) gerekece\u011fini netle\u015ftirin.<\/li>\n<\/ul>\n<h3><span id=\"2_WHM_log_ayarlarini_guncelleyin\">2. WHM log ayarlar\u0131n\u0131 g\u00fcncelleyin<\/span><\/h3>\n<ul>\n<li><strong>Archive logs in \/usr\/local\/apache\/domlogs too?<\/strong> se\u00e7ene\u011fini aktif edin; b\u00f6ylece domlogs alt\u0131nda ar\u015fivli eri\u015fim loglar\u0131n\u0131z olacak.<\/li>\n<li><strong>Keep log files at least<\/strong> alan\u0131n\u0131 \u00f6rne\u011fin <strong>14 g\u00fcn<\/strong> yap\u0131n; b\u00f6ylece en az\u0131ndan iki haftal\u0131k lokal eri\u015fim logunuz garanti alt\u0131na al\u0131nm\u0131\u015f olur.<\/li>\n<\/ul>\n<h3><span id=\"3_logrotate_yapilarini_gozden_gecirin\">3. logrotate yap\u0131lar\u0131n\u0131 g\u00f6zden ge\u00e7irin<\/span><\/h3>\n<p><code>\/etc\/logrotate.d\/<\/code> alt\u0131ndaki <code>httpd<\/code>, <code>exim<\/code>, <code>cpanel<\/code> ve di\u011fer logrotate dosyalar\u0131n\u0131 inceleyin. Gerekirse:<\/p>\n<ul>\n<li>Rotasyon s\u0131kl\u0131\u011f\u0131n\u0131 <strong>haftal\u0131k yerine g\u00fcnl\u00fck<\/strong> yap\u0131n.<\/li>\n<li><strong>rotate<\/strong> de\u011ferini 7\u201314 aras\u0131na \u00e7ekerek lokal disk tutma s\u00fcresini s\u0131n\u0131rlay\u0131n.<\/li>\n<li><strong>compress<\/strong> ve <strong>delaycompress<\/strong> se\u00e7eneklerinin aktif oldu\u011fundan emin olun.<\/li>\n<\/ul>\n<h3><span id=\"4_rclone_ile_object_storage_senkronizasyonu_kurun\">4. rclone ile object storage senkronizasyonu kurun<\/span><\/h3>\n<ol>\n<li>DCHost object storage hesab\u0131n\u0131z\u0131 olu\u015fturun ve eri\u015fim anahtarlar\u0131n\u0131 al\u0131n.<\/li>\n<li>cPanel sunucusuna rclone kurun ve <code>logs<\/code> ad\u0131nda bir remote tan\u0131mlay\u0131n.<\/li>\n<li>A\u015fa\u011f\u0131daki gibi bir senkronizasyon script\u2019i yaz\u0131n:<\/li>\n<\/ol>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">#!\/bin\/bash\nset -e\n\nHOSTNAME=$(hostname -s)\nDATE=$(date +%Y\/%m\/%d)\n\n# Apache domlogs\nrclone sync \n  \/usr\/local\/apache\/domlogs\/ \n  logs:cpanel-logs\/${HOSTNAME}\/apache\/${DATE}\/ \n  --include &quot;*.gz&quot; --ignore-existing\n\n# Exim mail loglar\u0131\nrclone sync \n  \/var\/log\/ \n  logs:cpanel-logs\/${HOSTNAME}\/mail\/${DATE}\/ \n  --include &quot;exim*gz&quot; --ignore-existing\n<\/code><\/pre>\n<p>Bu script\u2019i \u00f6rne\u011fin <code>\/usr\/local\/sbin\/log-offload.sh<\/code> olarak kaydedip, \u00e7al\u0131\u015ft\u0131r\u0131labilir yap\u0131n.<\/p>\n<h3><span id=\"5_Cron_ile_zamanlama_ve_lokal_temizlik\">5. Cron ile zamanlama ve lokal temizlik<\/span><\/h3>\n<p>Her gece saat 03:30\u2019da offload script\u2019ini \u00e7al\u0131\u015ft\u0131r\u0131n ve 30 g\u00fcnden eski lokal gzip loglar\u0131n\u0131 silin:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">30 3 * * * root \/usr\/local\/sbin\/log-offload.sh &gt;&gt; \/var\/log\/log-offload.log 2&gt;&amp;1\n45 3 * * * root find \/usr\/local\/apache\/domlogs\/ -name &quot;*.gz&quot; -mtime +30 -delete\n<\/code><\/pre>\n<p>B\u00f6ylece:<\/p>\n<ul>\n<li>cPanel sunucunuzda <strong>son 30 g\u00fcnl\u00fck s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f loglar<\/strong> kal\u0131r.<\/li>\n<li>Daha eski t\u00fcm loglar, DCHost object storage \u00fczerinde, Lifecycle Policy ile y\u00f6netilen d\u00fc\u015f\u00fck maliyetli depoda tutulur.<\/li>\n<\/ul>\n<h3><span id=\"6_Geri_donus_restore_senaryosunu_test_edin\">6. Geri d\u00f6n\u00fc\u015f (restore) senaryosunu test edin<\/span><\/h3>\n<p>Ar\u015fivleme stratejisi, geri d\u00f6n\u00fc\u015f\u00fc test edilmemi\u015fse tamamlanm\u0131\u015f say\u0131lmaz. Rastgele bir tarihteki log dosyas\u0131n\u0131 object storage\u2019tan indirip a\u00e7arak; hem eri\u015fim yetkilerinizin do\u011fru oldu\u011funu, hem de s\u0131k\u0131\u015ft\u0131rman\u0131n\/verinin bozulmad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n<h2><span id=\"VPSte_Gelismis_Log_Arsivleme_Merkezi_ve_Cok_Sunuculu_Yapilar\">VPS\u2019te Geli\u015fmi\u015f Log Ar\u015fivleme: Merkezi ve \u00c7ok Sunuculu Yap\u0131lar<\/span><\/h2>\n<p>Birden fazla VPS y\u00f6netti\u011finizde, log ar\u015fivlemeyi sadece tek sunucu \u00f6zelinde d\u00fc\u015f\u00fcnmek yerine <strong>merkezi bir mimari<\/strong>ye ta\u015f\u0131mak b\u00fcy\u00fck avantaj sa\u011flar. DCHost blogunda bunu iki farkl\u0131 boyutuyla anlatt\u0131k:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.dchost.com\/blog\/birden-fazla-sunucuda-log-yonetimi-elk-ve-loki-stack-ile-merkezi-hosting-loglama\/\">ELK ve Loki stack ile merkezi hosting loglama<\/a><\/li>\n<li><a href=\"https:\/\/www.dchost.com\/blog\/vps-log-yonetimi-nasil-rayina-oturur-grafana-loki-promtail-ile-merkezi\/\">Grafana Loki + Promtail ile VPS log y\u00f6netimi<\/a><\/li>\n<\/ul>\n<p>Merkezi loglama ile object storage ar\u015fivini birlikte kulland\u0131\u011f\u0131n\u0131zda ortaya \u015fu mimari \u00e7\u0131kar:<\/p>\n<ol>\n<li>Her VPS, Promtail\/beat\/agent arac\u0131l\u0131\u011f\u0131yla loglar\u0131 ger\u00e7ek zamanl\u0131 olarak merkezi Loki veya Elasticsearch k\u00fcmesine g\u00f6nderir.<\/li>\n<li>Merkezi sistemde <strong>k\u0131sa vadeli saklama<\/strong> (\u00f6r. 7\u201330 g\u00fcn) ve geli\u015fmi\u015f sorgulama\/alarmlar kurulur.<\/li>\n<li>Ayn\u0131 loglar e\u015f zamanl\u0131 veya periyodik olarak <strong>S3 uyumlu object storage\u2019a s\u0131k\u0131\u015ft\u0131r\u0131lm\u0131\u015f ar\u015fiv<\/strong> olarak yaz\u0131l\u0131r.<\/li>\n<li>Merkezi sistemde tutma s\u00fcresi dolan veriler silinir; ancak object storage\u2019taki uzun vadeli ar\u015fivler Lifecycle Policy ile y\u00f6netilmeye devam eder.<\/li>\n<\/ol>\n<p>B\u00f6ylece:<\/p>\n<ul>\n<li>Operasyon ekibiniz, son g\u00fcnlerin loglar\u0131n\u0131 h\u0131zl\u0131 ve etkile\u015fimli bir aray\u00fcz \u00fczerinden inceler.<\/li>\n<li>Uyumluluk ve inceleme ihtiya\u00e7lar\u0131 i\u00e7in y\u0131llara yay\u0131lan ar\u015fiv, d\u00fc\u015f\u00fck maliyetli object storage \u00fczerinde ya\u015far.<\/li>\n<\/ul>\n<h2><span id=\"Sik_Yapilan_Hatalar_ve_DCHost_Tarafinda_Onerdigimiz_Ipuclari\">S\u0131k Yap\u0131lan Hatalar ve DCHost Taraf\u0131nda \u00d6nerdi\u011fimiz \u0130pu\u00e7lar\u0131<\/span><\/h2>\n<p>Sahada en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar\u0131 ve bunlara kar\u015f\u0131 \u00f6nerilerimizi k\u0131saca derleyelim:<\/p>\n<ul>\n<li><strong>Hata:<\/strong> Sadece varsay\u0131lan logrotate\u2019e g\u00fcvenmek.<br \/><strong>\u00c7\u00f6z\u00fcm:<\/strong> Custom uygulama loglar\u0131n\u0131 da logrotate\u2019e dahil etti\u011finizden ve gzip\u2019in a\u00e7\u0131k oldu\u011fundan emin olun.<\/li>\n<li><strong>Hata:<\/strong> T\u00fcm loglar\u0131 NVMe disk \u00fczerinde y\u0131llarca tutmaya \u00e7al\u0131\u015fmak.<br \/><strong>\u00c7\u00f6z\u00fcm:<\/strong> cPanel\/VPS diskini sadece k\u0131sa vadeli loglar i\u00e7in kullan\u0131n, uzun vadeyi mutlaka object storage\u2019a offload edin.<\/li>\n<li><strong>Hata:<\/strong> KVKK kapsam\u0131ndaki verileri s\u00fcresiz saklamak.<br \/><strong>\u00c7\u00f6z\u00fcm:<\/strong> Log saklama s\u00fcrelerini i\u015f amac\u0131yla orant\u0131l\u0131 belirleyin, gerekirse IP maskeleme ve anonimle\u015ftirme uygulay\u0131n.<\/li>\n<li><strong>Hata:<\/strong> Yedek\/alarm kurup geri d\u00f6n\u00fc\u015f testini hi\u00e7 yapmamak.<br \/><strong>\u00c7\u00f6z\u00fcm:<\/strong> En az\u0131ndan 3 ayda bir, rastgele bir g\u00fcn\u00fcn loglar\u0131n\u0131 object storage\u2019tan indirip a\u00e7arak test edin.<\/li>\n<li><strong>Hata:<\/strong> Loglar\u0131 tek kopya ve tek lokasyonla s\u0131n\u0131rlamak.<br \/><strong>\u00c7\u00f6z\u00fcm:<\/strong> Kritik loglar i\u00e7in 3\u20112\u20111 prensibiyle en az bir kopyay\u0131 farkl\u0131 depolama t\u00fcr\u00fcnde (\u00f6rne\u011fin object storage) tutun.<\/li>\n<\/ul>\n<p>Daha geni\u015f resimde, KVKK\/GDPR uyumlulu\u011fu, log saklama ve anonimle\u015ftirme konular\u0131n\u0131 birlikte ele almak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/kvkk-ve-gdpr-uyumlu-hosting-secimi-turkiye-avrupa-ve-abd-veri\/\">KVKK ve GDPR uyumlu hosting stratejisi rehberimizi<\/a> de inceleyebilirsiniz.<\/p>\n<h2><span id=\"Sonuc_ve_DCHost_ile_Yol_Haritanizi_Netlestirin\">Sonu\u00e7 ve DCHost ile Yol Haritan\u0131z\u0131 Netle\u015ftirin<\/span><\/h2>\n<p>cPanel ve VPS ortamlar\u0131nda log ar\u015fivleme, \u201cdisk dolmas\u0131n\u201d diye yap\u0131lan basit bir temizlik i\u015fi de\u011fildir. Do\u011fru kurguland\u0131\u011f\u0131nda; performans sorunlar\u0131n\u0131 h\u0131zla te\u015fhis etmenize, g\u00fcvenlik olaylar\u0131n\u0131 geriye d\u00f6n\u00fck olarak detayl\u0131 incelemenize, e\u2011posta ve \u00f6deme hatalar\u0131n\u0131 somut verilerle kan\u0131tlaman\u0131za ve en \u00f6nemlisi, KVKK\/GDPR taraf\u0131nda denetime haz\u0131r bir pozisyonda olman\u0131za yard\u0131mc\u0131 olur.<\/p>\n<p>Bu yaz\u0131da, gzip ile s\u0131k\u0131\u015ft\u0131rma, S3 uyumlu object storage\u2019a offload ve saklama s\u00fcresi politikalar\u0131n\u0131 bir arada ele alan uygulanabilir bir \u00e7er\u00e7eve \u00e7izdik. S\u0131radaki ad\u0131m, kendi altyap\u0131n\u0131za bak\u0131p \u015fu \u00fc\u00e7 soruyu sormakt\u0131r:<\/p>\n<ul>\n<li>Hangi loglar\u0131 nerede ve ne kadar s\u00fcre sakl\u0131yorum?<\/li>\n<li>Disk doldu\u011funda veya inceleme talebi geldi\u011finde elimde hangi kan\u0131tlar olacak?<\/li>\n<li>Bu yap\u0131y\u0131 nas\u0131l otomatikle\u015ftirip, geri d\u00f6n\u00fc\u015f\u00fcn\u00fc nas\u0131l test edece\u011fim?<\/li>\n<\/ul>\n<p>E\u011fer bu sorular\u0131n cevab\u0131 hen\u00fcz net de\u011filse, DCHost olarak hem <strong>cPanel hosting<\/strong> hem de <strong>VPS\/<a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a><\/strong> m\u00fc\u015fterilerimiz i\u00e7in log ar\u015fivleme stratejisini birlikte tasarlamaktan memnuniyet duyar\u0131z. Mevcut sunucunuzu bize ta\u015f\u0131yor olun veya s\u0131f\u0131rdan bir altyap\u0131 planl\u0131yor olun; DCHost\u2019un S3 uyumlu object storage \u00e7\u00f6z\u00fcmleri, merkezi loglama mimarileri ve yedekleme stratejileriyle, loglar\u0131n\u0131z\u0131 hem <strong>\u00f6l\u00e7eklenebilir<\/strong> hem de <strong>uyumlu<\/strong> bir yap\u0131ya ta\u015f\u0131yabilirsiniz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Neden cPanel ve VPS\u2019te Log Ar\u015fivleme Stratejisi \u015eart? Loglar, bir sunucunun kara kutusudur: Performans sorunlar\u0131n\u0131, g\u00fcvenlik ihlallerini, e\u2011posta teslim problemlerini ve uygulama hatalar\u0131n\u0131 geriye d\u00f6n\u00fck olarak analiz etmenin tek somut kayna\u011f\u0131d\u0131r. Ancak plans\u0131z loglama, birka\u00e7 ay i\u00e7inde diski dolduran, arand\u0131\u011f\u0131nda bulunamayan ve KVKK\/GDPR taraf\u0131nda ba\u015f\u0131n\u0131z\u0131 a\u011fr\u0131tabilecek bir veri y\u0131\u011f\u0131n\u0131na d\u00f6n\u00fc\u015f\u00fcr. \u00d6zellikle cPanel kullanan payla\u015f\u0131ml\u0131 hosting [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4729,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4728","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\/4728","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=4728"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4728\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4729"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4728"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4728"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4728"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}