diff --git a/docs/platforms/javascript/common/logs/index.mdx b/docs/platforms/javascript/common/logs/index.mdx
index 220889aa994f6..0393776e39a20 100644
--- a/docs/platforms/javascript/common/logs/index.mdx
+++ b/docs/platforms/javascript/common/logs/index.mdx
@@ -8,7 +8,7 @@ sidebar_section: features
-Stack traces tell you *what* broke. Logs tell you *why*. When an error fires, you get a snapshot of the failure, but the context leading up to it is often missing. Logs capture the journey — what the data looked like, which code paths executed, and what state the system was in.
+Stack traces tell you _what_ broke. Logs tell you _why_. When an error fires, you get a snapshot of the failure, but the context leading up to it is often missing. Logs capture the journey — what the data looked like, which code paths executed, and what state the system was in.
Sentry Logs are **high-cardinality** — you can pass any attributes you want and search or filter by them later. No need to decide upfront which fields are important. Just log what might be useful and query it when you need it.
@@ -160,7 +160,7 @@ Already using `console.log`? Capture console calls as Sentry Logs with `consoleL
Multiple arguments are parsed as searchable attributes (requires SDK `10.13.0`+).
-For [Consola](https://github.com/unjs/consola) users, use `Sentry.createConsolaReporter()` instead (requires SDK `10.12.0`+).
+For [Consola](https://github.com/unjs/consola) users, see the [Consola integration](#consola-integration) below.
@@ -274,12 +274,28 @@ export default defineCloudflareOptions((env) => ({
+## Logging Libraries
+
+Connect your existing logger to send its output to Sentry without replacing your logging calls.
+
+
+
+
+
+
+
+
+
## How Logs Link to Other Features
Everything in Sentry is linked by trace. When you're viewing a log, you can jump to the parent trace to see the full request context. When you're viewing a trace, you can see all logs emitted during that operation. This connection makes it easy to move between high-level performance data and detailed diagnostic logs.
- **[Traces](/product/trace-explorer/)** — Logs emitted during an active span automatically include `sentry.trace.parent_span_id`. Click through from any log to see the full trace, or filter logs by trace ID to see everything that happened during a specific request.
-- **[Session Replay](/product/session-replay/)** — Logs include `sentry.replay_id` when a replay is active. Jump from a log entry directly to the replay to see what the user was doing when the log was emitted.
+-
+ **[Session Replay](/product/session-replay/)** — Logs include
+ `sentry.replay_id` when a replay is active. Jump from a log entry directly
+ to the replay to see what the user was doing when the log was emitted.
+
- **[Errors](/product/issues/)** — Logs capture the journey leading up to a failure. When an error occurs, your logs show what data was processed, which code paths executed, and what state the system was in — context that stack traces alone can't provide.
## Best Practices
@@ -294,10 +310,17 @@ Everything in Sentry is linked by trace. When you're viewing a log, you can jump
Any attributes set via `Sentry.setAttribute()` / `Sentry.setAttributes()` (or directly on a scope) are automatically included on all logs. `Sentry.setAttribute(s)` requires SDK version `10.61.0` or above. See [Attributes](#shared-attributes) above for details.
-
## Related Features
-- Tracing — Logs are automatically linked to traces, so you can see logs in the context of the request or operation that produced them.
-- Session Replay — Logs are automatically linked to replays, letting you jump from a log entry to see what the user was doing.
-- Error Monitoring — Use logs to add diagnostic context that helps you understand what led to an error.
-- Attributes — Set attributes once and have them automatically included on all your logs.
+- Tracing — Logs are automatically
+ linked to traces, so you can see logs in the context of the request or
+ operation that produced them.
+-
+ Session Replay — Logs are
+ automatically linked to replays, letting you jump from a log entry to see
+ what the user was doing.
+
+- Error Monitoring — Use logs to add
+ diagnostic context that helps you understand what led to an error.
+- Attributes —
+ Set attributes once and have them automatically included on all your logs.
diff --git a/includes/logs/javascript-winston-integration.mdx b/includes/logs/javascript-winston-integration.mdx
index 4b714ff845688..f809988816157 100644
--- a/includes/logs/javascript-winston-integration.mdx
+++ b/includes/logs/javascript-winston-integration.mdx
@@ -3,7 +3,8 @@
In `9.13.0` and above of the JavaScript SDKs, we've added support to send logs via the winston logging library.
- On SDK versions below `10.71.0`, logs are opt-in. Set `enableLogs: true` in your `Sentry.init` to send them.
+ On SDK versions below `10.71.0`, logs are opt-in. Set `enableLogs: true` in
+ your `Sentry.init` to send them.
```js
@@ -19,7 +20,7 @@ const logger = winston.createLogger({
The `createSentryWinstonTransport` method accepts the following options:
-### Filtering Log Levels
+#### Filtering Log Levels
Use the `levels` option to filter which levels are sent to Sentry. By default all levels are logged.
@@ -30,7 +31,7 @@ const SentryWinstonTransport = Sentry.createSentryWinstonTransport(Transport, {
});
```
-### Custom Level Mapping
+#### Custom Level Mapping