Skip to content

jaeger docs update #1698

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DaedalusG merged 3 commits into from
Mar 19, 2026
Merged

jaeger docs update #1698

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
17a6b53
jaeger docs update
DaedalusG Mar 19, 2026
c8255f1
simplify
DaedalusG Mar 19, 2026
e1ab62f
update
DaedalusG Mar 19, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions docs/self-hosted/deploy/kubernetes/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -395,6 +395,37 @@ jaeger:
enabled: true
```

#### Customize Jaeger configuration

Starting with Sourcegraph 7.1.0, the bundled Jaeger instance uses an [OpenTelemetry Collector-style YAML configuration](https://www.jaegertracing.io/docs/2.16/configuration/) instead of CLI flags. Common settings are exposed through the `jaeger.config` Helm value.

You can override these settings in your Helm values override file. For example, to increase the maximum number of in-memory traces:

```yaml
jaeger:
enabled: true
config:
maxTraces: 50000
```

Or using `--set` on the command line:

```bash
helm upgrade sourcegraph sourcegraph/sourcegraph \
--set jaeger.config.maxTraces=50000
```

The available configuration options are:

| Value | Default | Description |
| --- | --- | --- |
| `jaeger.config.maxTraces` | `20000` | Maximum number of traces stored in memory |
| `jaeger.config.logLevel` | `info` | Log level (`debug`, `info`, `warn`, `error`) |
| `jaeger.config.samplingDefaultProbability` | `1.0` | Default sampling probability (0.0–1.0) returned to services that query Jaeger for sampling config |
| `jaeger.config.existingConfigMap` | `""` | Name of a pre-existing ConfigMap containing a `jaeger-config.yaml` key. When set, the chart skips creating its own ConfigMap and uses yours instead |

For advanced customization beyond these options, set `jaeger.config.existingConfigMap` to the name of your own ConfigMap containing a full `jaeger-config.yaml` key. See the [Jaeger v2 configuration reference](https://www.jaegertracing.io/docs/2.16/configuration/) for all available options.

#### Configure OpenTelemetry Collector to use an external tracing backend

To configure the bundled otel-collector to export traces to an external OTEL-compatible backend, you you can customize the otel-collector's config file directly in your Helm values `override.yaml` file.
Expand Down
2 changes: 2 additions & 0 deletions docs/self-hosted/observability/tracing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ To deploy our bundled Jaeger backend, follow the instructions for your deploymen
- [Kubernetes with Kustomize](/self-hosted/deploy/kubernetes/configure#deploy-the-bundled-opentelemetry-collector-and-jaeger)
- [Docker Compose](/self-hosted/deploy/docker-compose/configuration#deploy-the-bundled-jaeger)

For Helm deployments, you can also [customize the Jaeger configuration](/self-hosted/deploy/kubernetes#customize-jaeger-configuration) (e.g., `max_traces`, sampling, log level) directly through Helm values.

Then configure your Site Configuration:

1. Ensure your `externalURL` is configured
Expand Down