logging behavior when API is "disabled"
belm0 opened this issue · comments
I have some situations where disabling the API is normal-- e.g. I only want analytics on certain platforms or for certain builds. However, the two ways I know of to disable the API (dryRun = true, or set tracking code null) both result in spamming the log at WARNING level on every event.
I could work around this by setting log level to ERROR, which happens to be unused currently.
Would it be reasonable though to only log the use of dry-run or lack of tracking code once?
I'm submitting a pull request to make the desktop implementation match Android SDK behavior as far as logging dry-run and opt-out: dry-run is verbose, and opt-out is not logged.