When you use an APM tool, it can become the weakest point in your data security practices. While you're providing different security mechanisms such as MFA to control the access to your data, your monitoring tool can read and save it into its database (to help you of course).
Thundra is no exception. When you instrument your code with Thundra libraries, you're letting our code to run along with yours and gather data about the lifecycle of your serverless-centric transactions. After the execution ends, our libraries are reporting the data to our backend in order to let you troubleshoot the issues with your serverless-centric apps.
We, as Thundra, believe that we need to provide the as many configuration as possible to make you really control the data that you want to share with us. That's why, we are providing numerous masking possibilities in every language that we are providing libraries. When you mask a particular field and/or data, our libraries don't report this data to our backend. For example; when you set the following variable true, our libraries won't send the SQS messages in your applications but continue showing how long it took to receive the callback from SQS.
In order to use masking, you can consult to dedicated documentation for