Consider a better default config file for your container.

[SleepyBrett]

I recently did an upgrade from a fairly old version of the tool (4.x) to 11.x and found that with the inclusion and default use of your default config file my deployment went from working to spewing errors right and left.

It's my opinion that all sinks should probably have an enabled true/false flag but also maybe not providing values that cause them to activate by default would be nice. A short list of things I can remember modifying the config file to disable, splunk, falconer, signalfx, gprc, xray...

[daviddyball]

I also just came across this issue. I wanted only the SignalFX sink, but because the default config ships with a DataDog API Key set (to fart) it started crash-looping because it couldn't auth with DataDog correctly.

Does setting the env-var VENEUR_DATADOGAPIKEY to "" work at disabling the sink?

[daviddyball]

Raised a PR with no sinks enabled by default: #733