[RUM-6160] Added errorSource property in LogEvent for mapping

[marco-saia-datadog]

What does this PR do?

Adds Error Source property to Log Events, so that it can be used in custom Log Event Mappers.

Example

configuration.logEventMapper = logEvent => {
    if (logEvent.source === ErrorSource.CONSOLE) {
        return null;
    }

    return logEvent;
};

To be discussed

This PR adds an extra parameter source to the public API DdLogs.error():

• message: string
• errorKind?: string
• errorMessage?: string
• stacktrace?: string
• context?: object
• fingerprint?: string
• source?: ErrorSource

Another option would be to add a custom Datadog attribute to the context and parse it internally (perhaps removing it before making the native call.

Finally, another option would be to refactor the implementation to hide the parameter from the public API.

Please let me know what you think about this.

Context

Currently, when trackErrors is set to true, we attach our error-reporting logic to:

• Console Errors (via console.error)

• React Native Global Error Handler (via ErrorUtils.setGlobalHandler)

In some cases, users might not want to report console errors, and we currently don’t have a way to disable this behaviour.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests
• Make sure you discussed the feature or bugfix with the maintaining team in an Issue
• Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)
• If this PR is auto-generated, please make sure also to manually update the code related to the change

[datadog-datadog-prod-us1]

🟠 Code Quality Violation

Unexpected console statement. (...read more)

Debugging with console is not considered a bad practice, but it's easy to forget about console statements and leave them in production code. There is no need to pollute production builds with debugging statements.