Metrics

The @PLUGIN@ plugin exports several metrics which can give insights into the usage and performance of the code owners functionality.

Latency Metrics

  • compute_changed_files_against_auto_merge: Latency for computing changed files against auto merge.
  • compute_changed_files_against_first_parent: Latency for computing changed files against first parent.
  • compute_file_status: Latency for computing the file status for one file.
  • compute_file_statuses: Latency for computing file statuses for all files in a change.
  • compute_owned_paths: Latency for computing file statuses.
  • compute_owned_paths: Latency for computing the files in a change that are owned by a user.
  • prepare_file_status_computation: Latency for preparing the file status computation.
  • prepare_file_status_computation_for_account: Latency for preparing the file status computation for an account.
  • resolve_code_owner_config: Latency for resolving a code owner config file.
  • resolve_code_owner_config_import: Latency for resolving an import of a code owner config file.
  • resolve_code_owner_config_imports: Latency for resolving all imports of a code owner config file.
  • run_code_owner_submit_rule: Latency for running the code owner submit rule.

Code Owner Config Latency Metrics

  • load_code_owner_config: Latency for loading a code owner config file (read + parse).
  • parse_code_owner_config: Latency for parsing a code owner config file.
  • read_code_owner_config: Latency for reading a code owner config file.

Counter Metrics

  • count_code_owner_config_reads: Total number of code owner config reads from backend.
  • count_code_owner_config_cache_reads: Total number of code owner config reads from cache.

Back to @PLUGIN@ documentation index

Part of Gerrit Code Review