Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Error Reporting
menggabungkan dan menampilkan setiap error dalam menjalankan layanan Cloud Run
Anda. Cloud Run terintegrasi secara otomatis dengan
Error Reporting tanpa perlu pengaturan atau konfigurasi.
Error berikutnya bisa dilihat secara otomatis:
Semua pengecualian yang mencakup pelacakan tumpukan dalam bahasa yang didukung
Error Reporting, dan yang dikirim ke stdout, stderr, atau ke log lainnya.
Error layanan "Batas memori terlampaui" dan "Tidak ada instance yang tersedia".
Anda harus menangani error dan pengecualian yang terjadi selama permintaan. Memungkinkan
terjadinya error menyebabkan kegagalan dalam aplikasi Anda pada
cold start saat instance
container baru dimulai.
Menampilkan error di Cloud Run
Tab "Metrics" pada halaman detail layanan
mencakup menampilkan tabel error teratas dari layanan ini
yang telah dideteksi dan digabungkan oleh Error Reporting.
Menampilkan error di Error Reporting
Anda dapat melihat error setelah Error Reporting mengumpulkannya. Untuk
mengetahui detail, lihat Viewing Errors.
Untuk meninjau error Anda saat ini, buka halaman Error Reporting di
Google Cloud konsol:
[[["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-08-21 UTC."],[],[],null,["# Error Reporting\naggregates and displays errors produced in your running Cloud Run\nservices. Cloud Run is automatically integrated with\nError Reporting **with no setup or configuration required**.\n\nThe following errors are automatically visible:\n\n1. All exceptions that include a stack trace in [Error Reporting-supported\n languages](/error-reporting/docs/setup), and that are sent to `stdout`, `stderr`, or to other logs.\n2. \"Memory limit exceeded\" and \"No instances available\" [service errors](https://cloud.google.com/error-reporting/docs/service-errors).\n\nYou should handle errors and exceptions that occur during requests. Allowing\nsuch errors to crash your application process results in a\n[cold start](/run/docs/tips#starting_services_quickly) where a new container\ninstance is started up.\n\n### Viewing errors in Cloud Run\n\nThe \"Metrics\" tab of the [service detail page](/run/docs/managing/services#details)\nincludes a table showing the top errors for this service that\nError Reporting has detected and aggregated.\n\n### Viewing errors in Error Reporting\n\nYou can view errors after Error Reporting has aggregated them. For\ndetails, see [Viewing Errors](/error-reporting/docs/viewing-errors).\n\nTo review your current errors, go to the Error Reporting page in the\nGoogle Cloud console:\n\n[Go to Error Reporting](https://console.cloud.google.com/errors)\n\nFor more details\n----------------\n\nFor information, see the [Error Reporting documentation](/error-reporting/docs)."]]
