Origin detection is enabled for non-kubernetes environemnts

[bwebster]

When trying to upgrade to the latest version - v5.7.0, we noticed that we are now getting a new c tag on all metrics. This appears to be related to origin detection for Kubernetes introduced in #310.

Having origin detection enabled by default was surprising for two reasons, 1) we are not using Kubernetes, and 2) I think it would have produced high cardinality tags on all our metrics which seems like it could have ballooned our bill.

It seems like the documentation either needs to be updated and this change needs to be loudly called out, or it should be disabled by default or somehow only enabled when kubernetes has been detected?

[mwdd146980]

Hi @bwebster, thanks for bringing this up! I've created a PR to add a call out that all our dogstatsd client libraries (not just the Ruby one) have origin detection enabled by default, but keep in mind that the Agent has it disabled by default (ref). You should not see an increase in tag cardinality if you have not enabled origin detection on the Agent.

I also wanted to mention that origin detection is possible for non-Kubernetes containerized environments, as mentioned here.

[bwebster]

Thanks for the clarification, and for updating the docs!

If I'm understanding, the docstatsd client will emit metrics with the origin detection tags, but it's up to the agent and it's configuration if those get propagated through?

[mwdd146980]

If I'm understanding, the docstatsd client will emit metrics with the origin detection tags, but it's up to the agent and it's configuration if those get propagated through?

Yep!

[bwebster]

Great. Thanks for the quick response.