Disallow tracing configs that trigger tracing for too many requests

Misconfigured tracing configs or tracing configs that are too broad can
trigger tracing for too many requests. This can badly impact the
performance and the availability of the server, if tracing makes
requests more expensive (e.g. if there are expensive logs that are only
written when a request is traced).

Examples for a misconfigured or trace configs that are too broad:
* a tracing config that specifies neither of the match criteria (e.g. it
  contains an unsupported parameter, which can happen is the parameter
  has typo)
* a tracing config that only specifies match criteria that are very
  broad (e.g. requestType=REST which would trigger tracing for all REST
  requests)

Fix this by requiring that tracing configs specify at least one of
requestUriPattern, account and projectPattern.

Release-Notes: Disallowed tracing configs that trigger tracing for too many requests
Bug: Google b/355393231
Change-Id: I9c9fac92f45e427087f7fe705169f73296c0b2c8
Signed-off-by: Edwin Kempin <ekempin@google.com>
4 files changed
tree: 460fc422017ebdb9cfa1ac267cece597d205641c
  1. .github/
  2. .settings/
  3. .ts-out/
  4. antlr3/
  5. contrib/
  6. Documentation/
  7. e2e-tests/
  8. java/
  9. javatests/
  10. lib/
  11. modules/
  12. plugins/
  13. polygerrit-ui/
  14. prolog/
  15. prologtests/
  16. proto/
  17. resources/
  18. tools/
  19. webapp/
  20. .bazelignore
  21. .bazelproject
  22. .bazelrc
  23. .bazelversion
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitignore
  27. .gitmodules
  28. .gitreview
  29. .mailmap
  30. .pydevproject
  31. .zuul.yaml
  32. BUILD
  33. COPYING
  34. INSTALL
  35. Jenkinsfile
  36. MODULE.bazel
  37. package.json
  38. README.md
  39. SUBMITTING_PATCHES
  40. version.bzl
  41. web-dev-server.config.mjs
  42. WORKSPACE
  43. yarn.lock
README.md

Gerrit Code Review

Gerrit is a code review and project management tool for Git based projects.

Build Status Maven Central

Objective

Gerrit makes reviews easier by showing changes in a side-by-side display, and allowing inline comments to be added by any reviewer.

Gerrit simplifies Git based project maintainership by permitting any authorized user to submit changes to the master Git repository, rather than requiring all approved changes to be merged in by hand by the project maintainer.

Documentation

For information about how to install and use Gerrit, refer to the documentation.

Source

Our canonical Git repository is located on googlesource.com. There is a mirror of the repository on Github.

Reporting bugs

Please report bugs on the issue tracker.

Contribute

Gerrit is the work of hundreds of contributors. We appreciate your help!

Please read the contribution guidelines.

Note that we do not accept Pull Requests via the Github mirror.

Getting in contact

The Developer Mailing list is repo-discuss on Google Groups.

License

Gerrit is provided under the Apache License 2.0.

Build

Install Bazel and run the following:

    git clone --recurse-submodules https://gerrit.googlesource.com/gerrit
    cd gerrit && bazel build release

Install binary packages (Deb/Rpm)

The instruction how to configure GerritForge/BinTray repositories is here

On Debian/Ubuntu run:

    apt-get update && apt-get install gerrit=<version>-<release>

NOTE: release is a counter that starts with 1 and indicates the number of packages that have been released with the same version of the software.

On CentOS/RedHat run:

    yum clean all && yum install gerrit-<version>[-<release>]

On Fedora run:

    dnf clean all && dnf install gerrit-<version>[-<release>]

Use pre-built Gerrit images on Docker

Docker images of Gerrit are available on DockerHub

To run a CentOS 8 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-centos8

To run a Ubuntu 20.04 based Gerrit image:

    docker run -p 8080:8080 gerritcodereview/gerrit[:version]-ubuntu20

NOTE: release is optional. Last released package of the version is installed if the release number is omitted.