cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to disable mobile app user actions "touch on" capture

AhmedSamy
Visitor

Hi Community,

Kindly I am using android Gradle for mobile user experience, and we had a request to disable the capture of user touch on sensors due to security reasons from code level (and not using masking) for example I don't want to capture actions like "touch on 1"

 

Can you please support with the exact Gradle configurations to disable touch on listener sensors?

Should the below configuration work:

---------
dynatrace {
    configurations {
        sampleConfig {
            userActions {
                sensors {

                    // fine-tune the sensors if necessary
                        UserActionSensors {
                            Click false
                            itemClick false
                            itemSelect false
                        }
                    }
                }
            }
        }
    }
---------


Thanks,
Ahmed

10 REPLIES 10

Julius_Loman
DynaMight Legend
DynaMight Legend

Hi @AhmedSamy ,


I'd highly recommend using user action masking as described here . 
You can also exclude certain classes from autoinstrumentation (PIN code entry for example).

Would that solve your case?



Certified Dynatrace Master | Alanata a.s., Slovakia, Dynatrace Master Partner

Mizső
DynaMight Leader
DynaMight Leader

Hi @AhmedSamy ,

 

Here is an example for user action masking rule which wa mentioned by @Julius_Loman.

 

Both solutions are perfect.

 

Mizs_0-1666597492180.png

 

Mizs_2-1666597600373.png

 

I hope it helps. Have nice day

 

Best regards,

 

Mizső

 

 

 

Certified Dynatrace Professional

@Mizső Well, the user action naming rule just renames the action. But the information is still capture. OneAgent SDK 1.249 includes a feature which masks automatically the user action names if the name may contain sensitive information - if content description (android)  or element text is about to be used in the captured name. 

Certified Dynatrace Master | Alanata a.s., Slovakia, Dynatrace Master Partner

Hi @Julius_Loman,

 

Thanks for the clarification and the information.

Can you help me where can I find the release notes or documnetation for OneAgent SDK 1.249? I would like to forward it for the affected mobile app developers.

 

Thanks in adavence. Have nice day.

 

Best regards,

Mizső

Certified Dynatrace Professional

Hi @Julius_Loman,

 

I'am blind. I have to learn use the communtiy. 😂

 

Thnaks.

 

Best regards,

 

Mizső

Certified Dynatrace Professional

Mizső
DynaMight Leader
DynaMight Leader

Hi @Julius_Loman,

 

Is there any similar solution for iOS?

 

Thanks in advance.

 

Best regards,

 

Mizső 

Certified Dynatrace Professional

Patrick_H
Dynatrace Champion
Dynatrace Champion

there are 2 different ways to approach it on iOS:
* disable instrumentation of e.g. Button touches by configuring the controls you don not want to get touch actions from - see DTXExcludedControls in this help page: https://www.dynatrace.com/support/help/shortlink/ios-configuration-keys
* use custom control titles for dedicated buttons instead of having them autogenerated: https://www.dynatrace.com/support/help/shortlink/ios-oneagent-sdk#custom-control-names

iOS help: https://www.dynatrace.com/support/help/shortlink/ios-hub

Mizső
DynaMight Leader
DynaMight Leader

Hi @Patrick_H,

 

Thanks very much your swift reaction and the information.

 

Have a nince day.

 

Best regards,

 

Mizső

Certified Dynatrace Professional

Thomas_Wirth1
Dynatrace Champion
Dynatrace Champion

Hey @AhmedSamy,

 

When you want to only deactivate sensors that generate a "Touch on" user action (and keep the other user actions), then you have to use the following configuration:

 

dynatrace {
    configurations {
        sampleConfig {
            userActions {
                sensors {
                    click false
                    itemClick false
                    itemSelect false
                    menuClick false
                    optionSelect false
                }
            }
        }
    }
}

 

It almost has the same effect as deactivating user action monitoring completely, because the plugin only instruments OnPageChangeListener and OnRefreshListener classes.

 

 

But I would also recommend the option(s) suggested by @Julius_Loman. Masking via the "namePrivacy" options guarantees that the agent will not use any sensitive information for user action monitoring.

Featured Posts