RUM Errors
Datadog の調査レポート: サーバーレスの状態 レポート: サーバーレスの状態

RUM Errors

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

Front-end errors are automatically collected with Real User Monitoring (RUM). The error message and stack trace are included when available.

Error Origins

Front-end errors are split in 3 different categories depending on their error.origin:

  • network: XHR or Fetch errors resulting from AJAX requests. Specific attributes to network errors can be found in the documentation
  • source: unhandled exceptions or unhandled promise rejections (source-code related)
  • console: console.error() API calls

Facet Collected

AttributeTypeDescription
error.originstringWhere the error originates from (i.e. console, network, etc.)
error.kindstringThe error type or kind (or code in some cases).
error.messagestringA concise, human-readable, one-line message explaining the event.
error.stackstringThe stack trace or complementary information about the error.

Network Errors

Network errors include information about the failing HTTP request. Hence, the following facets are also collected:

AttributeTypeDescription
http.status_codenumberThe response status code.
http.urlstringThe resource URL.
http.url_details.hoststringThe HTTP host part of the URL.
http.url_details.pathstringThe HTTP path part of the URL.
http.url_details.queryStringobjectThe HTTP query string parts of the URL decomposed as query params key/value attributes.
http.url_details.schemestringThe protocol name of the URL (HTTP or HTTPS)

Source Errors

Source Errors include code-level information about the error. More information about the different error types can be found in the MDN documentation.

AttributeTypeDescription
error.kindstringThe error type or kind (or code in some cases).

Further Reading