Skip to content

Move Praefect Grafana docs to a distinct step

James Ramsay (ex-GitLab) requested to merge docs/jramsay/praefect-grafana into master

What does this MR do?

Grafana is important for observing the behvaiour of Gitaly HA, and should be prominent step with detailed information about how to monitor the cluster. This first step moves the Grafana docs to its own section.

Related issues

Closes gitaly#2550 (closed)

Author's checklist

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

  • Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

  • Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.

3. Maintainer

  1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
  2. Ensure a release milestone is set.
  3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

Merge request reports