Untuk mendiskusikan dan memberikan masukan tentang produk kami, bergabunglah ke channel Discord Google Ads resmi di server Komunitas Iklan dan Pengukuran Google.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Logging dikonfigurasi dengan SLF4J, library logging generik untuk Java, yang memungkinkan log diarahkan ke banyak implementasi logging yang berbeda. Kami menyediakan
file konfigurasi untuk log4j 1.2/2 dan Java Util Logging (JUL).
Tata letak dan fungsi logging
Permintaan dicatat dengan ringkasan satu baris dan isi/header permintaan/respons lengkap.
Jenis log
Nama log
Tingkat keberhasilan
Tingkat kegagalan
RINGKASAN
com.google.ads.googleads.lib.request.summary
INFO
WARN
DETAIL
com.google.ads.googleads.lib.request.detail
DEBUG
INFO
Pemangkasan Log Detail
Log mendetail dipangkas secara default untuk menghindari pembuatan log berukuran besar. Untuk
mengubah panjang log yang dipangkas, tetapkan
-Dapi.googleads.maxLogMessageLength=<number>. Menyetel -1 akan menonaktifkan
pemangkasan log.
Log4j 2
Tambahkan dependensi pada library log4j-slf4j-impl, dengan mengganti
2.x.y dengan versi Log4j 2 yang Anda gunakan dalam project.
(Opsional) Buat file konfigurasi di direktori resource Anda, misalnya, di Maven: src/main/resources. Log4j 2 memuat file konfigurasi
dari classpath, bukan direktori kerja, jadi pastikan Anda membuatnya di
direktori resource.
Jalankan aplikasi Anda, dengan menentukan
-Dlog4j.configurationFile=<CONFIG_FILE_PATH>. Anda dapat menentukan
CONFIG_FILE_PATH=googleads-logging/log4j2.xml untuk menggunakan file
konfigurasi default yang disertakan dengan library klien.
Log4j 1.2 (lama)
Tambahkan dependensi pada library slf4j-log4j12, dengan mengganti 1.x.y dengan
versi Log4j 1.2 yang Anda gunakan dalam project Anda.
(Opsional) Buat file konfigurasi di direktori resource project Anda,
misalnya, di Maven, jalur adalah src/main/resources. Log4j 1.2 memuat file konfigurasinya dari classpath, bukan direktori kerja, jadi pastikan Anda menyalin ke direktori resource.
Jalankan aplikasi Anda, dengan menentukan -Dlog4j.configuration=<CONFIG_FILE_PATH>.
Anda dapat menentukan CONFIG_FILE_PATH=googleads-logging/log4j.properties untuk menggunakan file konfigurasi default yang disertakan dengan library klien.
Buat file konfigurasi JUL pada sistem file di jalur yang dapat dibaca dari
aplikasi Anda (misalnya, ./jdk-logger.properties). Template disediakan di
google-ads/src/main/resources/googleads-logging/jdk-logger.properties. JUL
hanya membaca dari sistem file, jadi jangan salin ke direktori resource.
Jalankan aplikasi Anda dengan menentukan
-Djava.util.logging.config.file=./jdk-logger.properties.
[null,null,["Terakhir diperbarui pada 2025-08-27 UTC."],[[["\u003cp\u003eLogging is managed through SLF4J, offering flexibility with log4j 1.2/2 and Java Util Logging configurations.\u003c/p\u003e\n"],["\u003cp\u003eRequest logging includes a summary line along with detailed request/response bodies and headers at configurable log levels.\u003c/p\u003e\n"],["\u003cp\u003eDetailed logs are truncated by default, adjustable via the \u003ccode\u003e-Dapi.googleads.maxLogMessageLength\u003c/code\u003e system property.\u003c/p\u003e\n"],["\u003cp\u003eConfiguration instructions and examples are provided for setup with Log4j 2, Log4j 1.2, and Java Util Logging.\u003c/p\u003e\n"]]],[],null,["# Logging is configured with SLF4J a generic logging library for Java, which\nallows logs to be directed to many different logging implementations. We provide\nconfiguration files for log4j 1.2/2 and Java Util Logging (JUL).\n\nLogging layout and functionality\n--------------------------------\n\nRequests are logged with a one line summary and the full request/response body\nand headers.\n\n| Log type | Log name | Success level | Failure level |\n|----------|----------------------------------------------|---------------|---------------|\n| SUMMARY | com.google.ads.googleads.lib.request.summary | INFO | WARN |\n| DETAIL | com.google.ads.googleads.lib.request.detail | DEBUG | INFO |\n\n| **Key Point:** Mutate requests where [Partial\n| failure](/google-ads/api/samples/handle-partial-failure) is true won't cause the entire request to fail. Thus, partial failure logs are always logged at Success level, not at Failure level as might be expected.\n\nDetail Log Truncation\n---------------------\n\nThe detailed logs are truncated by default to avoid creating large logs. To\nchange the length at which logs are truncated, set\n`-Dapi.googleads.maxLogMessageLength=\u003cnumber\u003e`. Setting `-1` disables\nlog truncation.\n\nLog4j 2\n-------\n\n1. Add a dependency on the `log4j-slf4j-impl` library, substituting\n `2.x.y` with the version of Log4j 2 you are using in your project.\n\n \u003cdependency\u003e\n \u003cgroupId\u003eorg.apache.logging.log4j\u003c/groupId\u003e\n \u003cartifactId\u003elog4j-slf4j-impl\u003c/artifactId\u003e\n \u003cversion\u003e2.x.y\u003c/version\u003e\n \u003c/dependency\u003e\n\n2. (Optional) Create a configuration file in your resources directory, for\n example, in Maven: `src/main/resources`. Log4j 2 loads its configuration\n file from the classpath, not the working directory, so ensure you create in a\n resources directory.\n\n3. Run your application, specifying\n `-Dlog4j.configurationFile=\u003cCONFIG_FILE_PATH\u003e`. You can specify\n `CONFIG_FILE_PATH=googleads-logging/log4j2.xml` to use the default\n configuration file included with the client libraries.\n\nLog4j 1.2 (legacy)\n------------------\n\n1. Add a dependency on the `slf4j-log4j12` library, substituting `1.x.y` with\n the version of Log4j 1.2 you are using in your project.\n\n \u003cdependency\u003e\n \u003cgroupId\u003eorg.slf4j\u003c/groupId\u003e\n \u003cartifactId\u003eslf4j-log4j12\u003c/artifactId\u003e\n \u003cversion\u003e1.x.y\u003c/version\u003e\n \u003c/dependency\u003e\n\n2. (Optional) Create a configuration file in your projects resources directory,\n for example, in Maven, path is `src/main/resources`. Log4j 1.2 loads its\n configuration file from the classpath, not the working directory, so ensure\n you copy to a resources directory.\n\n3. Run your application, specifying `-Dlog4j.configuration=\u003cCONFIG_FILE_PATH\u003e`.\n You can specify `CONFIG_FILE_PATH=googleads-logging/log4j.properties` to use\n the default configuration file includedwith the client libraries.\n\nJava Util Logging\n-----------------\n\n1. Add a dependency on the `slf4j-jdk14` library.\n\n \u003cdependency\u003e\n \u003cgroupId\u003eorg.slf4j\u003c/groupId\u003e\n \u003cartifactId\u003eslf4j-jdk14\u003c/artifactId\u003e\n \u003cversion\u003e1.7.25\u003c/version\u003e\n \u003c/dependency\u003e\n\n2. Create a JUL configuration file on the file system in a path readable from\n your application (for instance, `./jdk-logger.properties`). A template is\n provided at\n `google-ads/src/main/resources/googleads-logging/jdk-logger.properties`. JUL\n reads from the filesystem only, so do not copy to the resources directory.\n\n3. Run your application specifying\n `-Djava.util.logging.config.file=./jdk-logger.properties`."]]