GITBOOK-791: Remove traces of CI analytics

Author: Riley Draward

billing.md

@@ -12,13 +12,13 @@ Trunk offers a free plan to experiment with each of our features. Each feature h
 
 Similar to [calculating user counts](billing.md#calculating-user-counts), our free tier limits are calculated based on a 30-day rolling window.
 
-<table><thead><tr><th width="155">Feature</th><th width="257">Metric</th><th>Free Tier Limit</th></tr></thead><tbody><tr><td>All</td><td>Users</td><td>5 commiters per month, unlimited on public repos</td></tr><tr><td>Code Quality</td><td>Quality &#x26; security metrics</td><td>Up to 100k issues uploaded</td></tr><tr><td>Merge Queue</td><td>PRs merged per month</td><td>100 PRs merged per month</td></tr><tr><td>CI Analytics</td><td>Real-time ingestion of data</td><td>14 days per repo</td></tr><tr><td>Flaky Tests</td><td>Number of <a data-footnote-ref href="#user-content-fn-1">test spans</a></td><td>5 committers and 5M test spans per month</td></tr><tr><td></td><td>Data backfilling</td><td>Up to 30 days</td></tr></tbody></table>
+<table><thead><tr><th width="155">Feature</th><th width="257">Metric</th><th>Free Tier Limit</th></tr></thead><tbody><tr><td>All</td><td>Users</td><td>5 commiters per month, unlimited on public repos</td></tr><tr><td>Code Quality</td><td>Quality &#x26; security metrics</td><td>Up to 100k issues uploaded</td></tr><tr><td>Merge Queue</td><td>PRs merged per month</td><td>100 PRs merged per month</td></tr><tr><td>Flaky Tests</td><td>Number of <a data-footnote-ref href="#user-content-fn-1">test spans</a></td><td>5 committers and 5M test spans per month</td></tr><tr><td></td><td>Data backfilling</td><td>Up to 30 days</td></tr></tbody></table>
 
 #### Team Plans
 
 Trunk Team Plans offers a monthly subscription plan using a per-seat model. At the end of every billing period, we calculate the number of users using Trunk and update the next month’s invoice to reflect the latest user count. Each seat has access to all of Trunk's features.
 
-<table><thead><tr><th width="155">Feature</th><th width="257">Metric</th><th>Limits</th></tr></thead><tbody><tr><td>Code Quality</td><td>Quality &#x26; security metrics</td><td>Unlimited</td></tr><tr><td>Merge Queue</td><td>PRs merged per month</td><td>Unlimited</td></tr><tr><td>CI Analytics</td><td>Real-time ingestion of data</td><td>Unlimited</td></tr><tr><td>Flaky Tests</td><td>Number of <a data-footnote-ref href="#user-content-fn-1">test spans</a></td><td><p>1 million test spans per seat per month.</p><p>$3 for each additional 1 million test spans.</p></td></tr></tbody></table>
+<table><thead><tr><th width="155">Feature</th><th width="257">Metric</th><th>Limits</th></tr></thead><tbody><tr><td>Code Quality</td><td>Quality &#x26; security metrics</td><td>Unlimited</td></tr><tr><td>Merge Queue</td><td>PRs merged per month</td><td>Unlimited</td></tr><tr><td>Flaky Tests</td><td>Number of <a data-footnote-ref href="#user-content-fn-1">test spans</a></td><td><p>1 million test spans per seat per month.</p><p>$3 for each additional 1 million test spans.</p></td></tr></tbody></table>
 
 #### **Enterprise Plans**
 

code-quality/licensing.md

@@ -11,7 +11,6 @@ Trunk Code Quality is composed of a closed-source core complemented by open-sour
 #### Closed-Source Components
 
 * Trunk CLI: The core command-line tool is closed-source but free to use under specific conditions.
-* Trunk Web App: Provides reporting, analytics, and a dashboard to view codebase issues and track health over time.
 * VS Code Extension: Integrates Trunk Code Quality directly into your development environment. Under the hood, all code-checking by the VS Code extension is completed via the Trunk CLI, which drives the VS Code extension.
 
 #### Open-Source Components

merge-queue/managing-merge-queue/metrics.md

@@ -9,9 +9,7 @@ Your merge experience directly impacts the velocity and productivity of your dev
 You can access the metrics in your Trunk Merge Queue by navigating to the Trunk Web App > **Merge Queue** > **Health**. 
 
 {% hint style="info" %}
-#### Enabling CI Time and CI Jobs Triggered
-
-[Pushing data to CI Analytics](https://docs.trunk.io/ci-analytics/setup) is required to enable CI Time and CI Jobs Triggered charts if you're **not using GitHub Actions**.
+CI Time and CI Jobs Triggered charts are only available for **GitHub Actions**.
 {% endhint %}
 
 ### Time Buckets
@@ -57,7 +55,7 @@ The time in queue can be displayed as different statistical measures. You can sh
 CI Time measures the time it takes to test each pull request in the merge queue. Specifically, how long CI jobs have to run to test PRs. This measures **only CI steps relevant to the merge queue**, other CI steps like build or deploy or any workflows outside of the merge queue will not be measured.
 
 {% hint style="info" %}
-[Pushing data to CI Analytics](https://docs.trunk.io/ci-analytics/setup) is required to enable CI Time and CI Jobs Triggered charts if you're **not using GitHub Actions**.
+CI Time and CI Jobs Triggered charts are only available for **GitHub Actions**.
 {% endhint %}
 
 Monitoring the amount of time it takes for CI workflows to test PRs is important for making sure PRs can move through the queue quickly. The more time it takes to test PRs, the more time a PR will be in the queue. Large spikes signal that work should be devoted to reducing the length of bottlenecking CI jobs, or more CI resources are needed.
@@ -79,5 +77,5 @@ The count of Individual CI jobs that are triggered to test PRs in the merge queu
 Each job will require a CI runner. A spike or large number of requested jobs can result in PRs waiting longer to begin testing. 
 
 {% hint style="info" %}
-[Pushing data to CI Analytics](https://docs.trunk.io/ci-analytics/setup) is required to enable CI Time and CI Jobs Triggered charts if you're **not using GitHub Actions**.
+CI Time and CI Jobs Triggered charts are only available for **GitHub Actions**.
 {% endhint %}

merge-queue/set-up-trunk-merge/advanced-settings.md

@@ -20,10 +20,6 @@ There is an additional state `Switching Modes` that functions exactly like `Drai
 
 Configure how long a PR's test can run before auto-cancelling while testing in the Merge Queue. If a long-running test is detected, Merge will automatically cancel the test.
 
-{% hint style="info" %}
-If you're unsure about what timeout to set, you can use our [CI Analytics](https://trunk.io/ci-analytics) to analyze the runtime of your CI.
-{% endhint %}
-
 For example, assuming a timeout of 4 hours:
 
 * At 3:00, Bob submits PR 456 to the Merge Queue.