Some CUSTOM Actions not reported about dd-sdk-android HOT 8 CLOSED

Hi @mszerling-ynd ,
One of the limitation of our SDK is that RUM Actions, Errors and Resources are only reported when a View is active (this is a topic we're working on to make sure all information are correctly reported). One of my guess is that those actions are happening between the first fragment's onPause and the next one's onResume. What is strange is that nothing is showing up in the LogCat, did you enable the SDK's logs. You can do so using the following line after you initialised the SDK:

         Datadog.setVerbosity(Log.VERBOSE);

from dd-sdk-android.

One of my guess is that those actions are happening between the first fragment's onPause and the next one's onResume

The addUserAction method is called while the first fragment is still active

What is strange is that nothing is showing up in the LogCat

Something is shown, but it's just some logging related to syncing with the backend (no errors/warnings related to actions)

from dd-sdk-android.

Another option that might explain this is that only one action can be active at a given time (and action's span can extend with Resources and errors), meaning that some actions might be dropped because of that. We don't have yet any log for this situation but we'll add one very soon, and that way we'll be able to check if this is the case in your app.

from dd-sdk-android.

In our app there aren't really any bursts (multiple consecutive actions) fired one after another (if that's helpful for debugging).

Just one more comment on this:

The addUserAction method is called while the first fragment is still active

this refers to when the method is called but from what I see in the source code of the sdk the action is processed asynchronously by some executor service so maybe when it is being processed there is no active "View" (fragment in this case).

from dd-sdk-android.

Ok, well we'll add more logs to better understand the situation anyway. And indeed because calls to our API need to return fast, we delegate the creation of the Event to a background thread so it can explain that the action is dealt with after the view is stopped.

from dd-sdk-android.

Hello @mszerling-ynd ,

We have added additional logging in the form of warning when action if dropped if another action is still active for the certain view, hope it will help debugging the issue. The change will be available in the next release.

from dd-sdk-android.

Hello, So what are we supposed to do when getting this message?
RUM Action (CUSTOM on {Some Action Name}) was dropped, because another action is still active for the same view
Calling GlobalRum.get().stopUserAction(map); prior to addUserAction does not seem to help.
Also why does an action have any sort of "active" status. Isn't it supposed to be an event-like thing?

from dd-sdk-android.

Hi @eldarcbb,
RUM Actions can be active as we link resources and errors to the active action, in an attempt to find correlations that will provide valuable information in Datadog (Error X is caused by Action A, …).
Since version 1.10.0, when you add a custom action, it will never be dropped anymore, even when a previous action is still active.

from dd-sdk-android.