Damon

From your mention of AWS Lambda, I'm assuming your use case is within the AWS environment. If so, I would recommend leveraging security groups to restrict access to mongobetween instead...

Unfortunately we only support SCRAM authentication at the moment. We're open to PRs to get this added, but this isn't on our roadmap for the time being.

Instead of modifying the namespace (thus changing the metric name), I would prefer to instead leverage tags on the metric to append additional information. We do have a "backdoor" way...

We have documentation on setting mongobetween in our [README](https://github.com/coinbase/mongobetween/blob/master/README.md) -- from your application, you would connect to mongobetween in the way it was setup. e.g., if you follow the TCP...