2 minutes read

POSTED Dec, 2021 dot IN Debugging

Debug your GitLab Workloads Natively with Sidekick!

Mustafa Ilker Sarac

Written by Mustafa Ilker Sarac

Software Engineer @Thundra


The past couple of months have been a roller-coaster thrill for us here in Thundra. First, let me summarize a couple of news before switching to our main topic; Sidekick Gitlab integration.

Recently we launched the next version of Foresight, our latest product focuses on your tests and CI pipelines. For Foresight, initially, we've covered GitHub Actions and workflows but support for other vendors is on the way i.e. GitLab, Bitbucket, and etc. We've always kept an eye on our beloved monitoring product Thundra APM. While we are happily onboarding new monitoring addicts to our powerful APM tool we keep improving the platform. And my last update before the main news is that we've polished our beloved start page, which our users hit right after their login or signup, you should check it out.

After more than enough forewords, let’s dive into Thundra Sidekick. We developed Sidekick with a purpose in mind that could help you debug your applications in their natural habitat which is live in production. In simple words, it helps you understand the reasons for smokes out of your planes' engines without landing it, parking it in a hangar, or even worse, before crashing it.

Let's go about how to start using Thundra Sidekick step-by-step.

1. Create a Thundra account

You need to have a Thundra account to start using Sidekick and many more. You can go to our signup page and create a free account to start using Sidekick right now.

2. Install the Thundra agent

Every magic has a backstage. You need to install our agent to your application and configure it. Right now it supports Java and Python workloads.

3. Connect the source code of your running application

This is the step that we are announcing to add GitLab support. Previously Sidekick was supporting workloads on GitHub only but since we are constantly improving our product, we added GitLab as one of our source providers. We have Bitbucket support next on the line. We have a quick screen capture below about how you can connect your source code to Sidekick.

4. Set a Tracepoint on Sidekick Web IDE

Right after you connect your source code and see your source tree on the left-hand side source explorer area, now you are ready to find the file and lines to set your tracepoints. Sidekick works like a read-only IDE and you can put your tracepoints to the code lines from the gutter area.

5. Run and play your app to hit the tracepoint

After your tracepoints are set, Sidekick can start to capture events around these points. You just need to replay the scenarios in your mind upon your application. Then you can come back to Sidekick and see the events and application's state.

6. Complete visibility by distributed tracing

Sidekick has Thundra's powerful agents behind. They are evolved to play really well in distributed environments. Using this advantage you can easily debug your microservice distributed architecture with Sidekick thanks to Thundra's advanced distributed tracing capabilities.

Now you can start debugging your applications written in Python or Java with Thundra Sidekick, NodeJS is on the way. We provide a sample application for you to start easily and grasp the concepts behind it. Whether you use GitHub or GitLab to store your code, Sidekick works well and is ready for your service.

If you have any questions, you can directly contact our engineering team through our community slack, support@thundra.io, or by sending us a message through our contact us page.

Thundra offers end-to-end observability for the full software development life cycle. From development to production, Thundra’s products help you understand your application behavior and troubleshoot issues before they become problems or affect your end-users. If you still haven’t taken a step into Thundra’s world, you can start your journey here.