Automatically reporting errors
You can emit an error from a Cloud Function to
Error Reporting
as shown below:
If you would like more fine-grained error reporting, you can use the
Error
Reporting client
libraries
.
You can view the reported errors in
Error Reporting
in the GCP Console. You can also see the errors reported from a
particular function when you select it from the
list of functions
in the GCP Console.
Uncaught exceptions produced by your function will appear in Error Reporting.
Note that some types of uncaught exceptions (such as those thrown
asynchronously) will cause a
cold
start
to occur upon
a future function invocation. This increases the amount of time your function
will take to run.
Manually reporting errors
Sending to Cloud Logging
The
error
function from the Cloud Functions
logger
SDK will report errors to both Cloud Logging and
Error Reporting
. To include more context from the error as
structured data
, pass an error object as the second argument:
} catch (err) {
// Attach an error object as the second argument
functions.logger.error(
"Unable to read quote from Firestore, sending default instead",
err
);
}