help reducing log pollution

[vincentcr]

Summary

It would be great if the Amplitude experiment SDK config accepted a logger parameter so we could format error logs coming out of Amplitude to conform to our logging system.

Motivations

We use Datadog and the rest of our logs are emitted as JSON lines. Amplitude dumps stack traces directly to stdout and DD treats each line of the trace as a separate log entry. This not only pollutes our logs but makes hard to analyze any potential issue with Amplitude in particular.

This issue would be resolved if we could configure the logging interface the Amplitude SDK uses to emit errors. Launch Darkly for example has a logger parameter in its init function.

[bgiori]

@vincentcr Thanks for the feedback! Agreed. I've added this to our backlog.

[calm-mlin]

Any update on this? Looks like Amplitude might have had an outage recently and our logs got severely spammed by the console.xxx() used by this library. It's fairly common to have an agent that reads stdout and treats each lines as a single log entry.