diff --git a/docs/admin/code-hosts/aws-codecommit.mdx b/docs/admin/code-hosts/aws-codecommit.mdx index 54b70f895..69dabff04 100644 --- a/docs/admin/code-hosts/aws-codecommit.mdx +++ b/docs/admin/code-hosts/aws-codecommit.mdx @@ -37,7 +37,7 @@ AWS CodeCommit connections support the following configuration options, which ar {/* SCHEMA_SYNC_START: admin/code_hosts/aws_codecommit.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { // REQUIRED: diff --git a/docs/admin/code-hosts/azuredevops.mdx b/docs/admin/code-hosts/azuredevops.mdx index 807a1af5b..ef4a65626 100644 --- a/docs/admin/code-hosts/azuredevops.mdx +++ b/docs/admin/code-hosts/azuredevops.mdx @@ -69,7 +69,7 @@ Azure DevOps connections support the following configuration options, which are {/* SCHEMA_SYNC_START: admin/code_hosts/azuredevops.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json // Authentication alternatives: token OR windowsPassword diff --git a/docs/admin/code-hosts/bitbucket-cloud.mdx b/docs/admin/code-hosts/bitbucket-cloud.mdx index 3aa04e5cf..86f01b197 100644 --- a/docs/admin/code-hosts/bitbucket-cloud.mdx +++ b/docs/admin/code-hosts/bitbucket-cloud.mdx @@ -116,7 +116,7 @@ Bitbucket Cloud connections support the following configuration options, which a {/* SCHEMA_SYNC_START: admin/code_hosts/bitbucket_cloud.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { // The workspace access token to use when authenticating with Bitbucket Cloud. diff --git a/docs/admin/code-hosts/bitbucket-server.mdx b/docs/admin/code-hosts/bitbucket-server.mdx index f6d34d502..5c106543b 100644 --- a/docs/admin/code-hosts/bitbucket-server.mdx +++ b/docs/admin/code-hosts/bitbucket-server.mdx @@ -202,7 +202,7 @@ Bitbucket Server / Bitbucket Data Center connections support the following confi {/* SCHEMA_SYNC_START: admin/code_hosts/bitbucket_server.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json // Authentication alternatives: token OR password diff --git a/docs/admin/code-hosts/gerrit.mdx b/docs/admin/code-hosts/gerrit.mdx index 1daa1857a..efe108b6e 100644 --- a/docs/admin/code-hosts/gerrit.mdx +++ b/docs/admin/code-hosts/gerrit.mdx @@ -113,7 +113,7 @@ Gerrit connections support the following configuration options, which are specif {/* SCHEMA_SYNC_START: admin/code_hosts/gerrit.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { // If non-null, enforces Gerrit repository permissions. This requires that there is an item in the [site configuration json](https://sourcegraph.com/docs/admin/config/site_config#auth-providers) `auth.providers` field, of type "gerrit" with the same `url` field as specified in this `GerritConnection`. @@ -170,6 +170,12 @@ Gerrit connections support the following configuration options, which are specif // ] "projects": null, + // Rate limit applied to Gerrit REST API requests, including repository and permissions syncing. + "rateLimit": { + "enabled": false, + "requestsPerHour": 0 + }, + // The pattern used to generate the corresponding Sourcegraph repository name for a Gerrit repository. In the pattern, the variable "{host}" is replaced with the Gerrit host (such as gerrit.example.com), and "{name}" is replaced with the Gerrit repository's name (such as "myrepo"). // For example, if your Gerrit URL is https://gerrit.example.com and your Sourcegraph URL is https://src.example.com, then a repositoryPathPattern of "{host}/{name}" would mean that a Gerrit repository at https://gerrit.example.com/myrepo is available on Sourcegraph at https://src.example.com/gerrit.example.com/myrepo. // It is important that the Sourcegraph repository name generated with this pattern be unique to this code host. If different code hosts generate repository names that collide, Sourcegraph's behavior is undefined. diff --git a/docs/admin/code-hosts/github.mdx b/docs/admin/code-hosts/github.mdx index 394bdc81f..59c98a777 100644 --- a/docs/admin/code-hosts/github.mdx +++ b/docs/admin/code-hosts/github.mdx @@ -458,7 +458,7 @@ GitHub connections support the following configuration options, which are specif {/* SCHEMA_SYNC_START: admin/code_hosts/github.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json // Authentication alternatives: token OR gitHubAppDetails OR externalAccount OR useRandomExternalAccount diff --git a/docs/admin/code-hosts/gitlab.mdx b/docs/admin/code-hosts/gitlab.mdx index 0522c4c83..f0e78b96f 100644 --- a/docs/admin/code-hosts/gitlab.mdx +++ b/docs/admin/code-hosts/gitlab.mdx @@ -189,7 +189,7 @@ See [Internal rate limits](/admin/code-hosts/rate-limits#internal-rate-limits). {/* SCHEMA_SYNC_START: admin/code_hosts/gitlab.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { // If non-null, enforces GitLab repository permissions. This requires that there be an item in the `auth.providers` field of type "gitlab" with the same `url` field as specified in this `GitLabConnection`. diff --git a/docs/admin/code-hosts/gitolite.mdx b/docs/admin/code-hosts/gitolite.mdx index 516310245..76a2e7da8 100644 --- a/docs/admin/code-hosts/gitolite.mdx +++ b/docs/admin/code-hosts/gitolite.mdx @@ -25,7 +25,7 @@ To connect Gitolite to Sourcegraph: {/* SCHEMA_SYNC_START: admin/code_hosts/gitolite.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { // A list of repositories to never mirror from this Gitolite instance. Supports excluding by exact name ({"name": "foo"}). diff --git a/docs/admin/code-hosts/other.mdx b/docs/admin/code-hosts/other.mdx index 1539b5ef1..3d04484b9 100644 --- a/docs/admin/code-hosts/other.mdx +++ b/docs/admin/code-hosts/other.mdx @@ -68,7 +68,7 @@ Repositories must be listed individually: {/* SCHEMA_SYNC_START: admin/code_hosts/other_external_service.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { // A list of repositories to never mirror by name after applying repositoryPathPattern. Supports excluding by exact name ({"name": "myrepo"}) or regular expression ({"pattern": ".*secret.*"}). diff --git a/docs/admin/code-hosts/phabricator.mdx b/docs/admin/code-hosts/phabricator.mdx index 38e40ad28..17ce51933 100644 --- a/docs/admin/code-hosts/phabricator.mdx +++ b/docs/admin/code-hosts/phabricator.mdx @@ -76,7 +76,7 @@ The Sourcegraph instance's site admin must [update the `corsOrigin` site config {/* SCHEMA_SYNC_START: admin/code_hosts/phabricator.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { // SSH cipher to use when cloning via SSH. Must be a valid choice from `ssh -Q cipher`. diff --git a/docs/admin/config/settings.mdx b/docs/admin/config/settings.mdx index a372a89b1..0c26dd6f9 100644 --- a/docs/admin/config/settings.mdx +++ b/docs/admin/config/settings.mdx @@ -27,7 +27,7 @@ Settings options and their default values are shown below. {/* SCHEMA_SYNC_START: admin/config/settings.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { diff --git a/docs/admin/config/site-config.mdx b/docs/admin/config/site-config.mdx index bf2f2e53e..9960c999f 100644 --- a/docs/admin/config/site-config.mdx +++ b/docs/admin/config/site-config.mdx @@ -21,7 +21,7 @@ All site configuration options and their default values are shown below. {/* SCHEMA_SYNC_START: admin/config/site.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { @@ -928,7 +928,7 @@ All site configuration options and their default values are shown below. "executors.accessToken": null, // The image to use for batch changes in executors when using native execution. Use this value to pull from a custom image registry. - "executors.batcheshelperImage": "sourcegraph/batcheshelper", + "executors.batcheshelperImage": "us-docker.pkg.dev/sourcegraph-images/external/batcheshelper", // The tag to use for the batcheshelper image in executors when using native execution. Use this value to use a custom tag. Sourcegraph by default uses the best match, so use this setting only if you really need to overwrite it and make sure to keep it updated. // Other example values: diff --git a/docs/admin/repo/perforce.mdx b/docs/admin/repo/perforce.mdx index c76a948ad..bf17f323e 100644 --- a/docs/admin/repo/perforce.mdx +++ b/docs/admin/repo/perforce.mdx @@ -228,7 +228,7 @@ With this setting, Sourcegraph will ignore any rules with a host other than `*`, {/* SCHEMA_SYNC_START: admin/code_hosts/perforce.schema.json */} {/* WARNING: This section is auto-generated during releases. Do not edit manually. */} -{/* Last updated: 2026-08-25T23:40:39Z */} +{/* Last updated: 2026-09-02T22:00:02Z */} ```json { // If non-null, enforces Perforce depot permissions. diff --git a/docs/self-hosted/observability/alerts.mdx b/docs/self-hosted/observability/alerts.mdx index 6ab2447e8..90902e7b3 100644 --- a/docs/self-hosted/observability/alerts.mdx +++ b/docs/self-hosted/observability/alerts.mdx @@ -2412,7 +2412,7 @@ Generated query for critical alert: `min((sum by (app) (up{app=~".*(pgsql\\|code
Technical details -Generated query for warning alert: `max((max(src_workerutil_queue_duration_seconds{domain="codeintel_upload"})) >= 3600)` +Generated query for warning alert: `max((max(src_workerutil_queue_duration_seconds{domain="precise_code_intel_upload_worker"})) >= 3600)`
@@ -7375,7 +7375,7 @@ Generated query for critical alert: `max((max(deriv(src_deepsearch_questions_in_ **Next steps** -- Check frontend logs for `worker failed to process question` errors. +- Check worker logs for `worker failed to process question` errors. - Common causes: upstream LLM provider failures (rate limiting or capacity, e.g. 429/503, and timeouts), database errors mid-processing, or worker panics (`worker panic while processing question`). - More help interpreting this metric is available in the [dashboards reference](dashboards#deepsearch-deepsearch_question_processing_error_rate). - **Silence this alert:** If you are aware of this alert and want to silence notifications for it, add the following to your site configuration and set a reminder to re-evaluate the alert: @@ -7411,7 +7411,7 @@ Custom query for critical alert: `max(((sum(increase(src_deepsearch_question_pro **Next steps** -- Search frontend logs for questionIDs with long processing times. +- Search worker logs for questionIDs with long processing times. - Check `deepsearch_turn_p95_duration` to see if individual turns are slow. - Check `deepsearch_question_outcome_by_reason` for elevated truncation or error rates. - More help interpreting this metric is available in the [dashboards reference](dashboards#deepsearch-deepsearch_slow_questions). @@ -7447,7 +7447,7 @@ Generated query for critical alert: `max((sum(increase(src_deepsearch_question_p **Next steps** -- Search frontend logs for: "answer truncated due to output token limit with no response generated" to find affected questionIDs. +- Search worker logs for: "answer truncated due to output token limit with no response generated" to find affected questionIDs. - The output token budget was consumed before any answer text was produced, usually by reasoning tokens, so affected users got nothing back. - Check if a recent model change or reasoning effort change caused increased thinking token usage. - Compare against `deepsearch_response_truncated`: elevated truncations alone are usually users requesting very large outputs and are not a regression. diff --git a/docs/self-hosted/observability/dashboards.mdx b/docs/self-hosted/observability/dashboards.mdx index 8bf6bb6a0..a5ce15315 100644 --- a/docs/self-hosted/observability/dashboards.mdx +++ b/docs/self-hosted/observability/dashboards.mdx @@ -10971,7 +10971,7 @@ To see this panel, visit `/-/debug/grafana/d/precise-code-intel-worker/precise-c Query: ``` -max(src_workerutil_queue_duration_seconds{domain="codeintel_upload"}) +max(src_workerutil_queue_duration_seconds{domain="precise_code_intel_upload_worker"}) ``` @@ -36250,7 +36250,7 @@ histogram_quantile(0.50, sum(rate(src_deepsearch_question_processing_duration_se

Questions rejected by usage limits over 15m

-Number of deep search questions rejected because the user hit their usage entitlement limit, by entitlement name. These are intentional quota rejections, not processing failures, and do not count towards the question processing error rate. Check frontend logs for `question rejected: usage limit exceeded` to identify affected users. Sustained rejections from an API client usually mean the client does not back off after hitting its limit. +Number of deep search questions rejected because the user hit their usage entitlement limit, by entitlement name. These are intentional quota rejections, not processing failures, and do not count towards the question processing error rate. Check worker logs for `question rejected: usage limit exceeded` to identify affected users. Sustained rejections from an API client usually mean the client does not back off after hitting its limit. This panel has no related alerts.