Add stop functionality for datadog about dd-sdk-android HOT 5 CLOSED

Hi @laurenyew-nytimes

I assume your main motivation here is to control costs and we already have two ways to solve this. The first one is the ability to sample at the SDK level (see documentation). The second one is our preferred solution: with Datadog you can ingest all your logs but only index the ones that are important. This way, the logs are still sent if you need them for an escalation for instance, but you do not pay the cost of indexing when you don't need them. The log management documentation does a great job at explaining this.

from dd-sdk-android.

from dd-sdk-android.

Hi @laurenyew-nytimes ,

So what you need in there is a way to pause and resume your Logger instance based on some criteria, correct me if I am wrong. In that case making publicly the stop method will not help as this will completely stop and wipe out all the SDK tooling meaning that you will have to re - initialize again with a new Config to resume it (too much trouble). Also making a resume/pause method will introduce an extra complexity in the SDK which we don't really want in this moment as we are in a middle of a Beta release. Instead what we propose to you is to go around this and to follow what we are doing in the GlobalTracer or GlobalRum classes. Basically having a Singleton class for your Logger and being able to switch to a Sampled logger whenever you want to switch OFF your logs will work fine in your case. Please let me know your thoughts.

from dd-sdk-android.

Hi @mariusc83, thanks for your reply. Turns out we no longer need the dynamic stop capability so we are good to go with the current Logger. Thanks!

from dd-sdk-android.

Glad that things solved for you there and in case you need that again try that approach, it should work. Thank you again for your feedback @laurenyew-nytimes .

from dd-sdk-android.