UploadWorker Canceled about dd-sdk-android HOT 8 CLOSED

Hello @ichsanachmad! It is not quite clear what is the issue you have. Do you mean that you cannot see any data sent by Android SDK in the Datadog dashboard? If yes, can you please share your setup snippet and make sure that you configured SDK to use the right datacenter?

from dd-sdk-android.

some of my log not showing in the dashboard sir @0xnm

from dd-sdk-android.

@ichsanachmad Please provide the SDK setup code snippet and tell which datacenter you are using. Also if only some logs are missing, is it possible for you to identify the common pattern for the logs which are missing?

You may want also to set SDK logcat verbosity to DEBUG by calling Datadog.setVerbosity(Log.DEBUG) in order to explore the logcat for the messages from our SDK.

from dd-sdk-android.

i'm using EU1 data center, here's my setup @0xnm

        if (Datadog.isInitialized()) {
            Datadog.stopInstance()
        }
        isConvertKeyToCamelCase = autoConvertKeyToCamelCase
        val envName = prefs.getAppEnvironment()

        val datadogConfig = Configuration.Builder(
            clientToken = clientToken,
            env = envName,
            service = prefs.getAppName(),
        )
            .setCrashReportsEnabled(true)
            .useSite(datadogSite)
            .build()

        Datadog.initialize(
            context = context,
            configuration = datadogConfig,
            trackingConsent = TrackingConsent.GRANTED,
        )

        val logsConfig = LogsConfiguration.Builder().build()
        Logs.enable(logsConfig)

        datadogLogger = Logger.Builder()
            .setNetworkInfoEnabled(true)
            .setService(prefs.getAppName())
            .setLogcatLogsEnabled(true)
            .setBundleWithTraceEnabled(true)
            .setBundleWithRumEnabled(enableRum)
            .setName(prefs.getAppName())
            .build()

        if (isConvertKeyToCamelCase) {
            datadogLogger?.addTag(AttributeKeyCamelCase.APP_NAME.key, prefs.getAppName())
            datadogLogger?.addTag(AttributeKeyCamelCase.APP_ID.key, prefs.getAppId())
        } else {
            datadogLogger?.addTag(AttributeKeySnakeCase.APP_NAME.key, prefs.getAppName())
            datadogLogger?.addTag(AttributeKeySnakeCase.APP_ID.key, prefs.getAppId())
        }

        if (enableRum) {
            GlobalRumMonitor.get()
            Rum.enable(
                rumConfiguration = RumConfiguration
                    .Builder(applicationId)
                    .trackUserInteractions()
                    .trackLongTasks()
                    .trackBackgroundEvents(true)
                    .useViewTrackingStrategy(MixedViewTrackingStrategy(true))
                    .build(),
            )
        }

from dd-sdk-android.

@ichsanachmad Thanks for posting setup snippet. It looks okay, but I have few questions:

• What is the purpose of calling Datadog.stopInstance? Do you setup Datadog SDK in the Application#onCreate?
• What is the purpose of calling GlobalRumMonitor.get() and not using the return value? Anyway, it should be called only after RUM is enabled.

Do you see any pattern for the expected logs not showing up in the Datadog dashboard? Like maybe logs when application is in the background, etc.

What is the volume of the logs not showing up? Is it minority or majority of the logs sent?

Do you see any warnings/errors in the Logcat (apart of the stacktrace you've posted originally) if you set Datadog.setVerbosity(Log.DEBUG) when initializing the SDK?

from dd-sdk-android.

after i do some changes in the way init, i think everything run as expected by changing init call to Application#onCreate sir, @0xnm but some of majority logs missing, the pattern is like custom log and somethings like okhttp log is showing up, but still some of majority log still missing

from dd-sdk-android.

Unfortunately it is still not clear what is the pattern for the logs missing, given that some of them are in fact sent. If you don't see any warnings/errors in the Logcat from Datadog SDK, all of them should be delivered (the stacktrace in the original message should have no impact).

If you want us to analyze the data on the Dashboard side, you can open a ticket using the channels provided here, specifying your Org details and referencing this issue.

from dd-sdk-android.

Hello @ichsanachmad! I'm closing this issue due to inactivity. If you have more questions, don't hesitate to reopen it.

from dd-sdk-android.