Error Reporting can report stack traces collected from Rust applications
using std::backtrace.
To enable, set the RUST_BACKTRACE=1 environment variable and
make sure debug symbols are enabled.
For more information, see ReportedErrorEvent.
]]>You can view the available regional endpoints for the Error Reporting API on the REST reference pages. For an example, see Method: projects.events.list.
]]>You can use the Error Reporting API MCP server to let agents and AI applications interact with your error data. This feature is in Preview.
]]>Error Reporting can now analyze log entries that have been routed to a log bucket in a non-global region, provided the log sink is in the same project as the log bucket.
]]>Error Reporting can now analyze logs routed by project sinks to different projects than the source project. For more information, see Route logs to supported destinations.
]]>Announcing a common navigation pane in the Cloud console for Logging, Monitoring, Trace, and Error Reporting. When you are troubleshooting an issue, the new navigation pane simplifies accessing the pages you need to explore different types of telemetry:
You can continue to use the search bar to locate pages in the Cloud console and to find documentation.
]]>The Error Reporting API is now generally available. For more information about the API, see Overview.
]]>Troubleshooting errors with Duet AI assistance is now generally available.
]]>You can now view error groups on your custom dashboards. This feature is GA. For information when using the Cloud Console, see Display logs and errors on a custom dashboard. For information about using the API, see Dashboard with an ErrorReportingPanel widget.
]]>Error Reporting now supports Cloud Run Jobs as a monitored resource type. For more information, see Supported monitored resources.
]]>Troubleshooting errors with Duet AI assistance is now available in Preview.
]]>Error Reporting now reports recent application errors for Google Kubernetes Engine services and clusters on a new App Errors tab.
In the Error Reporting page's resource filter, you can now filter GKE resources by location, cluster, namespace, and container or pod. For more information, see Filter errors.
]]>Error Reporting now reports recent application errors for Google Kubernetes Engine workloads of type Deployment or Pod. Go to Kubernetes Engine in the Google Cloud console, and select Workloads. From the overview list, select an entry with type "Deployment" or "Pod" to see details about the workload, including recent application errors.
Errors generated by GKE applications (that is, applications with a
MonitoredResource type of k8s_container) now support additional labels for metadata extraction. The values of the following labels will now appear in the resource filter and in various tables and displays on Error Reporting pages in the Google Cloud console:
app value from your GKE YAML configuration is now used for the primary resource label (also referred to as "service").pod_name label of the k8s_container monitored-resource type is now used for the secondary resource label (also
referred to as "version").We continue to support the use of the YAML metadata labels k8s-pod/serving_knative_dev/service and
k8s-pod/serving_knative_dev/revision. These labels are prioritized for users already using them over the k8s-pod/app and pod_name labels described in this note. But we encourage users to begin using the new labels.
If you do not set the k8s-pod/app label, GKE application errors continue to use the default service name of gke_instances.
On the Error Reporting page, use the new resource filter to filter error groups by resource type. For more information, see Filter errors.
]]>Error Reporting is a Virtual Private Cloud (VPC) supported service.
]]>The Logs Explorer now shows an Error Group button for log entries that are part of error groups. Click the button to access grouping details or to change which log entries the Logs Explorer shows. For more information, see Find log entries with error groups.
]]>Preview: You can now get notification recommendations and insights for Error Reporting. For more information, see Error Reporting notification recommender and insights.
]]>Error Reporting now supports Webhooks and Slack as notification channels. For more information, see Create notification channel.
]]>Error Reporting notifications has been upgraded to use the Alerting infrastructure. For more information, see the Notifications guide.
]]>Service Errors is now available Generally Available (GA). Service Errors automatically captures and groups Google Cloud service errors and notifies you when these errors occur. For more information, refer to the Managing Service Errors documentation.
]]>Error Reporting has been updated to only analyze logs that are stored in global buckets in the same project where they are ingested. For more information, see Using Error Reporting with regionalized logs.
]]>Error Reporting now infers the service name and version from the logEntry fields named k8s-pod/serving_knative_dev/service and k8s-pod/serving_knative_dev/revision for Knative Serving labels on Cloud Run on Google Kubernetes Engine. This replaces the current default value of gke_instances for service name.
API
Error events written as instances of ReportedErrorEvent generate properly formatted error messages in Stackdriver Logging.
Error detection for Python applications has been improved. You might see more newly detected error groups or receive more notifications.
]]>Resolution Status features are now Generally Available. You can now assign a status to your error groups, making it easier to triage errors.
]]>IAM roles: Stackdriver Error Reporting IAM roles are now available. See Error Reporting IAM roles.
]]>Error filters: You can now filter errors by custom text in addition to filtering by time, service, and version.
]]>Cloud Functions: Cloud Functions automatically reports unhandled JavaScript exceptions to Stackdriver Error Reporting.
]]>