{"id":31219,"date":"2025-10-07T09:41:16","date_gmt":"2025-10-07T06:41:16","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=31219"},"modified":"2025-10-07T09:41:16","modified_gmt":"2025-10-07T06:41:16","slug":"javada-loglama-kapsamli-bir-bakis-ve-ornekler","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/","title":{"rendered":"Java’da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler"},"content":{"rendered":"

<\/p>\n

Java’da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler<\/h2>\n

Java uygulamalar\u0131 geli\u015ftirirken, kodun do\u011fru \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak, hatalar\u0131 tespit etmek ve uygulaman\u0131n davran\u0131\u015f\u0131n\u0131 anlamak kritik \u00f6neme sahiptir. Bu noktada “loglama” devreye girer. Loglama, bir uygulaman\u0131n \u00e7al\u0131\u015fma zaman\u0131nda belirli olaylar\u0131, durumlar\u0131 veya hata mesajlar\u0131n\u0131 kaydederek, geli\u015ftiricilere ve sistem y\u00f6neticilerine de\u011ferli i\u00e7g\u00f6r\u00fcler sunan bir mekanizmad\u0131r. Bu makalede, Java’da loglaman\u0131n neden bu kadar \u00f6nemli oldu\u011funu, yerle\u015fik loglama API’si java.util.logging<\/code>‘i, pop\u00fcler \u00fc\u00e7\u00fcnc\u00fc parti loglama \u00e7er\u00e7evelerini (Log4j, Logback, SLF4J) ve iyi loglama pratiklerini detayl\u0131 \u00f6rneklerle inceleyece\u011fiz.<\/p>\n

Giri\u015f: Loglama Neden \u00d6nemli?<\/h3>\n

Yaz\u0131l\u0131m geli\u015ftirme s\u00fcrecinde loglama, sadece hata ay\u0131klama arac\u0131 olmaktan \u00e7ok daha fazlas\u0131d\u0131r. Modern, karma\u015f\u0131k ve da\u011f\u0131t\u0131k sistemlerde loglar, uygulaman\u0131n “kara kutusunu” a\u00e7an bir pencere g\u00f6revi g\u00f6r\u00fcr. Loglaman\u0131n ba\u015fl\u0131ca faydalar\u0131 \u015funlard\u0131r:<\/p>\n

* Hata Ay\u0131klama (Debugging):<\/strong> Uygulama \u00e7\u00f6kt\u00fc\u011f\u00fcnde veya beklenmedik bir davran\u0131\u015f sergiledi\u011finde, loglar hatan\u0131n k\u00f6k nedenini bulmak i\u00e7in izlenebilecek bir “ekmek k\u0131r\u0131nt\u0131s\u0131” yolu sunar. Hata mesajlar\u0131, stack trace’ler ve de\u011fi\u015fken de\u011ferleri loglara kaydedilerek sorun tespiti kolayla\u015f\u0131r.
\n* Uygulama Takibi ve Performans \u0130zleme:<\/strong> Loglar, uygulaman\u0131n hangi i\u015flemlerden ge\u00e7ti\u011fini, ne kadar s\u00fcrd\u00fc\u011f\u00fcn\u00fc ve hangi kaynaklar\u0131 kulland\u0131\u011f\u0131n\u0131 g\u00f6sterir. Bu bilgiler, performans darbo\u011fazlar\u0131n\u0131 tespit etmek ve kullan\u0131c\u0131 deneyimini iyile\u015ftirmek i\u00e7in kullan\u0131labilir.
\n* G\u00fcvenlik Denetimi (Auditing):<\/strong> Kullan\u0131c\u0131 giri\u015fleri, hassas veri eri\u015fimleri, yetkilendirme denemeleri gibi g\u00fcvenlik a\u00e7\u0131s\u0131ndan \u00f6nemli olaylar loglanarak, olas\u0131 g\u00fcvenlik ihlallerinin tespiti ve analizi sa\u011flan\u0131r.
\n* \u0130\u015f S\u00fcreci \u0130zleme:<\/strong> Uygulama i\u00e7indeki belirli i\u015f ak\u0131\u015flar\u0131n\u0131n ba\u015far\u0131l\u0131 olup olmad\u0131\u011f\u0131n\u0131, hangi a\u015famada tak\u0131ld\u0131\u011f\u0131n\u0131 veya ka\u00e7 i\u015flem ger\u00e7ekle\u015ftirdi\u011fini loglar arac\u0131l\u0131\u011f\u0131yla takip edebiliriz. Bu, i\u015f operasyonlar\u0131n\u0131n izlenmesi ve raporlanmas\u0131 i\u00e7in \u00f6nemlidir.
\n* Sistem Entegrasyonu:<\/strong> Da\u011f\u0131t\u0131k sistemlerde farkl\u0131 servisler aras\u0131ndaki etkile\u015fimleri loglamak, entegrasyon sorunlar\u0131n\u0131 anlamak ve gidermek i\u00e7in vazge\u00e7ilmezdir.<\/p>\n

System.out.println()<\/code> kullanmak yerine ger\u00e7ek bir loglama mekanizmas\u0131 kullanmak, bu faydalar\u0131 sa\u011flaman\u0131n tek yoludur. System.out.println()<\/code>, \u00e7\u0131kt\u0131y\u0131 kontrol etme, filtreleme, farkl\u0131 hedeflere y\u00f6nlendirme veya formatlama gibi esneklikler sunmaz ve \u00fcretim ortamlar\u0131nda ciddi performans sorunlar\u0131na yol a\u00e7abilir.<\/p>\n

Java’da Temel Loglama Mekanizmalar\u0131<\/h3>\n

Java ekosisteminde birden fazla loglama se\u00e7ene\u011fi bulunmaktad\u0131r. Bunlar\u0131n en temel olan\u0131, Java’n\u0131n kendi b\u00fcnyesinde gelen java.util.logging<\/code> (JUL) API’sidir.<\/p>\n

java.util.logging (JUL)<\/h4>\n

java.util.logging<\/code>, Java SE platformunun bir par\u00e7as\u0131d\u0131r ve herhangi bir harici ba\u011f\u0131ml\u0131l\u0131k olmadan kullan\u0131labilir. Daha basit uygulamalar veya h\u0131zl\u0131 prototipleme i\u00e7in uygun olabilir.<\/p>\n

JUL Temel Bile\u015fenleri<\/h5>\n

* Logger<\/code>:<\/strong> Loglama mesajlar\u0131n\u0131 olu\u015fturan ana nesnedir. Belirli bir isimle (genellikle s\u0131n\u0131f\u0131n tam nitelikli ad\u0131) al\u0131n\u0131r.
\n* Level<\/code>:<\/strong> Loglama mesaj\u0131n\u0131n \u00f6nem derecesini belirtir. \u00d6n tan\u0131ml\u0131 seviyeler \u015funlard\u0131r: SEVERE<\/code> (ciddi hata), WARNING<\/code> (uyar\u0131), INFO<\/code> (bilgilendirme), CONFIG<\/code> (yap\u0131land\u0131rma), FINE<\/code> (detayl\u0131 hata ay\u0131klama), FINER<\/code>, FINEST<\/code> (en detayl\u0131 hata ay\u0131klama). Ayr\u0131ca ALL<\/code> (t\u00fcm mesajlar) ve OFF<\/code> (hi\u00e7bir mesaj) seviyeleri de bulunur.
\n* Handler<\/code>:<\/strong> Log mesajlar\u0131n\u0131 belirli bir hedefe (konsol, dosya, a\u011f, veritaban\u0131 vb.) yazmaktan sorumludur. \u00d6rne\u011fin, ConsoleHandler<\/code> konsola yazar, FileHandler<\/code> dosyalara yazar.
\n* Formatter<\/code>:<\/strong> Log mesajlar\u0131n\u0131n nas\u0131l bi\u00e7imlendirilece\u011fini belirler. \u00d6rne\u011fin, SimpleFormatter<\/code> basit metin \u00e7\u0131kt\u0131s\u0131 sa\u011flarken, XMLFormatter<\/code> XML format\u0131nda \u00e7\u0131kt\u0131 verir.<\/p>\n

JUL Kullan\u0131m \u00d6rne\u011fi<\/h5>\n
import java.util.logging.ConsoleHandler;\nimport java.util.logging.FileHandler;\nimport java.util.logging.Formatter;\nimport java.util.logging.Level;\nimport java.util.logging.LogRecord;\nimport java.util.logging.Logger;\nimport java.util.logging.SimpleFormatter;\nimport java.io.IOException;\n\npublic class JulLoggerExample {\n\n    private static final Logger logger = Logger.getLogger(JulLoggerExample.class.getName());\n\n    public static void main(String[] args) {\n        \/\/ Varsay\u0131lan olarak INFO seviyesindeki mesajlar loglan\u0131r.\n        \/\/ T\u00fcm mesajlar\u0131 g\u00f6rmek i\u00e7in seviyeyi de\u011fi\u015ftirebiliriz.\n        logger.setLevel(Level.ALL);\n\n        \/\/ Konsola log yazmak i\u00e7in bir Handler ekleyelim\n        ConsoleHandler consoleHandler = new ConsoleHandler();\n        consoleHandler.setLevel(Level.ALL); \/\/ Handler'\u0131n kendi seviyesi olabilir\n        logger.addHandler(consoleHandler);\n\n        \/\/ Dosyaya log yazmak i\u00e7in bir Handler ekleyelim\n        try {\n            FileHandler fileHandler = new FileHandler(\"my_app_jul.log\", true); \/\/ true: append modunda\n            fileHandler.setLevel(Level.FINE); \/\/ Sadece FINE ve \u00fcst\u00fc seviyeleri dosyaya yaz\n            \n            \/\/ \u00d6zel bir Formatter kullanabiliriz\n            fileHandler.setFormatter(new SimpleFormatter()); \/\/ Veya kendi Formatter'\u0131m\u0131z\u0131 yazabiliriz\n            logger.addHandler(fileHandler);\n        } catch (IOException e) {\n            logger.log(Level.SEVERE, \"Dosya Handler olu\u015fturulurken hata olu\u015ftu\", e);\n        }\n        \n        \/\/ Varsay\u0131lan handler'\u0131 (genellikle console) kald\u0131rmak isteyebiliriz\n        \/\/ logger.setUseParentHandlers(false);\n\n        logger.log(Level.INFO, \"Uygulama ba\u015flat\u0131l\u0131yor...\");\n        logger.info(\"Bu bir bilgilendirme mesaj\u0131d\u0131r.\"); \/\/ logger.info() k\u0131sayolu\n\n        try {\n            int result = divide(10, 0);\n            logger.log(Level.INFO, \"B\u00f6lme sonucu: \" + result);\n        } catch (ArithmeticException e) {\n            logger.log(Level.SEVERE, \"S\u0131f\u0131ra b\u00f6lme hatas\u0131 olu\u015ftu!\", e);\n        }\n\n        logger.warning(\"Bu bir uyar\u0131 mesaj\u0131d\u0131r.\");\n        logger.fine(\"Bu detayl\u0131 bir hata ay\u0131klama mesaj\u0131d\u0131r. (Sadece seviye uygunsa g\u00f6r\u00fcn\u00fcr)\");\n        logger.log(Level.CONFIG, \"Uygulama ayarlar\u0131 y\u00fcklendi.\");\n\n        logger.log(Level.INFO, \"Uygulama kapat\u0131l\u0131yor.\");\n    }\n\n    public static int divide(int a, int b) {\n        return a \/ b;\n    }\n}<\/code><\/pre>\n
JUL Avantajlar\u0131 ve Dezavantajlar\u0131<\/h5>\n
*   Avantajlar:<\/strong> Java’n\u0131n yerle\u015fik bir par\u00e7as\u0131d\u0131r, harici ba\u011f\u0131ml\u0131l\u0131k gerektirmez. Basit kullan\u0131m senaryolar\u0131 i\u00e7in yeterlidir.
\n*   Dezavantajlar:<\/strong> Yap\u0131land\u0131rma esnekli\u011fi s\u0131n\u0131rl\u0131d\u0131r. \u00d6zellikle \u00fc\u00e7\u00fcnc\u00fc parti k\u00fct\u00fcphanelerin farkl\u0131 loglama \u00e7er\u00e7evelerini kulland\u0131\u011f\u0131 karma\u015f\u0131k uygulamalarda y\u00f6netimi zorla\u015fabilir. Performans a\u00e7\u0131s\u0131ndan Log4j veya Logback kadar optimize de\u011fildir.<\/p>\n
\u00dc\u00e7\u00fcnc\u00fc Parti Loglama \u00c7er\u00e7eveleri<\/h3>\n
JUL’nin s\u0131n\u0131rlamalar\u0131 nedeniyle, Java toplulu\u011fu daha g\u00fc\u00e7l\u00fc ve esnek loglama \u00e7\u00f6z\u00fcmleri geli\u015ftirmi\u015ftir. Bunlar\u0131n ba\u015f\u0131nda Apache Log4j ve Logback gelir. Ayr\u0131ca, bu \u00e7er\u00e7eveler aras\u0131nda bir soyutlama katman\u0131 sa\u011flayan SLF4J de yayg\u0131n olarak kullan\u0131l\u0131r.<\/p>\n
Log4j (Apache Log4j 2)<\/h4>\n
Log4j, Apache Software Foundation taraf\u0131ndan geli\u015ftirilen, Java’daki en pop\u00fcler loglama \u00e7er\u00e7evelerinden biridir. \u00d6zellikle Log4j 2, Log4j 1.x’in bir\u00e7ok sorununu gidererek daha iyi performans, esneklik ve yap\u0131land\u0131rma se\u00e7enekleri sunar.<\/p>\n
Log4j 2 Temel Bile\u015fenleri<\/h5>\n
*   Logger<\/code>:<\/strong> Log mesajlar\u0131n\u0131 olu\u015fturan ana bile\u015fen. Belirli bir isimle (genellikle s\u0131n\u0131f\u0131n tam ad\u0131) al\u0131n\u0131r.
\n*   Appender<\/code>:<\/strong> Log mesajlar\u0131n\u0131 belirli bir hedefe (konsol, dosya, veritaban\u0131, JMS kuyru\u011fu, e-posta vb.) yazmaktan sorumludur. ConsoleAppender<\/code>, FileAppender<\/code>, RollingFileAppender<\/code> en yayg\u0131n olanlar\u0131d\u0131r.
\n*   Layout<\/code>:<\/strong> Log mesajlar\u0131n\u0131n nas\u0131l bi\u00e7imlendirilece\u011fini belirler. PatternLayout<\/code> en yayg\u0131n ve g\u00fc\u00e7l\u00fc olan\u0131d\u0131r, desenler kullanarak \u00e7\u0131kt\u0131y\u0131 \u00f6zelle\u015ftirmeye olanak tan\u0131r.
\n*   Level<\/code>:<\/strong> Log mesaj\u0131n\u0131n \u00f6nem derecesini belirtir. Log4j 2 seviyeleri: OFF<\/code>, FATAL<\/code>, ERROR<\/code>, WARN<\/code>, INFO<\/code>, DEBUG<\/code>, TRACE<\/code>, ALL<\/code>.
\n*   Filter<\/code>:<\/strong> Log mesajlar\u0131n\u0131n Appender’a iletilmeden \u00f6nce filtrelenmesini sa\u011flar. Belirli bir seviyeden, desenden veya i\u00e7erikten ge\u00e7en mesajlar\u0131 filtreleyebiliriz.<\/p>\n
Log4j 2 Yap\u0131land\u0131rmas\u0131<\/h5>\n
Log4j 2 genellikle XML, YAML veya JSON dosyalar\u0131 arac\u0131l\u0131\u011f\u0131yla yap\u0131land\u0131r\u0131l\u0131r. log4j2.xml<\/code> dosyas\u0131, s\u0131n\u0131f yolunda (classpath) bulunmal\u0131d\u0131r.<\/p>\n
\n\n\n    \n        \n        \n            \n        <\/Console>\n\n        \n        \n            \n            \n                \n            <\/Policies>\n             \n        <\/RollingFile>\n    <\/Appenders>\n\n    \n        \n        \n            \n        <\/Logger>\n\n        \n        \n            \n            \n        <\/Root>\n    <\/Loggers>\n<\/Configuration><\/code><\/pre>\n
Log4j 2 Kullan\u0131m \u00d6rne\u011fi<\/h5>\n
\u00d6ncelikle Maven ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131 eklemeliyiz:<\/p>\n
\n    org.apache.logging.log4j<\/groupId>\n    log4j-api<\/artifactId>\n    2.23.1<\/version>\n<\/dependency>\n\n    org.apache.logging.log4j<\/groupId>\n    log4j-core<\/artifactId>\n    2.23.1<\/version>\n<\/dependency><\/code><\/pre>\n
import org.apache.logging.log4j.LogManager;\nimport org.apache.logging.log4j.Logger;\n\npublic class Log4j2LoggerExample {\n\n    \/\/ Logger \u00f6rne\u011fini almak i\u00e7in s\u0131n\u0131f\u0131n ad\u0131n\u0131 kullan\u0131r\u0131z\n    private static final Logger logger = LogManager.getLogger(Log4j2LoggerExample.class);\n\n    public static void main(String[] args) {\n        logger.trace(\"Bu bir TRACE mesaj\u0131d\u0131r.\");\n        logger.debug(\"Bu bir DEBUG mesaj\u0131d\u0131r.\");\n        logger.info(\"Uygulama ba\u015flat\u0131l\u0131yor...\");\n        logger.warn(\"Bu bir uyar\u0131 mesaj\u0131d\u0131r.\");\n\n        try {\n            int result = divide(10, 0);\n            logger.info(\"B\u00f6lme sonucu: \" + result);\n        } catch (ArithmeticException e) {\n            \/\/ Hata mesaj\u0131n\u0131 ve stack trace'i loglamak i\u00e7in e nesnesini do\u011frudan ge\u00e7irebiliriz\n            logger.error(\"S\u0131f\u0131ra b\u00f6lme hatas\u0131 olu\u015ftu!\", e);\n        }\n\n        logger.fatal(\"Uygulama kritik bir hata nedeniyle kapat\u0131l\u0131yor.\");\n    }\n\n    public static int divide(int a, int b) {\n        return a \/ b;\n    }\n}<\/code><\/pre>\n
Logback<\/h4>\n
Logback, Log4j’nin orijinal yazar\u0131 Ceki G\u00fclc\u00fc taraf\u0131ndan geli\u015ftirilen, Log4j 1.x’in halefi olarak tasarlanm\u0131\u015f modern bir loglama \u00e7er\u00e7evesidir. Spring Boot’un varsay\u0131lan loglama \u00e7er\u00e7evesidir. Logback, Log4j 2’ye benzer bir mimariye sahiptir ve performans, esneklik ve daha zengin \u00f6zellikler sunar.<\/p>\n
Logback Temel Bile\u015fenleri<\/h5>\n
*   Logger<\/code>:<\/strong> Log mesajlar\u0131n\u0131 olu\u015fturan ana bile\u015fen.
\n*   Appender<\/code>:<\/strong> Log mesajlar\u0131n\u0131 hedeflere (konsol, dosya, veritaban\u0131 vb.) yazan bile\u015fen. ConsoleAppender<\/code>, FileAppender<\/code>, RollingFileAppender<\/code> gibi \u00e7e\u015fitleri vard\u0131r.
\n*   Encoder<\/code>:<\/strong> Log mesajlar\u0131n\u0131n nas\u0131l bi\u00e7imlendirilece\u011fini belirler. Log4j’deki Layout<\/code> kavram\u0131na benzer. PatternLayoutEncoder<\/code> en yayg\u0131n olan\u0131d\u0131r.
\n*   Level<\/code>:<\/strong> Log mesaj\u0131n\u0131n \u00f6nem derecesini belirtir. Logback seviyeleri: TRACE<\/code>, DEBUG<\/code>, INFO<\/code>, WARN<\/code>, ERROR<\/code>.<\/p>\n
Logback Yap\u0131land\u0131rmas\u0131<\/h5>\n
Logback genellikle logback.xml<\/code> veya logback-spring.xml<\/code> (Spring Boot i\u00e7in) dosyalar\u0131 arac\u0131l\u0131\u011f\u0131yla yap\u0131land\u0131r\u0131l\u0131r. Bu dosya da s\u0131n\u0131f yolunda bulunmal\u0131d\u0131r.<\/p>\n
\n\n    \n    \n        \n            %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n<\/pattern>\n        <\/encoder>\n    <\/appender>\n\n    \n    \n        logs\/my_app_logback.log<\/file>\n        \n            \n            logs\/my_app_logback-%d{yyyy-MM-dd}.%i.log.gz<\/fileNamePattern>\n            10MB<\/maxFileSize>\n            30<\/maxHistory> \n            1GB<\/totalSizeCap> \n        <\/rollingPolicy>\n        \n            %d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n<\/pattern>\n        <\/encoder>\n    <\/appender>\n\n    \n    \n        \n    <\/logger>\n\n    \n    \n        \n        \n    <\/root>\n<\/configuration><\/code><\/pre>\n
Logback Kullan\u0131m \u00d6rne\u011fi<\/h5>\n
Maven ba\u011f\u0131ml\u0131l\u0131klar\u0131:<\/p>\n
\n    ch.qos.logback<\/groupId>\n    logback-classic<\/artifactId>\n    1.5.6<\/version>\n<\/dependency>\n<\/code><\/pre>\n
import org.slf4j.Logger;\nimport org.slf4j.LoggerFactory;\n\npublic class LogbackLoggerExample {\n\n    \/\/ SLF4J aray\u00fcz\u00fcn\u00fc kullanarak Logger'\u0131 al\u0131yoruz, arka planda Logback kullan\u0131l\u0131yor\n    private static final Logger logger = LoggerFactory.getLogger(LogbackLoggerExample.class);\n\n    public static void main(String[] args) {\n        logger.trace(\"Bu bir TRACE mesaj\u0131d\u0131r.\");\n        logger.debug(\"Bu bir DEBUG mesaj\u0131d\u0131r.\");\n        logger.info(\"Uygulama ba\u015flat\u0131l\u0131yor...\");\n        logger.warn(\"Bu bir uyar\u0131 mesaj\u0131d\u0131r.\");\n\n        try {\n            int result = divide(10, 0);\n            logger.info(\"B\u00f6lme sonucu: \" + result);\n        } catch (ArithmeticException e) {\n            logger.error(\"S\u0131f\u0131ra b\u00f6lme hatas\u0131 olu\u015ftu!\", e);\n        }\n\n        logger.error(\"Uygulama kritik bir hata nedeniyle kapat\u0131l\u0131yor.\");\n    }\n\n    public static int divide(int a, int b) {\n        return a \/ b;\n    }\n}<\/code><\/pre>\n
Yukar\u0131daki \u00f6rnekte org.slf4j.Logger<\/code> kulland\u0131\u011f\u0131m\u0131za dikkat edin. Bunun nedeni, Logback’in genellikle SLF4J ile birlikte kullan\u0131lmas\u0131d\u0131r.<\/p>\n
SLF4J (Simple Logging Facade for Java)<\/h4>\n
SLF4J, Java uygulamalar\u0131 i\u00e7in basit bir loglama cephesi (facade) veya soyutlama katman\u0131d\u0131r. Do\u011frudan bir loglama \u00e7er\u00e7evesi de\u011fildir; bunun yerine, geli\u015ftiricilerin kodlar\u0131nda belirli bir loglama \u00e7er\u00e7evesine (Log4j, Logback, JUL vb.) ba\u011f\u0131ml\u0131 kalmadan loglama yapmalar\u0131n\u0131 sa\u011flar.<\/p>\n
Neden SLF4J Kullan\u0131lmal\u0131?<\/h5>\n
*   Esneklik:<\/strong> Uygulaman\u0131z\u0131n loglama altyap\u0131s\u0131n\u0131 istedi\u011finiz zaman de\u011fi\u015ftirebilirsiniz (\u00f6rne\u011fin, Log4j’den Logback’e ge\u00e7mek) kodunuzu de\u011fi\u015ftirmeden. Sadece ba\u011f\u0131ml\u0131l\u0131klar\u0131 ve yap\u0131land\u0131rma dosyas\u0131n\u0131 g\u00fcncellersiniz.
\n*   K\u00fct\u00fcphane Uyumlu\u011fu:<\/strong> Farkl\u0131 \u00fc\u00e7\u00fcnc\u00fc parti k\u00fct\u00fcphaneler farkl\u0131 loglama \u00e7er\u00e7eveleri kullanabilir. SLF4J, t\u00fcm bu farkl\u0131 \u00e7er\u00e7eveleri tek bir standart aray\u00fcz alt\u0131nda birle\u015ftirerek “loglama karma\u015fas\u0131n\u0131” \u00f6nler.
\n*   Performans:<\/strong> Parametreli log mesajlar\u0131 (logger.debug(\"Mesaj: {}\", parameter);<\/code>) sayesinde, log seviyesi uygun olmad\u0131\u011f\u0131nda gereksiz String birle\u015ftirme i\u015flemlerini \u00f6nler.<\/p>\n
SLF4J Kullan\u0131m \u00d6rne\u011fi (Logback ile Birlikte)<\/h5>\n
SLF4J kullanmak i\u00e7in iki ana ba\u011f\u0131ml\u0131l\u0131\u011fa ihtiyac\u0131n\u0131z vard\u0131r: slf4j-api<\/code> ve kullanmak istedi\u011finiz loglama \u00e7er\u00e7evesinin SLF4J uygulamas\u0131 (\u00f6rne\u011fin, logback-classic<\/code> Logback i\u00e7in, log4j-slf4j-impl<\/code> Log4j 2 i\u00e7in).<\/p>\n
Maven ba\u011f\u0131ml\u0131l\u0131klar\u0131 (Logback ile):<\/p>\n
\n    org.slf4j<\/groupId>\n    slf4j-api<\/artifactId>\n    2.0.13<\/version>\n<\/dependency>\n\n    ch.qos.logback<\/groupId>\n    logback-classic<\/artifactId>\n    1.5.6<\/version>\n    \n<\/dependency><\/code><\/pre>\n
Java kodu:<\/p>\n
import org.slf4j.Logger;\nimport org.slf4j.LoggerFactory;\n\npublic class Slf4jExample {\n\n    private static final Logger logger = LoggerFactory.getLogger(Slf4jExample.class);\n\n    public static void main(String[] args) {\n        String userName = \"Alice\";\n        int userId = 123;\n\n        logger.info(\"Kullan\u0131c\u0131 {} (ID: {}) sisteme giri\u015f yapt\u0131.\", userName, userId);\n        logger.debug(\"Kullan\u0131c\u0131 detaylar\u0131 getiriliyor...\");\n\n        try {\n            processData(null);\n        } catch (IllegalArgumentException e) {\n            logger.error(\"Veri i\u015flenirken hata olu\u015ftu: {}\", e.getMessage(), e); \/\/ Son parametre throwable i\u00e7in\n        }\n    }\n\n    public static void processData(String data) {\n        if (data == null) {\n            throw new IllegalArgumentException(\"\u0130\u015flenecek veri bo\u015f olamaz.\");\n        }\n        logger.info(\"Veri ba\u015far\u0131yla i\u015flendi.\");\n    }\n}<\/code><\/pre>\n
Bu \u00f6rnekte, kodunuzda sadece org.slf4j.Logger<\/code> ve LoggerFactory<\/code> kullan\u0131yorsunuz. Arka planda hangi loglama \u00e7er\u00e7evesinin \u00e7al\u0131\u015ft\u0131\u011f\u0131 (Logback, Log4j 2 veya JUL) ba\u011f\u0131ml\u0131l\u0131klar\u0131n\u0131za ve yap\u0131land\u0131rman\u0131za ba\u011fl\u0131d\u0131r. Bu sayede, uygulaman\u0131z\u0131n loglama altyap\u0131s\u0131n\u0131 de\u011fi\u015ftirmek istedi\u011finizde Java kodunuzu yeniden derlemenize gerek kalmaz.<\/p>\n
Loglama Seviyeleri (Logging Levels)<\/h3>\n
Loglama seviyeleri, bir log mesaj\u0131n\u0131n \u00f6nemini ve aciliyetini belirtmek i\u00e7in kullan\u0131l\u0131r. Bu seviyeler sayesinde, \u00fcretim ortam\u0131nda sadece kritik hatalar\u0131, geli\u015ftirme ortam\u0131nda ise daha detayl\u0131 hata ay\u0131klama mesajlar\u0131n\u0131 g\u00f6rebiliriz. \u00c7o\u011fu loglama \u00e7er\u00e7evesi benzer seviyeleri kullan\u0131r:<\/p>\n
*   OFF<\/code>:<\/strong> Hi\u00e7bir log mesaj\u0131 kaydedilmez. Loglama tamamen devre d\u0131\u015f\u0131 b\u0131rak\u0131l\u0131r.
\n*   FATAL<\/code> (Log4j 2):<\/strong> Uygulaman\u0131n \u00e7al\u0131\u015fmas\u0131n\u0131 tamamen durduran, kurtar\u0131lamaz bir hata. Genellikle uygulaman\u0131n \u00e7\u00f6kmesine yol a\u00e7ar.
\n*   ERROR<\/code>:<\/strong> Uygulaman\u0131n normal \u00e7al\u0131\u015fmas\u0131n\u0131 engelleyen, ancak mutlaka durdurmayan ciddi bir hata. Bir i\u015flemin ba\u015far\u0131s\u0131z olmas\u0131na neden olur.
\n*   WARN<\/code>:<\/strong> Potansiyel bir sorun veya beklenmedik bir durum. Uygulaman\u0131n \u00e7al\u0131\u015fmas\u0131n\u0131 etkilemez ancak gelecekte sorunlara yol a\u00e7abilir.
\n*   INFO<\/code>:<\/strong> Uygulaman\u0131n genel ilerleyi\u015fi hakk\u0131nda bilgi veren mesajlar. Kullan\u0131c\u0131 giri\u015fleri, uygulaman\u0131n ba\u015flat\u0131lmas\u0131\/kapat\u0131lmas\u0131 gibi olaylar.
\n*   DEBUG<\/code>:<\/strong> Geli\u015ftirme s\u0131ras\u0131nda hata ay\u0131klama i\u00e7in kullan\u0131lan detayl\u0131 bilgiler. De\u011fi\u015fken de\u011ferleri, metod \u00e7a\u011fr\u0131lar\u0131 gibi.
\n*   TRACE<\/code>:<\/strong> DEBUG<\/code> seviyesinden daha da detayl\u0131 bilgiler. \u00c7ok ince taneli i\u015flem ad\u0131mlar\u0131. Genellikle sadece \u00e7ok \u00f6zel durumlarda kullan\u0131l\u0131r.
\n*   ALL<\/code>:<\/strong> T\u00fcm log mesajlar\u0131 kaydedilir.<\/p>\n
Loglama seviyeleri hiyerar\u015fiktir. Bir logger’\u0131n seviyesi INFO<\/code> olarak ayarland\u0131\u011f\u0131nda, sadece INFO<\/code>, WARN<\/code>, ERROR<\/code> ve FATAL<\/code> seviyesindeki mesajlar i\u015flenir. DEBUG<\/code> ve TRACE<\/code> seviyesindeki mesajlar g\u00f6z ard\u0131 edilir.<\/p>\n
Loglama Yap\u0131land\u0131rmas\u0131 (Configuration)<\/h3>\n
Loglama \u00e7er\u00e7evelerinin g\u00fcc\u00fc, esnek yap\u0131land\u0131rma se\u00e7eneklerinden gelir. Yap\u0131land\u0131rma, loglar\u0131n nereye yaz\u0131laca\u011f\u0131n\u0131 (konsol, dosya, veritaban\u0131 vb.), hangi formatta olaca\u011f\u0131n\u0131, hangi seviyeden itibaren loglanaca\u011f\u0131n\u0131 ve log dosyalar\u0131n\u0131n nas\u0131l y\u00f6netilece\u011fini belirler.<\/p>\n
Yap\u0131land\u0131rma genellikle harici dosyalar arac\u0131l\u0131\u011f\u0131yla yap\u0131l\u0131r:
\n*   Log4j 2:<\/strong> log4j2.xml<\/code>, log4j2.yaml<\/code>, log4j2.json<\/code>
\n*   Logback:<\/strong> logback.xml<\/code>, logback-spring.xml<\/code>
\n*   JUL:<\/strong> logging.properties<\/code><\/p>\n
Bu dosyalar genellikle uygulaman\u0131n s\u0131n\u0131f yolu (classpath) i\u00e7inde bulunur.<\/p>\n
Yap\u0131land\u0131rma \u00d6rnekleri (Tekrar Hat\u0131rlatma)<\/h5>\n
Yukar\u0131daki Log4j 2 ve Logback \u00f6rneklerinde detayl\u0131 yap\u0131land\u0131rma dosyalar\u0131 verilmi\u015ftir. \u00d6nemli k\u0131s\u0131mlar:<\/p>\n
*   Appender’lar:<\/strong> Loglar\u0131n yaz\u0131laca\u011f\u0131 hedefleri tan\u0131mlar.
\n    *   ConsoleAppender<\/code>: Konsola yazar.
\n    *   FileAppender<\/code>: Tek bir dosyaya yazar.
\n    *   RollingFileAppender<\/code> (Log4j 2) \/ RollingFileAppender<\/code> (Logback): Belirli bir boyuta veya zamana ula\u015ft\u0131\u011f\u0131nda log dosyas\u0131n\u0131 d\u00f6nd\u00fcr\u00fcr (eski dosyay\u0131 ar\u015fivler ve yeni bir dosya olu\u015fturur). Bu, log dosyalar\u0131n\u0131n \u00e7ok b\u00fcy\u00fcmesini engeller.
\n    *   Di\u011fer Appender’lar: SMTPAppender<\/code> (e-posta g\u00f6nderir), JDBCAppender<\/code> (veritaban\u0131na yazar), JMSAppender<\/code> (JMS kuyru\u011funa g\u00f6nderir) vb.
\n*   Layout’lar \/ Encoder’lar:<\/strong> Log mesajlar\u0131n\u0131n format\u0131n\u0131 belirler. PatternLayout<\/code> (Log4j 2) ve PatternLayoutEncoder<\/code> (Logback) en yayg\u0131n olanlard\u0131r ve %d<\/code> (tarih), %t<\/code> (thread ad\u0131), %-5level<\/code> (log seviyesi), %logger<\/code> (logger ad\u0131), %msg<\/code> (mesaj), %n<\/code> (yeni sat\u0131r) gibi desen kodlar\u0131 kullan\u0131larak \u00e7\u0131kt\u0131 \u00f6zelle\u015ftirilebilir.
\n*   Logger’lar:<\/strong> Belirli paketler veya s\u0131n\u0131flar i\u00e7in log seviyeleri ve Appender referanslar\u0131 tan\u0131mlan\u0131r.
\n    *   Root Logger<\/code>: T\u00fcm log mesajlar\u0131 i\u00e7in varsay\u0131lan davran\u0131\u015f\u0131 belirler. Genellikle t\u00fcm Appender’lara y\u00f6nlendirilir.
\n    *   Spesifik Logger’lar: Belirli bir paket veya s\u0131n\u0131f i\u00e7in level<\/code> \u00f6zniteli\u011fi ile \u00f6zel bir log seviyesi ayarlanabilir. additivity=\"false\"<\/code> ayar\u0131, bu logger’\u0131n mesajlar\u0131n\u0131n Root Logger’a iletilmesini engeller. Bu, loglar\u0131n birden fazla kez yaz\u0131lmas\u0131n\u0131 \u00f6nlemek i\u00e7in kullan\u0131\u015fl\u0131d\u0131r.<\/p>\n
\u0130yi Loglama Pratikleri (Best Practices)<\/h3>\n
Etkili loglama, sadece bir loglama \u00e7er\u00e7evesi kullanmaktan ibaret de\u011fildir. Loglar\u0131n\u0131z\u0131 nas\u0131l olu\u015fturdu\u011funuz, y\u00f6netti\u011finiz ve analiz etti\u011finiz de \u00f6nemlidir.<\/p>\n
1.  Anlaml\u0131 ve Ba\u011flam \u0130\u00e7eren Mesajlar Yaz\u0131n:<\/strong> Log mesajlar\u0131 k\u0131sa ve net olmal\u0131, ancak ayn\u0131 zamanda yeterli ba\u011flam\u0131 sa\u011flamal\u0131d\u0131r. Sadece “Hata olu\u015ftu” demek yerine, “Kullan\u0131c\u0131 ID 123 i\u00e7in sipari\u015f i\u015flenirken veritaban\u0131 ba\u011flant\u0131 hatas\u0131 olu\u015ftu” gibi daha a\u00e7\u0131klay\u0131c\u0131 mesajlar kullan\u0131n.
\n2.  Do\u011fru Log Seviyelerini Kullan\u0131n:<\/strong> Her mesaj\u0131n amac\u0131na uygun bir seviye atay\u0131n.
\n    *   TRACE\/DEBUG<\/code>: Geli\u015ftirme ve hata ay\u0131klama s\u0131ras\u0131nda detayl\u0131 bilgi.
\n    *   INFO<\/code>: Uygulaman\u0131n normal ak\u0131\u015f\u0131n\u0131 g\u00f6steren \u00f6nemli olaylar.
\n    *   WARN<\/code>: Potansiyel sorunlar veya beklenmeyen ancak tolere edilebilir durumlar.
\n    *   ERROR<\/code>: Bir i\u015flemin ba\u015far\u0131s\u0131z olmas\u0131na neden olan hatalar.
\n    *   FATAL<\/code>: Uygulaman\u0131n \u00e7\u00f6kmesine neden olan kritik hatalar.
\n3.  Hassas Bilgileri Loglamaktan Ka\u00e7\u0131n\u0131n:<\/strong> Parolalar, kredi kart\u0131 numaralar\u0131, ki\u015fisel kimlik bilgileri (PII) gibi hassas verileri loglara yazmaktan kesinlikle ka\u00e7\u0131n\u0131n. Bu, g\u00fcvenlik a\u00e7\u0131klar\u0131 ve GDPR\/KVKK gibi d\u00fczenlemelerle uyumsuzluk yaratabilir. Gerekirse bu bilgileri maskeleyin veya anonimle\u015ftirin.
\n4.  Parametreli Log Mesajlar\u0131 Kullan\u0131n (SLF4J ile):<\/strong> logger.debug(\"Kullan\u0131c\u0131: {}\", username);<\/code> \u015feklinde parametreleri kullanarak String birle\u015ftirmeden ka\u00e7\u0131n\u0131n. Bu, log seviyesi uygun olmad\u0131\u011f\u0131nda String birle\u015ftirme maliyetini ortadan kald\u0131rarak performans\u0131 art\u0131r\u0131r.
\n5.  Exception’lar\u0131 Do\u011fru Loglay\u0131n:<\/strong> Hata durumlar\u0131nda, logger.error(\"Hata mesaj\u0131\", e);<\/code> \u015feklinde Exception<\/code> nesnesini log metoduna ikinci parametre olarak ge\u00e7irin. Bu, stack trace’in loglanmas\u0131n\u0131 sa\u011flar ve hatan\u0131n k\u00f6k nedenini bulmay\u0131 kolayla\u015ft\u0131r\u0131r.
\n6.  Asenkron Loglama Kullan\u0131n:<\/strong> \u00d6zellikle y\u00fcksek performans gerektiren uygulamalarda, loglama i\u015fleminin ana uygulama i\u015f par\u00e7ac\u0131\u011f\u0131n\u0131 engellemesini \u00f6nlemek i\u00e7in asenkron loglama yap\u0131land\u0131rmay\u0131 d\u00fc\u015f\u00fcn\u00fcn. Log4j 2 ve Logback, asenkron Appender’lar sunar.
\n7.  Loglar\u0131 Yap\u0131land\u0131r\u0131lm\u0131\u015f Formatlarda Tutun (JSON gibi):<\/strong> Da\u011f\u0131t\u0131k sistemlerde ve log analizi ara\u00e7lar\u0131yla (ELK Stack, Splunk) \u00e7al\u0131\u015f\u0131rken, loglar\u0131 JSON gibi yap\u0131land\u0131r\u0131lm\u0131\u015f bir formatta tutmak, loglar\u0131n otomatik olarak ayr\u0131\u015ft\u0131r\u0131lmas\u0131n\u0131 ve sorgulanmas\u0131n\u0131 kolayla\u015ft\u0131r\u0131r.
\n8.  Korelasyon ID’leri Kullan\u0131n:<\/strong> Mikroservis mimarilerinde veya da\u011f\u0131t\u0131k sistemlerde, bir iste\u011fin birden fazla servis aras\u0131nda nas\u0131l ilerledi\u011fini takip etmek zordur. Her istek i\u00e7in benzersiz bir “korelasyon ID” olu\u015fturup, bu ID’yi t\u00fcm log mesajlar\u0131na dahil etmek, bir iste\u011fin t\u00fcm ya\u015fam d\u00f6ng\u00fcs\u00fcn\u00fc izlemenizi sa\u011flar.
\n9.  Merkezi Log Y\u00f6netimi:<\/strong> \u00dcretim ortamlar\u0131nda, loglar\u0131 tek bir yerden toplamak, depolamak, aramak ve analiz etmek i\u00e7in merkezi bir log y\u00f6netimi \u00e7\u00f6z\u00fcm\u00fc (\u00f6rne\u011fin, ELK Stack: Elasticsearch, Logstash, Kibana) kullan\u0131n.<\/p>\n
\u00d6rnek Uygulama: SLF4J + Logback Kullan\u0131m\u0131<\/h3>\n
\u015eimdi, SLF4J ve Logback’i birle\u015ftirerek kapsaml\u0131 bir \u00f6rnek olu\u015ftural\u0131m.<\/p>\n
1. Maven pom.xml<\/code> Ba\u011f\u0131ml\u0131l\u0131klar\u0131:<\/strong><\/p>\n
\n\n    4.0.0<\/modelVersion>\n\n    com.example<\/groupId>\n    java-logging-example<\/artifactId>\n    1.0-SNAPSHOT<\/version>\n\n    \n        11<\/maven.compiler.source>\n        11<\/maven.compiler.target>\n        UTF-8<\/project.build.sourceEncoding>\n        2.0.13<\/slf4j.version>\n        1.5.6<\/logback.version>\n    <\/properties>\n\n    \n        \n        \n            org.slf4j<\/groupId>\n            slf4j-api<\/artifactId>\n            ${slf4j.version}<\/version>\n        <\/dependency>\n        \n        \n            ch.qos.logback<\/groupId>\n            logback-classic<\/artifactId>\n            ${logback.version}<\/version>\n        <\/dependency>\n        \n        \n            ch.qos.logback<\/groupId>\n            logback-core<\/artifactId>\n            ${logback.version}<\/version>\n        <\/dependency>\n    <\/dependencies>\n\n    \n        \n            \n                org.apache.maven.plugins<\/groupId>\n                maven-compiler-plugin<\/artifactId>\n                3.8.1<\/version>\n                \n                    ${maven.compiler.source}<\/source>\n                    ${maven.compiler.target}<\/target>\n                <\/configuration>\n            <\/plugin>\n            \n                org.apache.maven.plugins<\/groupId>\n                maven-jar-plugin<\/artifactId>\n                3.2.0<\/version>\n                \n                    \n                        \n                            true<\/addClasspath>\n                            com.example.logging.Application<\/mainClass>\n                        <\/manifest>\n                    <\/archive>\n                <\/configuration>\n            <\/plugin>\n        <\/plugins>\n    <\/build>\n<\/project><\/code><\/pre>\n
2. src\/main\/resources\/logback.xml<\/code> Yap\u0131land\u0131rmas\u0131:<\/strong><\/p>\n
\n    \n    \n\n    \n    \n        \n            %d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n<\/pattern>\n        <\/encoder>\n    <\/appender>\n\n    \n    \n        ${LOG_DIR}\/${LOG_FILE_NAME}<\/file>\n        \n            ${LOG_DIR}\/archived\/${LOG_FILE_NAME}.%d{yyyy-MM-dd}.%i.gz<\/fileNamePattern>\n            10MB<\/maxFileSize>\n            7<\/maxHistory> \n            1GB<\/totalSizeCap> \n        <\/rollingPolicy>\n        \n            %d{yyyy-MM-dd HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n<\/pattern>\n        <\/encoder>\n    <\/appender>\n\n    \n    \n        ${LOG_DIR}\/json_logs\/app-json.log<\/file>\n        \n            ${LOG_DIR}\/json_logs\/archived\/app-json.%d{yyyy-MM-dd}.%i.json.gz<\/fileNamePattern>\n            10MB<\/maxFileSize>\n            7<\/maxHistory>\n            1GB<\/totalSizeCap>\n        <\/rollingPolicy>\n        \n            {\"timestamp\":\"%d{yyyy-MM-dd HH:mm:ss.SSS}\", \"level\":\"%level\", \"thread\":\"%thread\", \"logger\":\"%logger{36}\", \"message\":\"%msg\"}%n<\/pattern>\n        <\/encoder>\n    <\/appender>\n\n    \n    \n        \n        \n    <\/logger>\n\n    \n    \n        \n        \n        \n    <\/root>\n<\/configuration><\/code><\/pre>\n
3. src\/main\/java\/com\/example\/logging\/Application.java<\/code> S\u0131n\u0131f\u0131:<\/strong><\/p>\n
package com.example.logging;\n\nimport com.example.logging.service.UserService;\nimport org.slf4j.Logger;\nimport org.slf4j.LoggerFactory;\n\npublic class Application {\n\n    \/\/ SLF4J Logger'\u0131 kullanarak loglama yap\u0131yoruz\n    private static final Logger logger = LoggerFactory.getLogger(Application.class);\n\n    public static void main(String[] args) {\n        logger.info(\"Uygulama ba\u015flat\u0131l\u0131yor...\");\n\n        UserService userService = new UserService();\n\n        \/\/ Ba\u015far\u0131l\u0131 bir kullan\u0131c\u0131 i\u015flemi\n        userService.createUser(\"Alice\", \"alice@example.com\");\n\n        \/\/ Hatal\u0131 bir kullan\u0131c\u0131 i\u015flemi\n        try {\n            userService.createUser(\"Bob\", \"invalid-email\");\n        } catch (IllegalArgumentException e) {\n            logger.error(\"Kullan\u0131c\u0131 olu\u015fturulurken bir hata olu\u015ftu: {}\", e.getMessage(), e);\n        }\n\n        \/\/ Farkl\u0131 log seviyelerinde mesajlar\n        logger.debug(\"Debug seviyesinde bir mesaj. Sadece debug seviyesi etkinse g\u00f6r\u00fcn\u00fcr.\");\n        logger.trace(\"Trace seviyesinde bir mesaj. En detayl\u0131 seviyedir.\");\n        logger.warn(\"Dikkat: Uygulama \u00f6nbelle\u011fi yenilenemedi.\");\n\n        logger.info(\"Uygulama ba\u015far\u0131yla tamamland\u0131.\");\n    }\n}<\/code><\/pre>\n
4. src\/main\/java\/com\/example\/logging\/service\/UserService.java<\/code> S\u0131n\u0131f\u0131:<\/strong><\/p>\n
package com.example.logging.service;\n\nimport org.slf4j.Logger;\nimport org.slf4j.LoggerFactory;\n\npublic class UserService {\n\n    \/\/ Servis katman\u0131 i\u00e7in ayr\u0131 bir logger\n    private static final Logger logger = LoggerFactory.getLogger(UserService.class);\n\n    public void createUser(String name, String email) {\n        logger.debug(\"Kullan\u0131c\u0131 olu\u015fturma iste\u011fi al\u0131nd\u0131: \u0130sim={}, E-posta={}\", name, email);\n\n        if (name == null || name.trim().isEmpty()) {\n            logger.error(\"Kullan\u0131c\u0131 ad\u0131 bo\u015f olamaz.\");\n            throw new IllegalArgumentException(\"Kullan\u0131c\u0131 ad\u0131 bo\u015f olamaz.\");\n        }\n\n        if (!isValidEmail(email)) {\n            logger.warn(\"Ge\u00e7ersiz e-posta format\u0131 alg\u0131land\u0131: {}\", email);\n            throw new IllegalArgumentException(\"Ge\u00e7ersiz e-posta format\u0131.\");\n        }\n\n        \/\/ Ger\u00e7ekte burada veritaban\u0131na kaydetme vb. i\u015flemler olurdu.\n        logger.info(\"Kullan\u0131c\u0131 '{}' (E-posta: {}) ba\u015far\u0131yla olu\u015fturuldu.\", name, email);\n    }\n\n    private boolean isValidEmail(String email) {\n        \/\/ Basit bir e-posta do\u011frulama kontrol\u00fc\n        return email != null && email.contains(\"@\") && email.contains(\".\");\n    }\n}<\/code><\/pre>\n
Bu \u00f6rnekte, Application<\/code> s\u0131n\u0131f\u0131 INFO<\/code> seviyesinde loglarken, UserService<\/code> s\u0131n\u0131f\u0131 i\u00e7in logback.xml<\/code> i\u00e7inde \u00f6zel bir logger<\/code> tan\u0131m\u0131 yaparak DEBUG<\/code> seviyesinde loglama yapmas\u0131n\u0131 sa\u011flad\u0131k. B\u00f6ylece, uygulaman\u0131n genel ak\u0131\u015f\u0131n\u0131 INFO<\/code> seviyesinde izlerken, UserService<\/code> i\u00e7indeki daha detayl\u0131 ad\u0131mlar\u0131 DEBUG<\/code> seviyesinde g\u00f6rebiliriz. Ayr\u0131ca, farkl\u0131 Appender’lar (konsol, metin dosyas\u0131, JSON dosyas\u0131) kullanarak loglar\u0131n farkl\u0131 hedeflere ve formatlarda yaz\u0131lmas\u0131n\u0131 g\u00f6sterdik.<\/p>\n
Sonu\u00e7<\/h3>\n
Java’da loglama, modern yaz\u0131l\u0131m geli\u015ftirmenin vazge\u00e7ilmez bir par\u00e7as\u0131d\u0131r. Uygulamalar\u0131n\u0131z\u0131n davran\u0131\u015f\u0131n\u0131 anlamak, hatalar\u0131 h\u0131zl\u0131ca tespit etmek ve performans sorunlar\u0131n\u0131 gidermek i\u00e7in sa\u011flam bir loglama stratejisi olu\u015fturmak hayati \u00f6neme sahiptir. java.util.logging<\/code> basit senaryolar i\u00e7in yeterli olsa da, Log4j 2 ve Logback gibi \u00fc\u00e7\u00fcnc\u00fc parti \u00e7er\u00e7eveler, daha fazla esneklik, performans ve zengin \u00f6zellikler sunar. SLF4J gibi bir soyutlama katman\u0131 kullanmak, uygulaman\u0131z\u0131 belirli bir loglama \u00e7er\u00e7evesine ba\u011f\u0131ml\u0131 k\u0131lmadan gelecekteki de\u011fi\u015fikliklere kar\u015f\u0131 diren\u00e7li hale getirir.<\/p>\n
Unutmay\u0131n ki iyi loglama pratikleri, sadece loglama \u00e7er\u00e7evesini do\u011fru yap\u0131land\u0131rmakla kalmaz, ayn\u0131 zamanda anlaml\u0131, ba\u011flam i\u00e7eren ve do\u011fru seviyelerde log mesajlar\u0131 yazmay\u0131 da i\u00e7erir. Bu sayede, loglar\u0131n\u0131z yaln\u0131zca bir dosya y\u0131\u011f\u0131n\u0131 olmaktan \u00e7\u0131kar ve uygulaman\u0131z\u0131n kalbine giden de\u011ferli bir rehber haline gelir.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"Java’da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler\nJava uygulamalar\u0131 geli\u015ftirirken, kodun do\u011fru \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak, hatalar\u0131 tespit","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1408],"tags":[],"class_list":{"0":"post-31219","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-java","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nJava'da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Java'da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler\" \/>\n<meta property=\"og:description\" content=\"Java'da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler Java uygulamalar\u0131 geli\u015ftirirken, kodun do\u011fru \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak, hatalar\u0131 tespit\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2025-10-07T06:41:16+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"19 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"Java’da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler\",\"datePublished\":\"2025-10-07T06:41:16+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/\"},\"wordCount\":2527,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Java\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/#respond\"]}],\"copyrightYear\":\"2025\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/\",\"name\":\"Java'da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2025-10-07T06:41:16+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Java’da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Java'da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/","og_locale":"tr_TR","og_type":"article","og_title":"Java'da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler","og_description":"Java'da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler Java uygulamalar\u0131 geli\u015ftirirken, kodun do\u011fru \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak, hatalar\u0131 tespit","og_url":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2025-10-07T06:41:16+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"19 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"Java’da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler","datePublished":"2025-10-07T06:41:16+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/"},"wordCount":2527,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Java"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/#respond"]}],"copyrightYear":"2025","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/","url":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/","name":"Java'da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2025-10-07T06:41:16+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/javada-loglama-kapsamli-bir-bakis-ve-ornekler\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Java’da Loglama: Kapsaml\u0131 Bir Bak\u0131\u015f ve \u00d6rnekler"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/31219","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=31219"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/31219\/revisions"}],"predecessor-version":[{"id":31220,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/31219\/revisions\/31220"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=31219"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=31219"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=31219"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}