Support disabling the capture SDK

[pyricau]

There doesn't seem to be a way to turn off the SDK? i.e. once configured, it's running. Ideally we could have a flag and live turn it on / off, which would make us feel safer about rolling it out

[mattklein123]

@pyricau disable semantics are a bit complicated. What is the behavior that you want to see? Something like no more network traffic and all logging functions become NOP? Something else?

[mattklein123]

(We have an internal mechanism to kill all network traffic already but would want to better understand what else you would want exposed.)

[murki]

This is particularly important for the case of enabled-by-default, disabled-by-request, since it makes sense that the SDK would be initialized early on and potentially disabled on demand later. We will work on adding this.

[pyricau]

Something like no more network traffic and all logging functions become NOP? Something else?

Yes, and any / all background threads as well.

We've unfortunately had the experience of some other observability vendors that should remain unnamed creating issues in prod, so we're now very cautious and like the ability to turn things off, especially in a context where our app runs all day in foreground so waiting for the next app start doesn't cut it.