Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Kami menyediakan paket logging yang kompatibel dengan library standar. Library Cloud Logging untuk Go mengekspos lapisan tingkat yang lebih tinggi untuk menggunakan Cloud Logging.
Agen Cloud Logging tidak harus diinstal untuk menggunakan library Cloud Logging untuk Go di instance VM Compute Engine.
Sebelum memulai
Sign in to your Google Cloud account. If you're new to
Google Cloud,
create an account to evaluate how our products perform in
real-world scenarios. New customers also get $300 in free credits to
run, test, and deploy workloads.
In the Google Cloud console, on the project selector page,
select or create a Google Cloud project.
// Sample stdlogging writes log.Logger logs to the Cloud Logging.packagemainimport("context""log""cloud.google.com/go/logging")funcmain(){ctx:=context.Background()// Sets your Google Cloud Platform project ID.projectID:="YOUR_PROJECT_ID"// Creates a client.client,err:=logging.NewClient(ctx,projectID)iferr!=nil{log.Fatalf("Failed to create client: %v",err)}deferclient.Close()// Sets the name of the log to write to.logName:="my-log"logger:=client.Logger(logName).StandardLogger(logging.Info)// Logs "hello world", log entry is visible at// Cloud Logs.logger.Println("hello world")}
Untuk mengetahui informasi selengkapnya tentang penginstalan, lihat
dokumentasi untuk
library Cloud Logging untuk Go. Anda juga dapat melaporkan masalah menggunakan
pelacak masalah.
Menulis log dengan library klien Cloud Logging
Untuk mengetahui informasi tentang cara menggunakan library klien Cloud Logging untuk
Go secara langsung, lihat Library Klien Cloud Logging.
Jalankan di Google Cloud
Agar aplikasi dapat menulis log menggunakan library Cloud Logging untuk Go, akun layanan untuk resource pokok harus memiliki peran Logs Writer (roles/logging.logWriter)IAM.
Sebagian besar lingkungan otomatis mengonfigurasi akun layanan default agar memiliki peran ini. Google Cloud
App Engine
Cloud Logging diaktifkan secara otomatis untuk App Engine, dan akun layanan default aplikasi Anda memiliki izin IAM secara default untuk menulis entri log.
GKE secara otomatis memberikan peran IAM Logs Writer (roles/logging.logWriter) kepada akun layanan default.
Jika Anda menggunakan
Workload Identity Federation untuk GKE
dengan akun layanan default ini untuk mengizinkan workload mengakses API
Google Cloud tertentu, tidak ada konfigurasi tambahan yang diperlukan.
Namun, jika Anda menggunakan Workload Identity Federation untuk GKE dengan akun layanan IAM kustom, pastikan akun layanan kustom tersebut memiliki peran Logs Writer (roles/logging.logWriter).
Jika perlu, Anda juga dapat menggunakan perintah berikut untuk menambahkan cakupan akses logging.write
saat membuat cluster:
Saat menggunakan instance VM Compute Engine, tambahkan cakupan akses cloud-platform
ke setiap instance. Saat membuat instance baru melalui
Google Cloud konsol, Anda dapat melakukannya di bagian Akses API dan identitas
pada panel Buat Instance. Gunakan akun layanan default Compute Engine atau akun layanan lain pilihan Anda, lalu pilih Izinkan akses penuh ke semua Cloud API di bagian Identity and API access. Akun layanan mana pun yang Anda pilih, pastikan akun tersebut telah diberi peran Logs Writer di bagian IAM & Admin pada konsolGoogle Cloud .
Menjalankan secara lokal dan di tempat lain
Untuk menggunakan library Cloud Logging untuk Go di luar Google Cloud,
termasuk menjalankan library di workstation Anda sendiri, di komputer pusat data Anda, atau di instance VM penyedia cloud lain, Anda harus menyiapkan Kredensial Default Aplikasi (ADC) di lingkungan lokal untuk melakukan autentikasi ke library Cloud Logging untuk Go.
Jika Anda menggunakan kotak penelusuran untuk menemukan halaman ini, pilih hasil yang subjudulnya adalah
Logging.
Di Logs Explorer, Anda harus menentukan satu atau beberapa resource, tetapi pemilihan resource mungkin tidak jelas. Berikut beberapa tips untuk membantu Anda memulai:
Jika Anda men-deploy aplikasi ke App Engine atau menggunakan
library khusus App Engine, setel resource Anda ke
Aplikasi GAE.
Jika Anda men-deploy aplikasi di Compute Engine, tetapkan resource ke Instance VM GCE.
Jika Anda men-deploy aplikasi di Google Kubernetes Engine, konfigurasi logging cluster Anda akan menentukan jenis resource entri log. Untuk mengetahui pembahasan mendetail tentang solusi Legacy Google Cloud Observability dan Google Cloud Observability Kubernetes Monitoring, serta pengaruh opsi tersebut terhadap jenis resource, lihat Bermigrasi ke Google Cloud Observability Kubernetes Monitoring.
Jika aplikasi Anda menggunakan Cloud Logging API secara langsung, resource bergantung pada API dan konfigurasi Anda. Misalnya,
di aplikasi, Anda dapat menentukan resource atau menggunakan resource default.
Jika Anda tidak melihat log apa pun di Logs Explorer, untuk melihat semua entri log,
beralihlah ke mode kueri lanjutan dan gunakan kueri kosong.
Untuk beralih ke mode kueri lanjutan, klik menu (▾) di bagian atas Logs Explorer, lalu pilih Konversikan ke filter lanjutan.
Hapus konten yang muncul di kotak filter.
Klik Kirim Filter.
Anda dapat memeriksa setiap entri untuk mengidentifikasi resource Anda.
[[["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-03 UTC."],[],[],null,["# Setting Up Cloud Logging for Go\n\nWe provide a standard library-compatible logging package. The\nCloud Logging library for Go exposes a higher-level layer for working with\nCloud Logging.\n\nThe Cloud Logging agent does not have to be installed to use the\nCloud Logging library for Go on a Compute Engine VM instance.\n\nBefore you begin\n----------------\n\n- Sign in to your Google Cloud account. If you're new to Google Cloud, [create an account](https://console.cloud.google.com/freetrial) to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n-\n\n\n Enable the Cloud Logging API.\n\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=logging.googleapis.com)\n\n- In the Google Cloud console, on the project selector page,\n select or create a Google Cloud project.\n\n | **Note**: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.\n\n [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)\n-\n [Verify that billing is enabled for your Google Cloud project](/billing/docs/how-to/verify-billing-enabled#confirm_billing_is_enabled_on_a_project).\n\n-\n\n\n Enable the Cloud Logging API.\n\n\n [Enable the API](https://console.cloud.google.com/flows/enableapi?apiid=logging.googleapis.com)\n\n\n### Installing the package\n\n```\ngo get cloud.google.com/go/logging\n```\n\n### Using the Go logger\n\n\n // Sample stdlogging writes log.Logger logs to the Cloud Logging.\n package main\n\n import (\n \t\"context\"\n \t\"log\"\n\n \t\"cloud.google.com/go/logging\"\n )\n\n func main() {\n \tctx := context.Background()\n\n \t// Sets your Google Cloud Platform project ID.\n \tprojectID := \"YOUR_PROJECT_ID\"\n\n \t// Creates a client.\n \tclient, err := logging.NewClient(ctx, projectID)\n \tif err != nil {\n \t\tlog.Fatalf(\"Failed to create client: %v\", err)\n \t}\n \tdefer client.Close()\n\n \t// Sets the name of the log to write to.\n \tlogName := \"my-log\"\n\n \tlogger := client.Logger(logName).https://cloud.google.com/go/docs/reference/cloud.google.com/go/logging/latest/index.html#cloud_google_com_go_logging_Logger_StandardLogger(logging.https://cloud.google.com/go/docs/reference/cloud.google.com/go/logging/latest/index.html#cloud_google_com_go_logging_Default_Debug_Info_Notice_Warning_Error_Critical_Alert_Emergency)\n\n \t// Logs \"hello world\", log entry is visible at\n \t// Cloud Logs.\n \tlogger.Println(\"hello world\")\n }\n\n\u003cbr /\u003e\n\nFor more information on installation, see the\n[documentation](/go/logging) for the\nCloud Logging library for Go. You can also report issues using the\n[issue tracker](https://github.com/GoogleCloudPlatform/google-cloud-go/issues).\n\nWrite logs with the Cloud Logging client library\n------------------------------------------------\n\nFor information on using the Cloud Logging client library for\nGo directly, see [Cloud Logging Client Libraries](/logging/docs/reference/libraries).\n\nRun on Google Cloud\n-------------------\n\nFor an application to write logs by using the Cloud Logging library for Go, the\nservice account for the underlying resource must have the\n[Logs Writer (`roles/logging.logWriter`)](/logging/docs/access-control#permissions_and_roles) [IAM](/iam/docs/understanding-roles) role.\nMost Google Cloud environments automatically configure the default\nservice account to have this role.\n\n### App Engine\n\nCloud Logging is automatically enabled for App Engine, and your app's\n[default service account](/appengine/docs/standard/go/service-account) has\nthe IAM permissions by default to write log entries.\n\nFor more information, see [Writing and viewing\nlogs](/appengine/docs/standard/go/writing-application-logs).\n\n### Google Kubernetes Engine (GKE)\n\n[GKE](/kubernetes-engine/docs) automatically grants the default service account\nthe [Logs Writer (`roles/logging.logWriter`)](/logging/docs/access-control#permissions_and_roles) IAM role.\nIf you use\n[Workload Identity Federation for GKE](/kubernetes-engine/docs/concepts/workload-identity)\nwith this default service account to let workloads access specific\nGoogle Cloud APIs, then no additional configuration is required.\nHowever, if you use Workload Identity Federation for GKE with a\ncustom IAM service account, then ensure that the custom service\naccount has the role of Logs Writer (`roles/logging.logWriter`).\n\nIf needed, you can also use the following command to add the `logging.write`\naccess scope when creating the cluster: \n\n gcloud container clusters create example-cluster-name \\\n --scopes https://www.googleapis.com/auth/logging.write\n\n### Compute Engine\n\n| **Note:** To use the Cloud Logging library for Go on a **Compute Engine** VM instance, you do not need to install the Cloud Logging agent.\n\nWhen using [Compute Engine](/compute/docs) VM instances, add the `cloud-platform`\naccess scope to each instance. When creating a new instance through the\nGoogle Cloud console, you can do this in the **Identity and API access** section\nof the **Create Instance** panel. Use the Compute Engine default service\naccount or another service account of your choice, and select\n**Allow full access to all Cloud APIs** in the **Identity and API access**\nsection. Whichever service\naccount you select, ensure that it has been granted the\n[Logs Writer role](/logging/docs/access-control#permissions_and_roles) in the **IAM \\& Admin** section of the\nGoogle Cloud console.\n\nRun locally and elsewhere\n-------------------------\n\nTo use the Cloud Logging library for Go outside of Google Cloud,\nincluding running the library on your own workstation, on your data center's\ncomputers, or on the VM instances of another cloud provider, you must\nset up Application Default Credentials (ADC) in your local environment to\nauthenticate to the Cloud Logging library for Go.\n\nFor more information, see\n[Set up ADC for on-premises or another cloud provider](/docs/authentication/set-up-adc-on-premises).\n\nView the logs\n-------------\n\nIn the Google Cloud console, go to the **Logs Explorer** page:\n\n[Go to **Logs Explorer**](https://console.cloud.google.com/logs/query)\n\n\u003cbr /\u003e\n\nIf you use the search bar to find this page, then select the result whose subheading is\n**Logging**.\n\nIn the Logs Explorer, you must specify one or more resources, but the resource\nselection might not be obvious. Here are some tips to help you get\nstarted:\n\n- If you are deploying your application to App Engine or using the\n App Engine-specific libraries, set your resource to\n **GAE Application**.\n\n- If you are deploying your application on Compute Engine, set the resource\n to **GCE VM Instance**.\n\n- If you are deploying your application on Google Kubernetes Engine, your\n cluster's logging configuration determines the resource type of the log\n entries. For a detailed\n discussion on the Legacy Google Cloud Observability and the Google Cloud Observability\n Kubernetes Monitoring solutions, and how those options affect the\n resource type, see\n [Migrating to Google Cloud Observability Kubernetes Monitoring](/monitoring/kubernetes-engine/migration#stackdriver-options).\n\n- If your application is using the Cloud Logging API directly,\n the resource is dependent on the API and your configuration. For example,\n in your application, you can specify a resource or use a default resource.\n\n- If you don't see any logs in the Logs Explorer, to see all log entries,\n switch to the advanced query mode and use an empty query.\n\n 1. To switch to the advanced query mode, click **menu** (▾) at the top of the Logs Explorer and then select **Convert to advanced filter**.\n 2. Clear the content that appears in the filter box.\n 3. Click **Submit Filter**.\n\n You can examine the individual entries to identify your resources.\n\nFor additional information, see [Using the Logs Explorer](/logging/docs/view/logs-explorer-interface)."]]
