Deployment Integrations
On-premise Integrations
Platform Integrations

Trace Configurations

Configuring Trace Plugin

Disabling Request/Response Tracing for Lambda

By default, request and response are traced but can be disabled with environment variable configuration.

To disable tracing request set the thundra_agent_lambda_trace_request_skipenvironment variable to true

Configuration via Environment Variable
thundra_agent_lambda_trace_request_skip: true

To disable tracing response set the thundra_agent_lambda_trace_response_skipenvironment variable to true

Configuration via Environment Variable
thundra_agent_lambda_trace_response_skip: true

Disabling trace plugin using environment variables

Configuration of Trace Plugin via Environment Variables
...
environment_variables:
thundra_agent_lambda_trace_disable: true
...

Trace Configuration of Automatically Supported Integrations

Configuring AWS SDK Trace

Masking SQS Messages

You can mask sent SQS message at client side which calls AWS SDK by setting following environment variable:

thundra_agent_trace_integrations_aws_sqs_message_mask: true

Masking SNS Messages

You can mask sent SNS message at client side which calls AWS SDK by setting following environment variable:

thundra_agent_trace_integrations_aws_sns_message_mask: true

Masking DynamoDB Statements

You can mask sent DynamoDB statements at client side which calls AWS SDK by setting following environment variable:

thundra_agent_trace_integrations_aws_dynamodb_statement_mask: true

Masking Lambda Payload

You can mask Lambda invocation payload at client side which calls AWS SDK by setting following environment variable:

thundra_agent_trace_integrations_aws_lambda_payload_mask: true

Unmasking Kinesis Records In Event

By default incoming Kinesis records at triggered lambda is not traced. You can enable sending Kinesis records in request by setting following environment variable:

thundra_agent_trace_integrations_aws_kinesis_record_unmask: true

Unmasking Firehose Records In Event

By default incoming Firehose records at triggered lambda is not traced. You can enable sending Firehose records in request by setting following environment variable:

thundra_agent_trace_integrations_aws_firehose_record_unmask: true

Enabling CloudWatch Log Messages In Event

By default incoming CloudWatch logs at triggered lambda is not traced. You can enable sending CloudWatch logs in request by setting following environment variable:

thundra_agent_lambda_trace_cloudwatchlog_request_enable: true

Disabling Sending AWS SDK Trace

By default, tracing AWS SDK calls is enabled, but can also be disabled as is required through configuration. You just need to set thundra_agent_trace_instrument_integrations_aws_sdk_disable to true

Configuring HTTP Trace

Masking HTTP Request Body

You can mask http request body at client side by setting following environment variable:

thundra_agent_trace_integrations_http_body_mask: true

Disabling Sending HTTP Trace

Thundra traces HTTP calls by default. However, you may disable it using environment variables. You can set thundra_agent_trace_integrations_http_disable environment variable to true for this purpose.