Datadog collects a lot of errors. It’s critical to the health of your system to monitor these errors, but there can be so many individual error events that it’s hard to identify which ones matter the most and should be fixed first.
Error Tracking makes it easier to monitor these errors by:
Error Tracking processes errors collected from the browser by the RUM SDK (errors with source origin).
To quickly get started with error tracking:
v1.11.5+version of the RUM Browser SDK.
The source code of some applications is obfuscated or minified when deployed to production for performance optimization and security concerns. The consequence is that stack traces of errors fired from those applications are also obfuscated, making the troubleshooting process much more difficult because the stack traces cannot be used to understand which file and which line of code are responsible for a given error.
Datadog allows you to securely upload your source maps to deobfuscate your stack traces:
package.jsonfile, you must use the
v0.5.2version and onwards of the CLI.
datadog-ci sourcemaps upload /path/to/build/directory \ --service=my-service \ --release-version=v35.2395005 \ --minified-path-prefix=https://hostname.com/static/js
For more information about CLI parameters, see the official Github repository.
sourcesContentattribute in your source maps is not empty before uploading them.