Using the Online Debugging with Java Lambda Functions
Integrate Thundra Java agent with your Lambda function using one of the available integration options.
Enable the online debugging using by adding the
thundra_agent_lambda_debugger_auth_token environment variable
Specify a session name if needed (as long as you don't have multiple concurrent debug sessions you don't have to specify a session name, default value just works fine)
Start the debug session in your IDE and invoke your function, Thundra Debugger will establish the connection between the IDE and your lambda function using your authentication token and the session name.
You can disable the Online Debugging once you completed your debugging session.
Fastest way of enabling Thundra debugger for a lambda function is setting the
thundra_agent_lambda_debugger_auth_token environment variable to the authentication token that you can get from the Thundra console. This way, Thundra will start your function in debug mode. You will be able to connect your function from your IDE to start the debugging session.
Online Debugging feature is disabled by default. However if you want to disable it explicitly, you can set
thundra_agent_lambda_debugger_enable environment variable to the false . In that case even if you have
thundra_agent_lambda_debugger_auth_token , online debugging will be still disabled.
In order to match the two end of an online debugging session which are your lambda function invocation and your local IDE, Thundra uses session names. When you enable the online debugging in your lambda function session name is set to the predefined value
default. If you want to use another session name you can specify it using the
thundra_agent_lambda_debugger_session_name environment variable.
Thundra broker establishes communication between your Lambda function and IDE. It receives data from Lambda function and forward to your IDE. To reduce overhead during this transmission process, you need to select a broker host that provides shortest path for your Lambda and IDE. Broker host need to be close to Lambda or your IDE location.
Thundra provides a broker host on Oregon by default. Moreover, we support different broker hosts listed below. You can select and set to
thundra_agent_lambda_debugger_broker_hostenvironment variable to reduce latency during debugging session.
debug.thundra.io (us-west-2 - Oregon)
debug-us-east-1.thundra.io (us-east-1 - N. Virginia)
debug-eu-west-2.thundra.io (eu-west-2 - London)
debug-ap-northeast-1.thundra.io (ap-northeast-1 - Tokyo)
Number of debug sessions for an account is limited for now. You can start 2 concurrent debug session at a time. You can contact us from email@example.com or intercom bubble on the right bottom corner of Thundra console if you want to increase your concurrent session limits.
The authentication token you get from the Thundra console. This field is required and there is no default value.
The unique session name to identify current debug session among the other concurrent debug sessions. The default value is "default".
The broker host address that Thundra connects to start a debug session with your IDE. The default value is "
The broker port that Thundra uses to connect the broker. The default value is 444.
The maximum amount of time in milliseconds that your function should wait until a debug session request is coming from the IDE. The default value is 60000.
Boolean value to enable Thundra debugger logs. The default value is false.
Boolean value to enable/disable to Thundra debugger. It can be set to the true to enable the debugger (authentication token environment variable should also be set), and setting it to the false disables the Thundra debugger.