diff --git a/docs/platforms/javascript/guides/bun/index.mdx b/docs/platforms/javascript/guides/bun/index.mdx
index ee47a23d628e5..61e9d70890ff7 100644
--- a/docs/platforms/javascript/guides/bun/index.mdx
+++ b/docs/platforms/javascript/guides/bun/index.mdx
@@ -1,5 +1,6 @@
---
title: Bun
+description: Learn how to manually set up Sentry in your Bun app and capture your first errors.
sdk: sentry.javascript.bun
categories:
- javascript
@@ -10,29 +11,30 @@ categories:
-## Install
+## Step 1: Install
-In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/).
+Choose the features you want to configure, and this guide will show you how:
-Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below.
+
-
+
-Sentry captures data by using an SDK within your application's runtime.
+### Install the SDK
+
+Use the Bun package manager to add the Sentry SDK to your application:
```bash {tabTitle:Bun}
bun add @sentry/bun
```
-## Configure
-
-Configuration should happen as early as possible in your application's lifecycle.
+## Step 2: Configure
-Sentry should be initialized as early in your app as possible. It is essential that you call `Sentry.init` before you require any other modules in your application—otherwise, auto-instrumentation of these modules will _not_ work.
+### Initialize the Sentry SDK
-Once this is done, Sentry's Bun SDK captures unhandled exceptions as well as tracing data for your application.
-
-You need to create a file named `instrument.js` that imports and initializes Sentry:
+Sentry should be initialized as early in your app as possible.
+To import and initialize Sentry, create a file named `instrument.js` in the root directory of your project and add the following code:
```javascript {filename: instrument.js}
import * as Sentry from "@sentry/bun";
@@ -53,22 +55,17 @@ Sentry.init({
// https://docs.sentry.io/platforms/javascript/configuration/options/#traces-sample-rate
tracesSampleRate: 1.0,
// ___PRODUCT_OPTION_END___ performance
+ // ___PRODUCT_OPTION_START___ logs
+
+ // Enable logs to be sent to Sentry
+ enableLogs: true,
+ // ___PRODUCT_OPTION_END___ logs
});
```
-Once you set a `tracesSampleRate`, performance instrumentation is automatically enabled for you. See Automatic Instrumentation to learn about all the things that the SDK automatically instruments for you.
-
-You can also manually capture performance data - see Custom Instrumentation for details.
-
-
-
-## Use
+### Apply Instrumentation to Your App
-
-
-Import `instrument.js` before any other modules to ensure Sentry initializes early. If you initialize later, auto-instrumentation and modules like database monitoring, agent monitoring, tracing may not work.
-
-
+Import `instrument.js` before any other modules to make sure Sentry initializes early. If you initialize later, auto-instrumentation and modules like tracing may not work.
```javascript {filename: app.js}
// Import this first!
@@ -80,33 +77,73 @@ import http from "http";
// Your application code goes here
```
-## Verify
+## Step 3: Add Readable Stack Traces With Source Maps (Optional)
+
+
+
+## Step 4: Verify Your Setup
+
+Let's test your setup and confirm that Sentry is working correctly and sending data to your Sentry project.
+
+### Issues
-This snippet includes an intentional error, so you can test that everything is working as soon as you set it up.
+First, let's verify that Sentry captures errors and creates issues in your Sentry project. Add the following code snippet to your main application file, which will call an undefined function, triggering an error that Sentry will capture:
```javascript
-// ___PRODUCT_OPTION_START___ performance
-Sentry.startSpan({
- op: "test",
- name: "My First Test Transaction",
-// ___PRODUCT_OPTION_END___ performance
-}, () => {
- setTimeout(() => {
- try {
- foo();
- } catch (e) {
- Sentry.captureException(e);
- }
- }, 99);
-// ___PRODUCT_OPTION_START___ performance
-});
-// ___PRODUCT_OPTION_END___ performance
+setTimeout(() => {
+ try {
+ foo();
+ } catch (e) {
+ Sentry.captureException(e);
+ }
+}, 99);
+```
+
+
+### Tracing
+To test your tracing configuration, update the previous code snippet by starting a trace to measure the time it takes for the execution of your code:
+
+```javascript
+Sentry.startSpan(
+ {
+ op: "test",
+ name: "My First Test Transaction",
+ },
+ () => {
+ setTimeout(() => {
+ try {
+ foo();
+ } catch (e) {
+ Sentry.captureException(e);
+ }
+ }, 99);
+ }
+);
```
-
+
+
+### View Captured Data in Sentry
+
+Finally, head over to your project on [Sentry.io](https://sentry.io/) to view the collected data (it takes a couple of moments for the data to appear).
+
+
+
+## Next Steps
+
+At this point, you should have integrated Sentry into your Bun application, which should already be sending data to your Sentry project.
+
+Now's a good time to customize your setup and look into more advanced topics.
+Our next recommended steps for you are:
+
+- Extend Sentry to your frontend using one of our [frontend SDKs](/)
+- Learn how to manually capture errors
+- Continue to customize your configuration
+- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts
-Learn more about manually capturing an error or message in our Usage documentation.
+
-
+- Find various topics in Troubleshooting
+- [Get support](https://sentry.zendesk.com/hc/en-us/)
-To view and resolve the recorded error, log into [sentry.io](https://sentry.io) and select your project. Clicking on the error's title will open a page where you can see detailed information and mark it as resolved.
+
diff --git a/platform-includes/getting-started-features-expandable/javascript.bun.mdx b/platform-includes/getting-started-features-expandable/javascript.bun.mdx
new file mode 100644
index 0000000000000..24c6ca4523b0b
--- /dev/null
+++ b/platform-includes/getting-started-features-expandable/javascript.bun.mdx
@@ -0,0 +1,13 @@
+
+
+- [**Issues**](/product/issues) (always enabled): Sentry's core error monitoring product that automatically reports errors,
+ uncaught exceptions, and unhandled rejections. If you have something that
+ looks like an exception, Sentry can capture it.
+- [**Tracing**](/product/tracing): Track software performance while seeing the
+ impact of errors across multiple systems. For example, distributed tracing
+ allows you to follow a request from the frontend to the backend and back.
+- [**Logs**](/product/explore/logs): Centralize and analyze your application logs to
+ correlate them with errors and performance issues. Search, filter, and
+ visualize log data to understand what's happening in your applications.
+
+
diff --git a/platform-includes/getting-started-verify-locate-data/javascript.bun.mdx b/platform-includes/getting-started-verify-locate-data/javascript.bun.mdx
new file mode 100644
index 0000000000000..2aeda41f6656d
--- /dev/null
+++ b/platform-includes/getting-started-verify-locate-data/javascript.bun.mdx
@@ -0,0 +1,7 @@
+
+
+1. Open the [**Issues**](https://sentry.io/issues) page and select an error from the issues list to view the full details and context of this error. For more details, see this [interactive walkthrough](/product/sentry-basics/integrate-frontend/generate-first-error/#ui-walkthrough).
+2. Open the [**Traces**](https://sentry.io/explore/traces) page and select a trace to reveal more information about each span, its duration, and any errors. For an interactive UI walkthrough, click [here](/product/sentry-basics/distributed-tracing/generate-first-error/#ui-walkthrough).
+3. Open the [**Logs**](https://sentry.io/explore/logs) page and filter by service, environment, or search keywords to view log entries from your application. For an interactive UI walkthrough, click [here](/product/explore/logs/#overview).
+
+