Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Melihat log Integration Connectors
Halaman ini menjelaskan data logging yang tersedia untuk konektor dan cara Anda dapat mengakses data ini menggunakan Cloud Logging.
Cloud Logging adalah layanan terkelola sepenuhnya yang dapat Anda gunakan untuk menyimpan, menelusuri, menganalisis, memantau,
serta membuat pemberitahuan terkait data dan peristiwa logging dari Google Cloud. Untuk mengetahui informasi selengkapnya tentang Cloud Logging, lihat dokumentasi Cloud Logging.
Anda dapat mengonfigurasi konektor untuk mencatat log di salah satu level berikut:
Error: Mencatat pesan error yang terjadi
selama kegagalan seperti kegagalan koneksi, dan kegagalan autentikasi.
Log peringatan untuk pesan non-kritis juga akan dicatat. Misalnya, jika
Anda mengakses entitas yang tidak didukung, pesan peringatan akan dicatat ke dalam log.
Info: Mencatat informasi tentang operasi dan eksekusi. Umumnya, log ini akan memiliki permintaan, respons, dan header untuk permintaan yang dibuat konektor ke sistem backend Anda.
Debug: Mencatat informasi pelacakan mendetail yang akan berguna untuk men-debug
masalah apa pun dalam koneksi atau eksekusi. Log ini
akan memiliki semua informasi yang dicatat ke dalam log di tingkat Info dan Error, serta
detail tambahan seperti informasi SSL, panggilan jaringan, dan informasi pelacakan lainnya.
Melihat log
Jika logging diaktifkan untuk konektor, Anda dapat melihat log di Logs Explorer. Untuk melihat log di Google Cloud console, lakukan langkah-langkah berikut:
Contoh kueri ini menampilkan log untuk semua koneksi di semua region. Anda dapat memfilter log lebih lanjut berdasarkan region dan nama koneksi. Misalnya, kueri berikut menunjukkan log untuk koneksi cloud-storage-con-1, yang dikonfigurasi di lokasi us-central1.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 UTC."],[[["\u003cp\u003eThis page outlines how to access and view logging data for connectors using Google Cloud Logging, a service for storing, searching, and analyzing log events.\u003c/p\u003e\n"],["\u003cp\u003eConnectors can log at three levels: Error (including warning messages), Info (operations and execution details), and Debug (detailed tracing information); logging is disabled by default to maintain connector performance.\u003c/p\u003e\n"],["\u003cp\u003eTo view connector logs, you must enable logging during the connector's configuration or by editing an existing connector, then navigate to the Logs Explorer in the Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eIn the Logs Explorer, use the query \u003ccode\u003eresource.type="connectors.googleapis.com/Connection"\u003c/code\u003e to find logs for all connections, or refine the query by location and connection name for more specific results.\u003c/p\u003e\n"],["\u003cp\u003eFurther filtering of search results can be done in the Logs explorer by time, severity, and log name.\u003c/p\u003e\n"]]],[],null,["# View Integration Connectors logs\n================================\n\nThis page describes the logging data available for a connector and how you can access this\ndata using Cloud Logging.\n\n\nCloud Logging is a fully managed service that allows you to store, search, analyze, monitor,\nand alert on logging data and events from Google Cloud. For more information about\nCloud Logging, see [Cloud Logging documentation](/logging/docs).\n\nYou can configure a connector to log at any of the following levels:\n\n- **Error:** Logs error messages that occur during failures such as connection failures, and authentication failures. \n Warning logs for non-critical messages also get logged. For example, if you are accessing an unsupported entity, a warning message is logged.\n- **Info:** Logs information about operations and executions. Generally, this log will have request, response, and headers for the requests which the connector makes to your backend system.\n- **Debug:** Logs detailed tracing information which would be useful for debugging any issues in connection or execution. This log will have all the information that is logged at the **Info** and **Error** levels, and additional details such as SSL information, network calls, and other tracing information.\n\n| **Note:** Logging is disabled by default for a connector as enabling logging might impact performance. You can enable logging when configuring a new connector or if you already have a connector, you can enable logging by editing the connector. To understand how to edit a connector, see [Edit connection](/integration-connectors/docs/manage-connections).\n\nView logs\n---------\n\nIf logging is enabled for a connector, you can view the logs in the Logs Explorer. To view\nthe logs in the Google Cloud console, do the following steps:\n\n1. Go to the Logs Explorer in the Google Cloud console: [Go to Logs Explorer](https://console.cloud.google.com/logs)\n\n\n To get a better understanding of the Logs Explorer, see [Logs Explorer interface](/logging/docs/view/logs-explorer-interface).\n2. In the **Query** tab, enter: \n\n ```\n resource.type=\"connectors.googleapis.com/Connection\"\n ```\n\n This sample query shows logs for all the connections across all the regions. You can further\n filter the logs based on region and a connection name. For example, the following query\n shows logs for the `cloud-storage-con-1` connection, that is configured in the\n `us-central1` location. \n\n ```\n resource.type=\"connectors.googleapis.com/Connection\"\n resource.labels.location=\"us-central1\"\n resource.labels.connection=\"cloud-storage-con-1\"\n ```\n3. You can filter the search results further by time, severity, and log name.\n4. Click **Run query**."]]
