feat(elixir): logs docs (#16237)

In the Elixir SDK 12.0.0 we're adding support for Logs, so here are the
docs 😄

## Preview


https://sentry-docs-git-solnic-logs-docs-for-elixir.sentry.dev/platforms/elixir/logs/

## IS YOUR CHANGE URGENT?  

Help us prioritize incoming PRs by letting us know when the change needs
to go live.
- [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE -->
- [ ] Other deadline: <!-- ENTER DATE HERE -->
- [x] None: Not urgent, can wait up to 1 week+

## SLA

- Teamwork makes the dream work, so please add a reviewer to your PRs.
- Please give the docs team up to 1 week to review your PR unless you've
added an urgent due date to it.
Thanks in advance for your help!

## PRE-MERGE CHECKLIST

*Make sure you've checked the following before merging your changes:*

- [x] Checked Vercel preview for correctness, including links
- [x] PR was reviewed and approved by any necessary SMEs (subject matter
experts)
- [x] PR was reviewed and approved by a member of the [Sentry docs
team](https://github.com/orgs/getsentry/teams/docs)

## LEGAL BOILERPLATE

<!-- Sentry employees and contractors can delete or ignore this section.
-->

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

## EXTRA RESOURCES

- [Sentry Docs contributor guide](https://docs.sentry.io/contributing/)

Author: solnic

docs/platforms/elixir/configuration/options.mdx

@@ -146,3 +146,25 @@ config :sentry,
 If both `:traces_sampler` and `:traces_sample_rate` are configured, `:traces_sampler` takes precedence.
 
 </SdkOption>
+
+## Telemetry Processor Options
+
+The Telemetry Processor is a buffered, priority-based event delivery mechanism. It batches events and sends them to Sentry using a weighted scheduler that prioritizes critical events (like errors) over lower-priority ones (like logs). Logs are routed through the Telemetry Processor by default. You can opt in to route other event types through the processor as well. In a future major release, the Telemetry Processor will become the default delivery mechanism for all event types.
+
+<SdkOption name="telemetry_processor_categories" type='list' defaultValue='[:log]'>
+
+A list of event categories to route through the Telemetry Processor. By default, only `:log` events use the processor. You can opt in to route additional event types through it.
+
+Valid categories:
+
+- `:error` — error events (critical priority)
+- `:check_in` — cron check-in events (high priority)
+- `:transaction` — transaction events (medium priority)
+- `:log` — log events (low priority)
+
+```elixir
+config :sentry,
+  telemetry_processor_categories: [:error, :check_in, :transaction, :log]
+```
+
+</SdkOption>

docs/platforms/elixir/crons/index.mdx

@@ -3,6 +3,7 @@ title: Set Up Crons
 sidebar_title: Crons
 description: "Sentry Crons allows you to monitor the uptime and performance of any scheduled, recurring job in your application."
 sidebar_order: 5750
+sidebar_section: features
 ---
 
 Once implemented, it'll allow you to get alerts and metrics to help you solve errors, detect timeouts, and prevent disruptions to your service.

docs/platforms/elixir/logs/index.mdx

@@ -0,0 +1,34 @@
+---
+title: Set Up Logs
+sidebar_title: Logs
+description: "Structured logs allow you to send, view and query logs sent from your applications within Sentry."
+sidebar_order: 4
+sidebar_section: features
+new: true
+---
+
+With Sentry Structured Logs, you can send text-based log information from your applications to Sentry. Once in Sentry, these logs can be viewed alongside relevant errors, searched by text-string, or searched using their individual attributes.
+
+## Requirements
+
+<PlatformContent includePath="logs/requirements" />
+
+## Setup
+
+<PlatformContent includePath="logs/setup" />
+
+## Usage
+
+<PlatformContent includePath="logs/usage" />
+
+## Integrations
+
+<PlatformContent includePath="logs/integrations" />
+
+## Options
+
+<PlatformContent includePath="logs/options" />
+
+## Default Attributes
+
+<PlatformContent includePath="logs/default-attributes" />

docs/platforms/elixir/tracing/index.mdx

@@ -3,6 +3,7 @@ title: Set Up Tracing
 sidebar_title: Tracing
 description: "Learn how to enable tracing in your app and discover valuable performance insights of your application."
 sidebar_order: 30
+sidebar_section: features
 ---
 
 With [tracing](/product/insights/overview/), Sentry tracks your software performance, measuring metrics like throughput and latency, and displaying the impact of errors across multiple systems.

docs/platforms/elixir/usage/index.mdx

@@ -1,7 +1,9 @@
 ---
 title: Usage
+sidebar_title: Capturing Errors
 description: "Use the SDK to manually capture errors and other events."
 sidebar_order: 10
+sidebar_section: features
 ---
 
 Sentry's SDK hooks into your runtime environment and automatically reports errors, uncaught exceptions, and unhandled rejections as well as other types of errors depending on the platform.

docs/platforms/elixir/user-feedback/index.mdx

@@ -3,6 +3,7 @@ title: Set Up User Feedback
 sidebar_title: User Feedback
 description: "Learn more about collecting user feedback when an event occurs. Sentry pairs the feedback with the original event, giving you additional insight into issues."
 sidebar_order: 6000
+sidebar_section: features
 ---
 
 When a user experiences an error, Sentry provides the ability to collect additional feedback. You can collect feedback according to the method supported by the SDK.

platform-includes/configuration/before-send-log/elixir.mdx

@@ -0,0 +1,34 @@
+```elixir
+config :sentry,
+  dsn: "___PUBLIC_DSN___",
+  enable_logs: true,
+  before_send_log: fn log_event ->
+    # Skip info logs
+    if log_event.level == :info do
+      false
+    else
+      log_event
+    end
+  end
+```
+
+You can also use a module/function tuple:
+
+```elixir
+config :sentry,
+  dsn: "___PUBLIC_DSN___",
+  enable_logs: true,
+  before_send_log: {MyApp.Sentry, :before_send_log}
+
+# In lib/my_app/sentry.ex
+defmodule MyApp.Sentry do
+  def before_send_log(%Sentry.LogEvent{} = log_event) do
+    # Filter out logs from specific domains or modify attributes
+    if String.contains?(log_event.body, "sensitive") do
+      false
+    else
+      log_event
+    end
+  end
+end
+```

platform-includes/logs/default-attributes/elixir.mdx

@@ -0,0 +1,16 @@
+The Elixir SDK automatically sets several default attributes on all log entries to provide context and improve debugging:
+
+<Include name="logs/default-attributes/core" />
+
+<Include name="logs/default-attributes/message-template" />
+
+<Include name="logs/default-attributes/server" />
+
+### OpenTelemetry Attributes
+
+If you're using OpenTelemetry with the `opentelemetry_logger_metadata` package, the following attributes are automatically included:
+
+- `trace_id`: The OpenTelemetry trace ID associated with the log event.
+- `span_id`: The OpenTelemetry span ID associated with the log event.
+
+If no OpenTelemetry context is available, a random trace ID is generated to allow log correlation within Sentry.

platform-includes/logs/integrations/elixir.mdx

@@ -0,0 +1,43 @@
+Logs are sent to Sentry through Erlang's `:logger` system via `Sentry.LoggerHandler`. When `enable_logs: true` is set in your Sentry configuration, the SDK automatically attaches the handler — no manual setup is needed. Any logs from your application or libraries that use Elixir's `Logger` or Erlang's `:logger` will be captured and sent to Sentry at or above the configured level.
+
+The logs behavior is configured globally via the `:logs` key — not through the handler config map:
+
+```elixir
+config :sentry,
+  enable_logs: true,
+  logs: [
+    level: :info,
+    metadata: [:request_id, :user_id]
+  ]
+```
+
+With this configuration, logs at or above `:info` will be sent to Sentry:
+
+```elixir
+require Logger
+
+Logger.debug("Debug message")  # Not sent (below :info level)
+Logger.info("Info message")    # Sent to Sentry
+Logger.warning("Warning")      # Sent to Sentry
+Logger.error("Error occurred") # Sent to Sentry
+```
+
+### Excluding Domains
+
+You can exclude specific logger domains from being sent to Sentry using the `:excluded_domains` option under `:logs`:
+
+```elixir
+config :sentry,
+  enable_logs: true,
+  logs: [
+    level: :info,
+    excluded_domains: [:ecto, :phoenix]
+  ]
+```
+
+<Alert level="info" title="Logs vs Error Reporting">
+  The logs feature (configured under `:logs`) is separate from error
+  reporting (configured via `Sentry.LoggerHandler`'s `:level` option). Error reporting captures crash reports and
+  exceptions, while logs captures structured log events. You can configure both
+  independently.
+</Alert>

platform-includes/logs/options/elixir.mdx

@@ -0,0 +1,43 @@
+### before_send_log
+
+To filter or modify logs before they are sent to Sentry, use the `before_send_log` callback. Return `false` to skip a log, or return the log event to send it.
+
+<PlatformContent includePath="configuration/before-send-log" />
+
+### Logs Configuration
+
+Logs behavior is configured under the `:logs` key in your Sentry configuration. These options control the auto-attached `Sentry.LoggerHandler`:
+
+- **`:level`** - The minimum log level to send to Sentry's Logs Protocol. Default: `:info`. Supported values: `:debug`, `:info`, `:notice`, `:warning`, `:error`, `:critical`, `:alert`, `:emergency`.
+
+- **`:excluded_domains`** - A list of logger domains to exclude from logs sent to Sentry. Default: `[]`.
+
+- **`:metadata`** - Logger metadata keys to include as attributes in log events. Set to `:all` to include all metadata, or a list of specific keys like `[:request_id, :user_id]`. Default: `[]`.
+
+```elixir
+config :sentry,
+  dsn: "___PUBLIC_DSN___",
+  enable_logs: true,
+  logs: [
+    level: :info,
+    excluded_domains: [:ecto],
+    metadata: [:request_id, :user_id] # or :all
+  ]
+```
+
+### Global Configuration Options
+
+These options are set in your Sentry configuration (`config :sentry`):
+
+- **`:enable_logs`** - Set to `true` to enable the logs feature. When enabled, the SDK automatically attaches a `Sentry.LoggerHandler` and routes log events through the SDK's Telemetry Processor. Default is `false`.
+
+- **`:before_send_log`** - A callback function to filter or modify log events before they are sent.
+
+Log events are buffered by the Telemetry Processor with a capacity of 1000 entries and flushed in batches of 100 or every 5 seconds, whichever comes first. You can customize these defaults through the <PlatformLink to="/configuration/options/#telemetry-processor-options">Telemetry Processor options</PlatformLink>.
+
+```elixir
+config :sentry,
+  dsn: "___PUBLIC_DSN___",
+  enable_logs: true,
+  before_send_log: {MyApp.Sentry, :before_send_log}
+```