Melihat log konsol untuk VM yang menggunakan Runtime VM di GDC
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Dokumen ini ditujukan untuk pemilik aplikasi yang menjalankan Google Distributed Cloud.
Dokumen ini menunjukkan cara melihat log konsol untuk virtual machine (VM) yang menggunakan Runtime VM di GDC. Anda dapat menggunakan log konsol VM untuk
memecahkan masalah dan mendiagnosis masalah di cluster.
Sebelum memulai
Untuk menyelesaikan dokumen ini, Anda memerlukan akses ke resource berikut:
Alat klien virtctl yang diinstal sebagai plugin untuk kubectl. Jika diperlukan,
instal alat klien virtctl.
Menghubungkan ke VM
Untuk memastikan ada log yang akan ditinjau, hubungkan ke VM Anda dan buat beberapa aktivitas log.
Untuk mengakses VM dari konsol, gunakan kubectl:
kubectlvirtconsoleVM_NAME
Ganti VM_NAME dengan nama VM yang ingin Anda
hubungkan.
Saat diminta, masukkan kredensial pengguna yang Anda tentukan saat membuat VM.
Jalankan perintah untuk memeriksa update, seperti apt-get untuk VM berbasis Debian
atau yum check-update untuk VM berbasis Red Hat.
Berbasis Debian
apt-getupdate
Berbasis Red Hat
yumcheck-update
Setelah berhasil membuat beberapa aktivitas log konsol, keluar dari sesi VM
dan konsol:
Ctrl+]
Melihat log konsol VM
Anda melihat log konsol VM di Google Cloud konsol. Log konsol serial VM
di-streaming ke Cloud Logging dan dapat dilihat di Logs Explorer. VM
yang berjalan menggunakan Runtime VM di GDC diklasifikasikan sebagai penampung dalam
log konsol.
Di konsol Google Cloud , buka halaman Logs Explorer di menu
Logging.
[[["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."],[],[],null,["This document is intended for application owners that run Google Distributed Cloud.\nThis document shows you how to view console logs for virtual machine (VM) that\nuse VM Runtime on GDC. You can use the VM console logs to\ntroubleshoot and diagnose problems in your cluster.\n\nBefore you begin\n\nTo complete this document, you need access to the following resources:\n\n- A VM that runs in one of your clusters. If needed, [create a VM in Google Distributed Cloud](/kubernetes-engine/distributed-cloud/bare-metal/docs/vm-runtime/quickstart).\n- The `virtctl` client tool installed as a plugin for `kubectl`. If needed, [install the virtctl client tool](/kubernetes-engine/distributed-cloud/bare-metal/docs/vm-runtime/quickstart#install_the_virtctl_client_tool).\n\nConnect to VM\n\nTo make sure there are logs to review, connect to your VM and generate some log\nactivity.\n\n1. To access a VM from the console, use `kubectl`:\n\n kubectl virt console \u003cvar label=\"name\" translate=\"no\"\u003eVM_NAME\u003c/var\u003e\n\n Replace \u003cvar translate=\"no\"\u003eVM_NAME\u003c/var\u003e with the name of the VM that you want to\n connect to.\n2. When prompted, enter the user credentials you specified when you created the\n VM.\n\n3. Run a command to check for updates, such as `apt-get` for Debian-based VMs\n or `yum check-update` for Red Hat-based VMs.\n\n Debian-based \n\n apt-get update\n\n Red Hat-based \n\n yum check-update\n\n4. After you have successfully generated some console log activity, exit the VM\n session and console:\n\n Ctrl + ]\n\nView VM console logs\n\nYou view VM console logs in the Google Cloud console. VM serial console logs\nare streamed to Cloud Logging and can be viewed in Logs Explorer. VMs\nthat run using VM Runtime on GDC are classed as containers in the\nconsole logs.\n\n1. In the Google Cloud console, go to the **Logs Explorer** page in the\n **Logging** menu.\n\n [Go to Logs Explorer](https://console.cloud.google.com/logs/query)\n2. In the **Query** field, enter the following basic query:\n\n resource.type=\"k8s_container\"\n resource.labels.container_name=\"log\"\n\n3. The **Query results** window shows the output of the console logs from\n your VMs, as shown in the following example screenshot:\n\n4. You can further filter the results of your query to a particular VM by adding\n the cluster name and the name of the VM to your query:\n\n resource.type=\"k8s_container\"\n resource.labels.container_name=\"log\"\n resource.labels.cluster_name=\"\u003cvar label=\"name of your cluster containing the VM\" translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e\"\n labels.k8s-pod/kubevirt/vm=\"\u003cvar label=\"name of your VM\" translate=\"no\"\u003eVM_NAME\u003c/var\u003e\"\n\n Replace the following:\n - \u003cvar scope=\"CLUSTER_NAME\" translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e: the name of the cluster that contains your VM.\n - \u003cvar scope=\"VM_NAME\" translate=\"no\"\u003eVM_NAME\u003c/var\u003e: the name of your VM.\n\nWhat's next\n\n- To learn more about how to filter your console logs, see [Build queries in Logs Explorer](/logging/docs/view/building-queries)."]]
