instance_limits.md 29.1 KB
Newer Older
1
---
2 3
stage: Enablement
group: Distribution
4
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
5 6 7
type: reference
---

8
# GitLab application limits **(FREE SELF)**
9 10 11 12 13

GitLab, like most large applications, enforces limits within certain features to maintain a
minimum quality of performance. Allowing some features to be limitless could affect security,
performance, data, or could even exhaust the allocated resources for the application.

14 15 16 17
## Rate limits

Rate limits can be used to improve the security and durability of GitLab.

18
For example, one script can make thousands of web requests per second. Whether malicious, apathetic, or just a bug, your application and infrastructure may not be able to cope with the load. Rate limits can help to mitigate these types of attacks.
19 20 21 22 23 24 25 26 27

Read more about [configuring rate limits](../security/rate_limits.md) in the Security documentation.

### Issue creation

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/28129) in GitLab 12.10.

This setting limits the request rate to the issue creation endpoint.

28
Read more about [issue creation rate limits](../user/admin_area/settings/rate_limit_on_issues_creation.md).
29

30
- **Default rate limit**: Disabled by default.
31 32 33 34 35

### By User or IP

This setting limits the request rate per user or IP.

36
Read more about [User and IP rate limits](../user/admin_area/settings/user_and_ip_rate_limits.md).
37

38
- **Default rate limit**: Disabled by default.
39 40 41 42 43 44 45

### By raw endpoint

> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/30829) in GitLab 12.2.

This setting limits the request rate per endpoint.

46
Read more about [raw endpoint rate limits](../user/admin_area/settings/rate_limits_on_raw_endpoints.md).
47

48
- **Default rate limit**: 300 requests per project, per commit and per file path.
49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67

### By protected path

This setting limits the request rate on specific paths.

GitLab rate limits the following paths by default:

```plaintext
'/users/password',
'/users/sign_in',
'/api/#{API::API.version}/session.json',
'/api/#{API::API.version}/session',
'/users',
'/users/confirmation',
'/unsubscribes/',
'/import/github/personal_access_token',
'/admin/session'
```

68
Read more about [protected path rate limits](../user/admin_area/settings/protected_paths.md).
69

70
- **Default rate limit**: After 10 requests, the client must wait 60 seconds before trying again.
71

72 73 74 75 76 77 78
### Package Registry

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/57029) in GitLab 13.12.

This setting limits the request rate on the Packages API per user or IP. For more information, see
[Package Registry Rate Limits](../user/admin_area/settings/package_registry_rate_limits.md).

79
- **Default rate limit**: Disabled by default.
80

81 82 83 84 85 86
### Import/Export

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/35728) in GitLab 13.2.

This setting limits the import/export actions for groups and projects.

87 88 89 90
| Limit                   | Default (per minute per user) |
|-------------------------|-------------------------------|
| Project Import          | 6 |
| Project Export          | 6 |
91
| Project Export Download | 1 |
92 93 94
| Group Import            | 6 |
| Group Export            | 6 |
| Group Export Download   | 1 |
95

96
Read more about [import/export rate limits](../user/admin_area/settings/import_export_rate_limits.md).
97 98 99 100 101 102 103

### Rack attack

This method of rate limiting is cumbersome, but has some advantages. It allows
throttling of specific paths, and is also integrated into Git and container
registry requests.

104
Read more about the [Rack Attack initializer](../security/rack_attack.md) method of setting rate limits.
105

106
- **Default rate limit**: Disabled.
107

108 109 110 111 112 113 114
### Member Invitations

Limit the maximum daily member invitations allowed per group hierarchy.

- GitLab.com: Free members may invite 20 members per day.
- Self-managed: Invites are not limited.

115
### Webhook rate limit
116 117

> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/61151) in GitLab 13.12.
118
> - [Feature flag removed](https://gitlab.com/gitlab-org/gitlab/-/issues/330133) in GitLab 14.1.
119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135

Limit the number of times any given webhook can be called per minute.
This only applies to project and group webhooks.

Calls over the rate limit are logged into `auth.log`.

```ruby
# If limits don't exist for the default plan, you can create one with:
# Plan.default.create_limits!

Plan.default.actual_limits.update!(web_hook_calls: 10)
```

Set the limit to `0` to disable it.

- **Default rate limit**: Disabled.

136 137
## Gitaly concurrency limit

138
Clone traffic can put a large strain on your Gitaly service. To prevent such workloads from overwhelming your Gitaly server, you can set concurrency limits in Gitaly's configuration file.
139

140
Read more about [Gitaly concurrency limits](gitaly/configure_gitaly.md#limit-rpc-concurrency).
141

142
- **Default rate limit**: Disabled.
143

144
## Number of comments per issue, merge request, or commit
145

146
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/22388) in GitLab 12.4.
147 148 149

There's a limit to the number of comments that can be submitted on an issue,
merge request, or commit. When the limit is reached, system notes can still be
150
added so that the history of events is not lost, but the user-submitted
Manisha Singh's avatar
Manisha Singh committed
151
comment fails.
152

153
- **Max limit**: 5,000 comments.
154

155 156
## Size of comments and descriptions of issues, merge requests, and epics

157
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/61974) in GitLab 12.2.
158 159

There is a limit to the size of comments and descriptions of issues, merge requests, and epics.
Manisha Singh's avatar
Manisha Singh committed
160 161
Attempting to add a body of text larger than the limit, results in an error, and the
item is also not created.
162

Manisha Singh's avatar
Manisha Singh committed
163
It's possible that this limit changes to a lower number in the future.
164

165
- **Max size**: ~1 million characters / ~1 MB.
166

167 168 169 170 171
## Size of commit titles and descriptions

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/292039) in GitLab 13.9

Commits with arbitrarily large messages may be pushed to GitLab, but when
Manisha Singh's avatar
Manisha Singh committed
172 173
displaying commits, titles (the first line of the commit message)
limits to 1KiB, and descriptions (the rest of the message) limits to
174 175
1MiB.

176 177
## Number of issues in the milestone overview

178 179
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/39453) in GitLab 12.10.
> - [Set](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/58168) to 500 in GitLab 13.11.
180

181
The maximum number of issues loaded on the milestone overview page is 500.
182
When the number exceeds the limit the page displays an alert and links to a paginated
183
[issue list](../user/project/issues/managing_issues.md) of all issues in the milestone.
184

185
- **Limit**: 500 issues.
186

187 188
## Number of pipelines per Git push

189
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/51401) in GitLab 11.10.
190 191 192 193 194

The number of pipelines that can be created in a single push is 4.
This is to prevent the accidental creation of pipelines when `git push --all`
or `git push --mirror` is used.

195
Read more in the [CI documentation](../ci/yaml/index.md#processing-git-pushes).
196 197 198

## Retention of activity history

199
Activity history for projects and individuals' profiles was limited to one year until [GitLab 11.4](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/52246) when it was extended to two years, and in [GitLab 12.4](https://gitlab.com/gitlab-org/gitlab/-/issues/33840) to three years.
200

201 202 203 204 205 206
## Number of embedded metrics

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14939) in GitLab 12.7.

There is a limit when embedding metrics in GFM for performance reasons.

207
- **Max limit**: 100 embeds.
208

Andy Soiron's avatar
Andy Soiron committed
209 210
## Number of webhooks

211
On GitLab.com, the [maximum number of webhooks and their size](../user/gitlab_com/index.md#webhooks) per project, and per group, is limited.
Andy Soiron's avatar
Andy Soiron committed
212

213
To set this limit for a self-managed installation, where the default is `100` project webhooks and `50` group webhooks, run the following in the
214
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
215 216 217 218 219

```ruby
# If limits don't exist for the default plan, you can create one with:
# Plan.default.create_limits!

Andy Soiron's avatar
Andy Soiron committed
220
# For project webhooks
221
Plan.default.actual_limits.update!(project_hooks: 200)
Andy Soiron's avatar
Andy Soiron committed
222 223

# For group webhooks
224
Plan.default.actual_limits.update!(group_hooks: 100)
225 226
```

227
Set the limit to `0` to disable it.
228

229 230 231 232 233 234 235
## Pull Mirroring Interval

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/237891) in GitLab 13.7.

The [minimum time between pull refreshes](../user/project/repository/repository_mirroring.md)
defaults to 300 seconds (5 minutes).

236
To change this limit for a self-managed installation, run the following in the
237 238 239 240 241 242 243 244 245
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):

```ruby
# If limits don't exist for the default plan, you can create one with:
# Plan.default.create_limits!

Plan.default.actual_limits.update!(pull_mirror_interval_seconds: 200)
```

246 247
## Incoming emails from auto-responders

248
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/30327) in GitLab 12.4.
249 250 251 252

GitLab ignores all incoming emails sent from auto-responders by looking for the `X-Autoreply`
header. Such emails don't create comments on issues or merge requests.

253
## Amount of data sent from Sentry through Error Tracking
254 255 256 257 258 259

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/14926) in GitLab 12.6.

Sentry payloads sent to GitLab have a 1 MB maximum limit, both for security reasons
and to limit memory consumption.

260
## Max offset allowed by the REST API for offset-based pagination
261 262 263 264 265 266

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/34565) in GitLab 13.0.

When using offset-based pagination in the REST API, there is a limit to the maximum
requested offset into the set of results. This limit is only applied to endpoints that
support keyset-based pagination. More information about pagination options can be
267
found in the [API docs section on pagination](../api/index.md#pagination).
268

269
To set this limit for a self-managed installation, run the following in the
270
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
271 272 273 274 275

```ruby
# If limits don't exist for the default plan, you can create one with:
# Plan.default.create_limits!

276
Plan.default.actual_limits.update!(offset_pagination_limit: 10000)
277 278
```

279
- **Default offset pagination limit**: `50000`.
280

281
Set the limit to `0` to disable it.
282

283 284 285 286
## CI/CD limits

### Number of jobs in active pipelines

287
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/32823) in GitLab 12.6.
288 289 290 291 292 293 294 295 296

The total number of jobs in active pipelines can be limited per project. This limit is checked
each time a new pipeline is created. An active pipeline is any pipeline in one of the following states:

- `created`
- `pending`
- `running`

If a new pipeline would cause the total number of jobs to exceed the limit, the pipeline
Manisha Singh's avatar
Manisha Singh committed
297
fails with a `job_activity_limit_exceeded` error.
298

Craig Norris's avatar
Craig Norris committed
299 300 301 302 303
- GitLab SaaS subscribers have different limits [defined per plan](../user/gitlab_com/index.md#gitlab-cicd),
  and they affect all projects under that plan.
- On [GitLab Premium](https://about.gitlab.com/pricing/) self-managed or
  higher installations, this limit is defined under a `default` plan that affects all
  projects. This limit is disabled (`0`) by default.
304

305
To set this limit for a self-managed installation, run the following in the
306
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
307 308 309 310 311

```ruby
# If limits don't exist for the default plan, you can create one with:
# Plan.default.create_limits!

312
Plan.default.actual_limits.update!(ci_active_jobs: 500)
313 314
```

315
Set the limit to `0` to disable it.
316

317 318 319 320 321 322 323 324 325
### Maximum number of deployment jobs in a pipeline

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/46931) in GitLab 13.7.

You can limit the maximum number of deployment jobs in a pipeline. A deployment is
any job with an [`environment`](../ci/environments/index.md) specified. The number
of deployments in a pipeline is checked at pipeline creation. Pipelines that have
too many deployments fail with a `deployments_limit_exceeded` error.

Craig Norris's avatar
Craig Norris committed
326
The default limit is 500 for all [GitLab self-managed and SaaS plans](https://about.gitlab.com/pricing/).
327

328
To change the limit for a self-managed installation, change the `default` plan's limit with the following
329 330 331 332 333 334 335 336 337 338 339
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session) command:

```ruby
# If limits don't exist for the default plan, you can create one with:
# Plan.default.create_limits!

Plan.default.actual_limits.update!(ci_pipeline_deployments: 500)
```

Set the limit to `0` to disable it.

340 341
### Number of CI/CD subscriptions to a project

342
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/9045) in GitLab 12.9.
343 344 345 346 347

The total number of subscriptions can be limited per project. This limit is
checked each time a new subscription is created.

If a new subscription would cause the total number of subscription to exceed the
Manisha Singh's avatar
Manisha Singh committed
348
limit, the subscription is considered invalid.
349

Craig Norris's avatar
Craig Norris committed
350 351 352 353 354
- GitLab SaaS subscribers have different limits [defined per plan](../user/gitlab_com/index.md#gitlab-cicd),
  and they affect all projects under that plan.
- On [GitLab Premium](https://about.gitlab.com/pricing/) self-managed
  or higher installations, this limit is defined under a `default` plan that
  affects all projects. By default, there is a limit of `2` subscriptions.
355

356
To set this limit for a self-managed installation, run the following in the
357
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
358 359

```ruby
360
Plan.default.actual_limits.update!(ci_project_subscriptions: 500)
361 362
```

363
Set the limit to `0` to disable it.
364

365 366 367 368 369 370 371
### Number of pipeline schedules

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/29566) in GitLab 12.10.

The total number of pipeline schedules can be limited per project. This limit is
checked each time a new pipeline schedule is created. If a new pipeline schedule
would cause the total number of pipeline schedules to exceed the limit, the
Manisha Singh's avatar
Manisha Singh committed
372
pipeline schedule is not created.
373

Craig Norris's avatar
Craig Norris committed
374
GitLab SaaS subscribers have different limits [defined per plan](../user/gitlab_com/index.md#gitlab-cicd),
375 376
and they affect all projects under that plan.

Craig Norris's avatar
Craig Norris committed
377 378
On [GitLab Premium](https://about.gitlab.com/pricing/) self-managed or
higher installations, this limit is defined under a `default` plan that affects all
379
projects. By default, there is a limit of `10` pipeline schedules.
380

381
To set this limit for a self-managed installation, run the following in the
382
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
383 384

```ruby
385
Plan.default.actual_limits.update!(ci_pipeline_schedules: 100)
386 387
```

388 389 390 391 392 393
### Number of instance level variables

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/216097) in GitLab 13.1.

The total number of instance level CI/CD variables is limited at the instance level.
This limit is checked each time a new instance level variable is created. If a new variable
Manisha Singh's avatar
Manisha Singh committed
394
would cause the total number of variables to exceed the limit, the new variable is created.
395 396 397 398 399

On self-managed instances this limit is defined for the `default` plan. By default,
this limit is set to `25`.

To update this limit to a new value on a self-managed installation, run the following in the
400
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
401 402

```ruby
403
Plan.default.actual_limits.update!(ci_instance_level_variables: 30)
404 405
```

406 407
### Maximum file size per type of artifact

408
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/37226) in GitLab 13.3.
409

410
Job artifacts defined with [`artifacts:reports`](../ci/yaml/index.md#artifactsreports)
411
that are uploaded by the runner are rejected if the file size exceeds the maximum
412
file size limit. The limit is determined by comparing the project's
413
[maximum artifact size setting](../user/admin_area/settings/continuous_integration.md#maximum-artifacts-size)
414 415 416 417 418 419 420 421 422 423
with the instance limit for the given artifact type, and choosing the smaller value.

Limits are set in megabytes, so the smallest possible value that can be defined is `1 MB`.

Each type of artifact has a size limit that can be set. A default of `0` means there
is no limit for that specific artifact type, and the project's maximum artifact size
setting is used:

| Artifact limit name                         | Default value |
|---------------------------------------------|---------------|
424 425 426 427 428
| `ci_max_artifact_size_accessibility`              | 0             |
| `ci_max_artifact_size_api_fuzzing`                | 0             |
| `ci_max_artifact_size_archive`                    | 0             |
| `ci_max_artifact_size_browser_performance`        | 0             |
| `ci_max_artifact_size_cluster_applications`       | 0             |
429
| `ci_max_artifact_size_cluster_image_scanning`     | 0             |
430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451
| `ci_max_artifact_size_cobertura`                  | 0             |
| `ci_max_artifact_size_codequality`                | 0             |
| `ci_max_artifact_size_container_scanning`         | 0             |
| `ci_max_artifact_size_coverage_fuzzing`           | 0             |
| `ci_max_artifact_size_dast`                       | 0             |
| `ci_max_artifact_size_dependency_scanning`        | 0             |
| `ci_max_artifact_size_dotenv`                     | 0             |
| `ci_max_artifact_size_junit`                      | 0             |
| `ci_max_artifact_size_license_management`         | 0             |
| `ci_max_artifact_size_license_scanning`           | 0             |
| `ci_max_artifact_size_load_performance`           | 0             |
| `ci_max_artifact_size_lsif`                       | 100 MB ([Introduced at 20 MB](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/37226) in GitLab 13.3 and [raised to 100 MB](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/46980) in GitLab 13.6.) |
| `ci_max_artifact_size_metadata`                   | 0             |
| `ci_max_artifact_size_metrics_referee`            | 0             |
| `ci_max_artifact_size_metrics`                    | 0             |
| `ci_max_artifact_size_network_referee`            | 0             |
| `ci_max_artifact_size_performance`                | 0             |
| `ci_max_artifact_size_requirements`               | 0             |
| `ci_max_artifact_size_sast`                       | 0             |
| `ci_max_artifact_size_secret_detection`           | 0             |
| `ci_max_artifact_size_terraform`                  | 5 MB ([introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/37018) in GitLab 13.3) |
| `ci_max_artifact_size_trace`                      | 0             |
452

Craig Norris's avatar
Craig Norris committed
453
For example, to set the `ci_max_artifact_size_junit` limit to 10 MB on a self-managed
454
installation, run the following in the [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
455 456 457 458 459

```ruby
Plan.default.actual_limits.update!(ci_max_artifact_size_junit: 10)
```

460 461 462 463 464 465 466 467 468 469 470 471 472 473 474
### Number of files per GitLab Pages web-site

The total number of file entries (including directories and symlinks) is limited to `100000` per
GitLab Pages website.

This is the default limit for all [GitLab self-managed and SaaS plans](https://about.gitlab.com/pricing/).

You can update the limit in your self-managed instance using the
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session).
For example, to change the limit to `100`:

```ruby
Plan.default.actual_limits.update!(pages_file_entries: 100)
```

475 476 477 478
### Number of registered runners per scope

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/321368) in GitLab 13.12.

479 480 481
The total number of registered runners is limited at the group and project levels. Each time a new runner is registered,
GitLab checks these limits against runners that have been active in the last 3 months.
A runner's registration fails if it exceeds the limit for the scope determined by the runner registration token.
482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499

- GitLab SaaS subscribers have different limits defined per plan, affecting all projects using that plan.
- Self-managed GitLab Premium and Ultimate limits are defined by a default plan that affects all projects:

    | Runner scope                                | Default value |
    |---------------------------------------------|---------------|
    | `ci_registered_group_runners`               | 1000          |
    | `ci_registered_project_runners`             | 1000          |

    To update these limits, run the following in the
    [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):

    ```ruby
    # Use ci_registered_group_runners or ci_registered_project_runners
    # depending on desired scope
    Plan.default.actual_limits.update!(ci_registered_project_runners: 100)
    ```

500 501
### Maximum file size for job logs

502 503
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/276192) in GitLab 14.1, disabled by default.
> - Enabled by default and [feature flag `ci_jobs_trace_size_limit` removed](https://gitlab.com/gitlab-org/gitlab/-/issues/335259) in GitLab 14.2.
504

505
The job log file size limit is 100 megabytes by default. Any job that exceeds this value is dropped.
506

507 508
You can change the limit in the [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session).
Update `ci_jobs_trace_size_limit` with the new value in megabytes:
509 510 511 512 513

```ruby
Plan.default.actual_limits.update!(ci_jobs_trace_size_limit: 125)
```

514 515
## Instance monitoring and metrics

516 517
### Incident Management inbound alert limits

518
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/17859) in GitLab 12.5.
519 520 521 522 523 524 525 526 527

Limiting inbound alerts for an incident reduces the number of alerts (issues)
that can be created within a period of time, which can help prevent overloading
your incident responders with duplicate issues. You can reduce the volume of
alerts in the following ways:

- Max requests per period per project, 3600 seconds by default.
- Rate limit period in seconds, 3600 seconds by default.

528 529
### Prometheus Alert JSON payloads

530
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/19940) in GitLab 12.6.
531 532 533

Prometheus alert payloads sent to the `notify.json` endpoint are limited to 1 MB in size.

Sean Arnold's avatar
Sean Arnold committed
534
### Generic Alert JSON payloads
535 536 537 538 539

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/16441) in GitLab 12.4.

Alert payloads sent to the `notify.json` endpoint are limited to 1 MB in size.

540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571
### Metrics dashboard YAML files

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/34834) in GitLab 13.2.

The memory occupied by a parsed metrics dashboard YAML file cannot exceed 1 MB.

The maximum depth of each YAML file is limited to 100. The maximum depth of a YAML
file is the amount of nesting of its most nested key. Each hash and array on the
path of the most nested key counts towards its depth. For example, the depth of the
most nested key in the following YAML is 7:

```yaml
dashboard: 'Test dashboard'
links:
- title: Link 1
  url: https://gitlab.com
panel_groups:
- group: Group A
  priority: 1
  panels:
  - title: "Super Chart A1"
    type: "area-chart"
    y_label: "y_label"
    weight: 1
    max_value: 1
    metrics:
    - id: metric_a1
      query_range: 'query'
      unit: unit
      label: Legend Label
```

572 573 574 575
## Environment Dashboard limits **(PREMIUM)**

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/33895) in GitLab 13.4.

576
See [Environment Dashboard](../ci/environments/environments_dashboard.md#adding-a-project-to-the-dashboard) for the maximum number of displayed projects.
577

578 579 580 581 582 583
## Environment data on Deploy Boards

[Deploy Boards](../user/project/deploy_boards.md) load information from Kubernetes about
Pods and Deployments. However, data over 10 MB for a certain environment read from
Kubernetes won't be shown.

584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603
## Merge requests

### Diff limits

GitLab has limits around:

- The patch size for a single file. [This is configurable on self-managed instance](../user/admin_area/diff_limits.md).
- The total size of all the diffs for a merge request.

An upper and lower limit applies to each of these:

- The number of changed files.
- The number of changed lines.
- The cumulative size of the changes displayed.

The lower limits result in additional diffs being collapsed. The higher limits
prevent any more changes from rendering. For more information about these limits,
[read the development documentation](../development/diffs.md#diff-limits).

### Merge request reports size limit
604 605 606

Reports that go over the 20 MB limit won't be loaded. Affected reports:

607
- [Merge request security reports](../user/project/merge_requests/testing_and_reports_in_merge_requests.md#security-reports)
608
- [CI/CD parameter `artifacts:expose_as`](../ci/yaml/index.md#artifactsexpose_as)
609
- [Unit test reports](../ci/unit_test_reports.md)
610

611
## Advanced Search limits
612

613 614 615 616 617
### Maximum file size indexed

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/8638) in GitLab 13.3.

You can set a limit on the content of repository files that are indexed in
618
Elasticsearch. Any files larger than this limit only index the file name.
619
The file content is neither indexed nor searchable.
620

621 622
Setting a limit helps reduce the memory usage of the indexing processes and
the overall index size. This value defaults to `1024 KiB` (1 MiB) as any
623 624
text files larger than this likely aren't meant to be read by humans.

Craig Norris's avatar
Craig Norris committed
625
You must set a limit, as unlimited file sizes aren't supported. Setting this
626
value to be greater than the amount of memory on GitLab Sidekiq nodes causes
Manisha Singh's avatar
Manisha Singh committed
627 628
the GitLab Sidekiq nodes to run out of memory, as this amount of memory
is pre-allocated during indexing.
629

630 631
### Maximum field length

632
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/201826) in GitLab 12.8.
633

634
You can set a limit on the content of text fields indexed for Advanced Search.
635
Setting a maximum helps to reduce the load of the indexing processes. If any
636 637 638 639 640
text field exceeds this limit, then the text is truncated to this number of
characters. The rest of the text is not indexed, and not searchable.
This applies to all indexed data except repository files that get
indexed, which have a separate limit. For more information, read
[Maximum file size indexed](#maximum-file-size-indexed).
641

642 643
- On GitLab.com, the field length limit is 20,000 characters.
- For self-managed installations, the field length is unlimited by default.
644

645 646
You can configure this limit for self-managed installations when you
[enable Elasticsearch](../integration/elasticsearch.md#enabling-advanced-search).
647
Set the limit to `0` to disable it.
648 649 650

## Wiki limits

651
- [Wiki page content size limit](wikis/index.md#wiki-page-content-size-limit).
652
- [Length restrictions for file and directory names](../user/project/wiki/index.md#length-restrictions-for-file-and-directory-names).
653

654 655
## Snippets limits

656
See the [documentation about Snippets settings](snippets/index.md).
657

658 659 660 661
## Design Management limits

See the [Design Management Limitations](../user/project/issues/design_management.md#limitations) section.

662 663 664 665
## Push Event Limits

### Webhooks and Project Services

666
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/31009) in GitLab 12.4.
667 668 669 670 671 672 673

Total number of changes (branches or tags) in a single push. If changes are more
than the specified limit, hooks won't be executed.

More information can be found in these docs:

- [Webhooks push events](../user/project/integrations/webhooks.md#push-events)
674
- [Project services push hooks limit](../user/project/integrations/overview.md#push-hooks-limit)
675 676 677

### Activities

678
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/31007) in GitLab 12.4.
679 680

Total number of changes (branches or tags) in a single push to determine whether
Manisha Singh's avatar
Manisha Singh committed
681
individual push events or a bulk push event are created.
682 683

More information can be found in the [Push event activities limit and bulk push events documentation](../user/admin_area/settings/push_event_activities_limit.md).
684 685 686 687 688 689 690

## Package Registry Limits

### File Size Limits

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/218017) in GitLab 13.4.

691 692
On GitLab.com, the maximum file size for a package that's uploaded to the [GitLab Package Registry](../user/packages/package_registry/index.md) varies by format:

693 694 695 696 697 698
- Conan: 5 GB
- Generic: 5 GB
- Maven: 5 GB
- npm: 5 GB
- NuGet: 5 GB
- PyPI: 5 GB
699

700
To set this limit for a self-managed installation, run the following in the
701
[GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session):
702 703 704 705 706 707 708

```ruby
# File size limit is stored in bytes

# For Conan Packages
Plan.default.actual_limits.update!(conan_max_file_size: 100.megabytes)

Suzanne Selhorn's avatar
Suzanne Selhorn committed
709
# For npm Packages
710 711 712 713 714 715 716 717 718 719
Plan.default.actual_limits.update!(npm_max_file_size: 100.megabytes)

# For NuGet Packages
Plan.default.actual_limits.update!(nuget_max_file_size: 100.megabytes)

# For Maven Packages
Plan.default.actual_limits.update!(maven_max_file_size: 100.megabytes)

# For PyPI Packages
Plan.default.actual_limits.update!(pypi_max_file_size: 100.megabytes)
Mathieu Parent's avatar
Mathieu Parent committed
720 721 722

# For Debian Packages
Plan.default.actual_limits.update!(debian_max_file_size: 100.megabytes)
723 724 725

# For Generic Packages
Plan.default.actual_limits.update!(generic_packages_max_file_size: 100.megabytes)
726 727 728
```

Set the limit to `0` to allow any file size.
729 730 731 732

### Package versions returned

When asking for versions of a given NuGet package name, the GitLab Package Registry returns a maximum of 300 versions.
733

734
## Branch retargeting on merge **(FREE SELF)**
735 736 737

> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/320902) in GitLab 13.9.

738 739 740
If a branch is merged while open merge requests still point to it, GitLab can
retarget merge requests pointing to the now-merged branch. To learn more, read
[Branch retargeting on merge](../user/project/merge_requests/getting_started.md#branch-retargeting-on-merge).