回報錯誤

自動回報錯誤

您可以如下所示,從 Cloud 函式發出錯誤至 Error Reporting

Node.js

// These WILL be reported to Error Reporting
throw new Error('I failed you'); // Will cause a cold start if not caught

Python

@functions_framework.http
def hello_error_1(request):
    # This WILL be reported to Error Reporting,
    # and WILL NOT show up in logs or
    # terminate the function.
    from google.cloud import error_reporting

    client = error_reporting.Client()

    try:
        raise RuntimeError("I failed you")
    except RuntimeError:
        client.report_exception()

    # This WILL be reported to Error Reporting,
    # and WILL terminate the function
    raise RuntimeError("I failed you")


@functions_framework.http
def hello_error_2(request):
    # These errors WILL NOT be reported to Error
    # Reporting, but will show up in logs.
    import logging
    import sys

    print(RuntimeError("I failed you (print to stdout)"))
    logging.warning(RuntimeError("I failed you (logging.warning)"))
    logging.error(RuntimeError("I failed you (logging.error)"))
    sys.stderr.write("I failed you (sys.stderr.write)\n")

    # This is considered a successful execution and WILL NOT be reported
    # to Error Reporting, but the status code (500) WILL be logged.
    from flask import abort

    return abort(500)

如果您需要更詳細的錯誤報告,可以使用錯誤報告用戶端程式庫

您可以在 GCP 管理中心的 Error Reporting 中查看回報的錯誤。當您從 GCP Console 的函式清單選取特定函式時,也可以查看從該函式回報的錯誤。

您的函式產生了未捕捉到的例外狀況會顯示在 Error Reporting 中。請注意,某些未擷取的例外狀況類型 (例如非同步擲回的例外狀況) 會在日後函式叫用時發生冷啟動。這會增加函式執行所需的時間。

手動回報錯誤

傳送至 Cloud Logging

Cloud Functions 記錄器 SDK 的 error 函式會將錯誤回報至 Cloud Logging 和 Error Reporting。如要加入錯誤中更多的背景資訊做為結構化資料,請傳送錯誤物件做為第二個引數:

} catch (err) {
  // Attach an error object as the second argument
  functions.logger.error(
    "Unable to read quote from Firestore, sending default instead",
    err
  );
}