In order to start debugging with Thundra Sidekick, one of the pre-requisites is to instrument an application and select it via Thundra Sidekick dashboard. Applications and tracepoints area let developers manage their applications and tracepoints set on those applications.
After you successfully instrument your application, you'll need to select the applications that you'll work on during your debugging session. You can open the application selection screen by clicking the pencil button at top-right.
Thundra Sidekick Application Select Screen
Selecting Applications to Debug
After you click on the pencil button, you'll see the below screen to select the applications you want to debug. When you select an application, you'll be automatically select the all instances of that application.
Thundra Sidekick - Selecting Applications
Here you'll see all the applications with their identifying tags. You'll also see that how many instances of this application are live now and how many tracepoints are currently active on the application. Clicking on the "Done" button will take you to the previous screen this time showing the selected applications. See below:
Thundra Sidekick - Applications Selected
Now, you can set up a tracepoint by clicking on the gutter area on code editor area. You can further edit your application selection by clicking on the pencil button on top-right.
This section shows the list of active tracepoints by adding some inline action buttons with them.
Thundra Sidekick - Tracepoints List
By hovering on any of the tracepoints in this table, you'll see the action buttons for a tracepoint as below:
Thundra Sidekick - One Tracepoint with Action Buttons
The action buttons in a row is useful for the following jobs respectively from left to right:
Locating the tracepoint in the source code on code editor area
Enabling/disabling the tracepoint (Enable if disabled, disable if enabled)
Editing the tracepoint
Removing the tracepoint
Editing a tracepoint
We may want to make the tracepoint conditional by defining a condition to take a snapshot during code execution. We may want to change the default expiration settings of the tracepoint or we may want to remove the distributed tracing connection of a particular tracepoint using the "Edit Tracepoint" modal. When clicked save, our tracepoint will be active with the new configuration.