Updating Thundra docs and adding link to channel (sst#1373)

Author: jayair

www/config.js

@@ -2,9 +2,10 @@ module.exports = {
   email: "hello@serverless-stack.com",
   home: "https://serverless-stack.com/",
   guide: "https://serverless-stack.com/#guide",
+  slack: "https://serverless-stack.slack.com/",
   twitter: "https://twitter.com/ServerlessStack",
-  slack: "https://serverless-stack.com/slack",
   forum: "https://discourse.serverless-stack.com/",
+  slack_invite: "https://serverless-stack.com/slack",
   newsletter: "https://serverless-stack.com/newsletter.html",
   examples: "https://serverless-stack.com/examples/index.html",
   github: "https://github.com/serverless-stack/serverless-stack",

www/docs/about.md

@@ -63,7 +63,7 @@ npx sst deploy --stage prod
 ## Join our community
 
 <div className={styles.communityPanels}>
-  <a className={styles.communityPanel} href={ config.slack }>
+  <a className={styles.communityPanel} href={ config.slack_invite }>
     <div className={styles.communityPanelIconSlack}>
       <i className="fab fa-slack"></i>
     </div>

www/docs/advanced/monitoring.md

@@ -3,6 +3,8 @@ title: Monitoring
 description: "Learn how to use services like Datadog, Sentry, Epsagon, and Lumigo to monitor the Lambda functions in your SST app in production."
 ---
 
+import config from "../../config";
+
 Once your app has been [deployed to production](../going-to-production.md), it's useful to be able to monitor your Lambda functions. There are a few different services that you can use for this. We'll look at them below.
 
 ## Datadog
@@ -95,32 +97,6 @@ export const handler = Sentry.AWSLambda.wrapHandler(async (event) => {
 
 For more details, [check out the Sentry docs](https://docs.sentry.io/platforms/node/guides/aws-lambda/).
 
-## Epsagon
-
-:::caution
-
-Epsagon is undergoing some changes after the acquisition by Cisco. We recommend using one of the other monitoring services.
-
-:::
-
-[Epsagon](https://epsagon.com) is an end-to-end [Application Monitoring Service](https://epsagon.com/) and can monitor the full lifecycle of your serverless requests.
-
-The Epsagon docs on [using a Lambda Layer](https://docs.epsagon.com/docs/getting-started/monitoring-applications/aws-lambda-layer) are incorrect. You'll need to install the Epsagon agent for your Lambda functions.
-
-``` bash
-npm install epsagon
-```
-
-And wrap your Lambda functions with their tracing wrapper.
-
-``` js
-const handler = epsagon.lambdaWrapper(function(event, context) {
-  // Lambda code
-});
-
-export { handler };
-```
-
 ## Lumigo
 
 [Lumigo](https://lumigo.io) offers a [Serverless Monitoring and Debugging Platform](https://lumigo.io/).
@@ -153,6 +129,10 @@ For more details, [check out the Lumigo docs on auto-tracing](https://docs.lumig
 
 To get started, [sign up for an account](https://console.thundra.io/landing/). Then [follow the steps in the quick start guide](https://apm.docs.thundra.io/getting-started/quick-start-guide/connect-thundra) to deploy their stack into the AWS account you wish to monitor.
 
+:::info
+Need help setting up? <a href={ config.slack_invite }>Join us on Slack</a> and head over to the <a href={ `${config.slack}app_redirect?channel=thundra` }>#thundra</a> channel. The Thundra team is ready to help.
+:::
+
 To enable Lambda monitoring, you'll need to add a layer to the functions you want to monitor. To figure out the layer ARN for the latest version, [check the badge here](https://apm.docs.thundra.io/node.js/nodejs-integration-options).
 
 With the layer ARN, you can use the layer construct in your CDK code.
@@ -183,8 +163,13 @@ if (!scope.local) {
 }
 ```
 
-For more details, [check out the Thundra docs](https://apm.docs.thundra.io/).
+For more details, [check out the Thundra docs](https://apm.docs.thundra.io/node.js/nodejs-integration-options).
 
+#### Time Travel Debugging
+
+Thudra also offers a feature called [Time Travel Debugging (TTD)](https://apm.docs.thundra.io/debugging/offline-debugging) that makes it possible to travel back in time to previous states of your application by getting a snapshot of when each line is executed. You can step over each line of the code and track the values of the variables captured during execution.
+
+To enable TTD in your SST app, you'll need to modify the esbuild config. [Check out the Thundra docs on this](https://apm.docs.thundra.io/node.js/ttd-time-travel-debugging-for-nodejs#using-with-sst).
 
 ## New Relic
 
@@ -214,3 +199,29 @@ if (!scope.local) {
   });
 }
 ```
+
+## Epsagon
+
+:::caution
+
+Epsagon is undergoing some changes after the acquisition by Cisco. We recommend using one of the other monitoring services.
+
+:::
+
+[Epsagon](https://epsagon.com) is an end-to-end [Application Monitoring Service](https://epsagon.com/) and can monitor the full lifecycle of your serverless requests.
+
+The Epsagon docs on [using a Lambda Layer](https://docs.epsagon.com/docs/getting-started/monitoring-applications/aws-lambda-layer) are incorrect. You'll need to install the Epsagon agent for your Lambda functions.
+
+``` bash
+npm install epsagon
+```
+
+And wrap your Lambda functions with their tracing wrapper.
+
+``` js
+const handler = epsagon.lambdaWrapper(function(event, context) {
+  // Lambda code
+});
+
+export { handler };
+```

www/docs/design-principles.md

@@ -125,7 +125,7 @@ cron.attachPermissions([
 
 ### Having an escape hatch
 
-We are continually working to improve the design of the SST constructs. Feel free to send us your feedback <a href={ config.slack }>via Slack</a> or <a href={ `mailto:${config.email}` }>email</a>.
+We are continually working to improve the design of the SST constructs. Feel free to send us your feedback <a href={ config.slack_invite }>via Slack</a> or <a href={ `mailto:${config.email}` }>email</a>.
 
 That said, you might run into cases where you are trying to do something that these constructs do not support. In these cases, you can fallback to using the native CDK constructs instead. This _escape hatch_ ensures that you won't be locked in to using SST's constructs.
 

www/docs/faq.md

@@ -59,7 +59,7 @@ SST has a couple of defaults, like a built-in linter, type checker, and bundler.
 
 You can disable the linter, provide your own TypeScript config, and disable bundling. You also don't have to use the higher-level constructs that SST has and just use the native CDK ones.
 
-If you hit a limitation, feel free to hop into our <a href={ config.slack } target="\_blank">Slack community</a> and let us know about it.
+If you hit a limitation, feel free to hop into our <a href={ config.slack_invite } target="\_blank">Slack community</a> and let us know about it.
 
 ### Why does SST not use CDK's built-in way to build Node.js functions?