Changing local root - Thundra APM

Search…

Welcome to Thundra APM

Switch to Foresight Docs

Getting Started

Getting Started with Thundra APM

Quick Start Guide

Performance Benchmarks

Thundra Web Console

Functions List Page

Function Details Page

Invocation Detail Page

Applications Page

Applications Detail Page

Custom Dashboard Page

Architecture Page

Unique Traces Page

Unique Trace Details Page

Operations Page

API Details Page

Account & Settings

Error Inspector Page

Node.js

Integration Options for Node.js SDK

Integration Options for Node.js SDK in Containers and VMs

Configuration Options for Node.js

Enrich Tracing in Node.js

AWS Lambda Debugging for Serverless Node.js

TTD (Time Travel Debugging) for NodeJS

Node.js Example Projects

FAQ for Node.js SDK

Python

Integration Options for Python SDK

Configuration Options for Python

Enrich Tracing in Python

AWS Lambda Debugging for Serverless Python

Python Example Projects

FAQ for Python SDK

Java

Integration Options for Java SDK

Integration Options for Java SDK in Containers and VMs

Configuration Options for Java

Enrich Tracing in Java

AWS Lambda Debugging for Serverless Java

Java Example Projects

FAQ for Java SDK

Go

Integration Options for Go SDK

Configuration Options for Go

Enrich Tracing in Go

Golang Example Projects

.Net

Integration Options for .NET SDK

Integration Options for .NET SDK in Containers and VMs

Upgrading from v1.x to v2.x

Configuration Options for .NET SDK

Enrich Tracing in .NET

.NET Example Projects

FAQ for .NET SDK

Web Frameworks

Debugging

Time-Travel Debugging

AWS Lambda Debugger

IDE Integrations

Changing local root

IntelliJ IDEA Plugin

Observability

Root Cause Analysis of Outliers

Architectural View to Check The Issues at a Glance

Tracking Serverless Transactions End-to-End

Staying Aware of Issues with Alerts

How to Respond Alerts in Thundra

Reducing Data Size with Sampling

Chaos Engineering with Thundra

Three Pillars of Observability

Seamless Monitoring

Digging Observability Data with Thundra Queries

Performance

Zero Overhead with Lambda Extensions

Zero Overhead with Asynchronous Monitoring

Dealing with Cold Starts

Deployment Integrations

Serverless Framework

Step by Step Migration Guide from Epsagon to Thundra

Powered By GitBook

Changing local root

While debugging a lambda function using Thundra's Online Debugger, if the local root does not match the remote root; VSCode might not be able to resolve the breakpoint locations. If you put a breakpoint in your Lambda function, the function is connected however debugger is not stopping at the breakpoint; the problem might be related to the local root.
To solve this issue you can use the "Thundra: Change local root" command provided by the Thundra's VSCode extension.
In the below example we have a directory opened in VSCode, containing two separate Lambda functions.
When you deploy these two lambda functions and try to debug the first Lambda function using Thundra's online debugger, you will see the function will not stop at the breakpoint.
That's because VSCode couldn't resolve the incoming breakpoint location in the current workspace. To resolve this issue, you can use "Thundra: Change local root" command.
Since we want to debug the first lambda function we can set the local root for the debugger to "./firstLambda/" directory.
After setting the local root, when you try to start the debugger again and invoke the function; you will see that the function will stop at the breakpoint that we have put.

IDE Integrations - Previous

Next - IDE Integrations

IntelliJ IDEA Plugin

Last modified 1yr ago

Copy link