Add docs for runner fleet dashboard early adopters program

What does this MR do and why?

Addresses Write documentation for using CI Analytics with... (#424500 - closed)

We want to test the new Runner Fleet dashboard with a few selected self-managed clients. This MR provides the documentation on how to setup Clickhouse database and enable necessary feature flags for such tests.

This page is intentionally placed in our development section of the documentation and not the user one. The idea is to emphasize that using Clickhouse is still experimental, and we don't yet fully support it.

I also plan to record a video walking through this.

Ideally in the future this documentation should be broken into 3 separate pages:

1. Normal dashboard documentation which doesn't require Clickhouse
2. Clickhouse setup docs
3. Dashboard setup docs

But I on purpose budled it up toghether into a single page for now.

Review app: http://main-ee-135227.docs.gitlab-review.app/ee/development/runner_fleet_dashboard.html

Screenshots or screen recordings

I'm still working on this.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

assigned to @vshushlin

Proper labels assigned to this merge request. Please ignore me.

@vshushlin - please see the following guidance and update this merge request.

	1 Error
	Please add typebug typefeature, or typemaintenance label to this merge request.

added 1 commit

• d33cf5db - WIP: add docs for runner fleet dashboard

Compare with previous version

added docs-only label

Setting label grouprunner based on @vshushlin's group.

added grouprunner label

Setting label(s) devopsverify sectionci based on grouprunner.

added devopsverify sectionci labels

added 1 commit

• f5d13e74 - WIP: add docs for runner fleet dashboard

Compare with previous version

added 1 commit

• d3ea93f4 - Add docs for runner fleet dashboard early adopters program

Compare with previous version

changed title from WIP: add docs for runner fleet dashboard to Add docs for runner fleet dashboard

marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed

changed milestone to %16.6

added [Deprecated] Category:Runner Fleet clickhouse documentation featureaddition typefeature workflowin review labels

resolved all threads

@fneill @pedropombeiro can you do the first review pass on this?

I'm still working on it, but I consider it's ready for review.

changed title from Add docs for runner fleet dashboard to Add docs for runner fleet dashboard early adopters program

requested review from @fneill

added Technical Writing label

approved this merge request

Hey @vshushlin thanks again for providing these docs! I've added a few suggestions. While it seems like there are a lot they're mainly for style. Usually docs in the /development folder don't undergo such a heavy review, but since this is for a Beta feature, I wanted to make sure the page adheres to the style guidelines and structures in the user docs.

added 1 commit

• 00a2ee02 - Add docs for runner fleet dashboard early adopters program

Compare with previous version

assigned to @pedropombeiro

added 1 commit

• 6f21a9e2 - Add docs for runner fleet dashboard early adopters program

Compare with previous version

added 835 commits

• 6f21a9e2...bf567056 - 833 commits from branch master
• 99b79e38 - Add docs for runner fleet dashboard early adopters program
• 5e42c614 - Address MR review suggestions

Compare with previous version

added 1 commit

• 0969a940 - Address MR review suggestions

Compare with previous version

approved this merge request

added 99 commits

• 0969a940...edc8f701 - 96 commits from branch master
• d1fa4a4d - Add docs for runner fleet dashboard early adopters program
• c742bcd5 - Address MR review suggestions
• 8ecadd5b - Address MR review comment

Compare with previous version

added 1 commit

• 235825ba - Add link to ClickHouse self-managed recommendations

Compare with previous version

We should a note that the other metrics (except for wait time to pick up a job) will load without Clickhouse. Of course only if this assumption is correct.

added 1 commit

• b1cfd6d1 - Apply 2 suggestion(s) to 1 file(s)

Compare with previous version

added 418 commits

• b1cfd6d1...a4fb2903 - 412 commits from branch master
• 01e6abb4 - Add docs for runner fleet dashboard early adopters program
• 7f8f467c - Address MR review suggestions
• ef7c202d - Address MR review comment
• 30906059 - Add link to ClickHouse self-managed recommendations
• 9d3feddf - Apply 2 suggestion(s) to 1 file(s)
• f5b907ce - Add queue wait times to list of features

Compare with previous version

mentioned in merge request gitlab-com/www-gitlab-com!130597 (merged)

approved this merge request

added 860 commits

• f5b907ce...63fbe576 - 853 commits from branch master
• fc6ff154 - Add docs for runner fleet dashboard early adopters program
• 596d1842 - Address MR review suggestions
• 3f37a71a - Address MR review comment
• 66fa3c1c - Add link to ClickHouse self-managed recommendations
• 34ba83fe - Apply 2 suggestion(s) to 1 file(s)
• 37ebc788 - Add queue wait times to list of features
• 96a94425 - Apply Gina's suggestion

Compare with previous version

added clickhousereview pending label

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/development/img/runner_fleet_dashboard.png (Link to current live version)
• doc/development/runner_fleet_dashboard.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added 1 commit

• 8786def6 - Minor style corrections

Compare with previous version

resolved all threads

enabled an automatic merge when the pipeline for 5cb1b94e succeeds

merged

mentioned in commit 7b3f5efa

@vshushlin now that !136103 (merged) is merged, should we update these instructions so that users rely on the migrations, instead of duplicating the schema here? This will also ensure they have the latest schema.

added workflowstaging-canary label and removed workflowin review label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added workflowpost-deploy-db-production label and removed workflowproduction label

added releasedcandidate label