Skip to content

Commit 20e4c53

Browse files
committed
wip docs edits
1 parent dfc06ff commit 20e4c53

File tree

2 files changed

+28
-56
lines changed

2 files changed

+28
-56
lines changed

docs/vendor/compatibility-matrix-usage.md

Lines changed: 27 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -1,84 +1,58 @@
1-
# Compatibility Matrix Usage
1+
# Viewing Compatibility Matrix Usage History
22
This topic describes using the Replicated Vendor Portal to understand
33
Compatibility Matrix usage across your team.
44

5-
## Currently Active Clusters and Virtual Machines
6-
You can find current active clusters and virtual machines (VMs) on the Compatibility
7-
Matrix overview page which is accessible by clicking the **Compatibility Matrix**
8-
tab and then selecting **Overview** from the sidebar.
9-
10-
![Compatibility Matrix Overview Page](/images/compatibility-matrix-overview.png)
11-
12-
For more information on the Cluster and VM statuses displayed on this page
13-
see [Cluster Status](/vendor/testing-about#cluster-status).
14-
15-
## Historical Usage
16-
The Vendor Portal offers a Compatibility Matrix history page that provides
17-
historical information about both clusters and virtual machines.
18-
19-
You can access the Compatibility Matrix history page by clicking the
20-
**Compatibility Matrix** tab and then selecting **History** from the sidebar.
21-
22-
Only terminated clusters and VMs are displayed on the history page. Terminated
23-
is defined as a cluster or VM that has been deleted or errored.
5+
## View Historical Usage
6+
The **Compatibility Matrix > History** page provides
7+
historical information about both clusters and VMs, as shown below:
248

259
![Compatibility Matrix History Page](/images/compatibility-matrix-history.png)
10+
[View a larger version of this image](/images/compatibility-matrix-history.png)
11+
12+
Only _terminated_ clusters and VMs that have been deleted or errored are displayed on the **History** page.
2613

27-
The top of the page displays the total number of terminated clusters and VMs
14+
The top of the **History** page displays the total number of terminated clusters and VMs
2815
in the selected time period as well as the total cost and usage time for
2916
the terminated resources.
3017

31-
The table below includes cluster and VM entries with the following columns:
18+
The table includes cluster and VM entries with the following columns:
3219
- **Name:** The name of the cluster or VM.
3320
- **By:** The actor that created the resource.
34-
- **Cost:** The cost of the resource, this is calculated at termination and is
21+
- **Cost:** The cost of the resource. This is calculated at termination and is
3522
based on the time the resource was running.
36-
- **Distribution:** The distribution and version of the resource, for example
23+
- **Distribution:** The distribution and version of the resource. For example,
3724
`kind 1.32.1`.
38-
- **Type:** The distribution type of the resource. Kubernetes clusters
25+
- **Type:** The distribution type of the resource. Kubernetes clusters
3926
are listed as `kubernetes` and VMs are listed as `vm`.
40-
- **Status:** The status of the resource, for example `terminated` or `error`.
41-
- **Instance:** The instance type of the resource, for example `r1.small`.
42-
- **Nodes:** The node count for "kubernetes" resources, VMs do not use this
27+
- **Status:** The status of the resource. For example `terminated` or `error`.
28+
- **Instance:** The instance type of the resource. For example `r1.small`.
29+
- **Nodes:** The node count for "kubernetes" resources. VMs do not use this
4330
field.
44-
- **Node Groups:** The node group count for "kubernetes" resources, VMs do not
31+
- **Node Groups:** The node group count for "kubernetes" resources. VMs do not
4532
use this field.
4633
- **Created At:** The time the resource was created.
47-
- **Running At:** The time the resource started running. For billing purposes,
34+
- **Running At:** The time the resource started running. For billing purposes,
4835
this is the time when Replicated began charging for the resource.
49-
- **Terminated At:** The time the resource was terminated. For billing
36+
- **Terminated At:** The time the resource was terminated. For billing
5037
purposes, this is the time when Replicated stopped charging for the resource.
51-
- **TTL:** The time-to-live for the resource, this is the maximum amount of
38+
- **TTL:** The time-to-live for the resource. This is the maximum amount of
5239
time the resource can run before it is automatically terminated.
53-
- **Duration:** The total time the resource was running, this is the time
40+
- **Duration:** The total time the resource was running. This is the time
5441
between the `running` and `terminated` states.
5542
- **Tag:** Any tags that were applied to the resource.
5643

57-
Each of these fields can be filtered and sorted to help you find the information
58-
you are looking for. To sort by a specific field, click on the column header.
59-
The column will display an up or down arrow to denote that the column is being
60-
sorted and the direction of the sort:
44+
## Filter and Sort Usage History
6145

62-
![Compatibility Matrix History Page, column header clicked](/images/compatibility-matrix-column-sort.png)
46+
Each of the fields on the **History** page can be filtered and sorted. To sort by a specific field, click on the column header.
6347

64-
To filter by a specific field, click on the filter icon in the column header:
65-
66-
![Compatibility Matrix History Page, filter icon clicked](/images/compatibility-matrix-column-filter.png)
67-
68-
Then use each specific filter input to filter the results:
48+
To filter by a specific field, click on the filter icon in the column header, then use each specific filter input to filter the results, as shown below:
6949

7050
![Compatibility Matrix History Page, filter input](/images/compatibility-matrix-column-filter-input.png)
51+
[View a larger version of this image](/images/compatibility-matrix-column-filter-input.png)
7152

53+
## Get Usage History with the Vendor API v3
7254

73-
## Using the Vendor API v3
74-
You also use the [Vendor API v3](/vendor/vendor-api-using)
75-
to obtain Compatibility Matrix usage information.
76-
77-
To perform queries against the Vendor API v3, you must have a valid API token,
78-
see [Generating API Tokens](/vendor/replicated-api-tokens).
79-
80-
Just like the Vendor Portal, historical and running Compatibility Matrix usage
81-
is divided into distinct endpoints.
55+
For more information about using the Vendor API v3 to get Compatibility Matrix usage history information, see [/v3/cmx/history](https://replicated-vendor-api.readme.io/reference/listcmxhistory) and [/v3/cmx/getcmxstats](https://replicated-vendor-api.readme.io/reference/getcmxstats) in the Vendor API v3 documentation.
8256

8357
### Credit Balance and Summarized Usage
8458
To obtain summarized usage information in addition to your Compatibility Matrix
@@ -255,6 +229,4 @@ curl --request GET \
255229
If any filter is passed for an object that does not exist, no warning is given.
256230
For example, if you filter by `actor-filter=name` and there are no results
257231
the response will be empty.
258-
:::
259-
260-
232+
:::

sidebars.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -208,7 +208,6 @@ const sidebars = {
208208
'vendor/instance-notifications-config',
209209
'vendor/custom-metrics',
210210
'vendor/instance-data-export',
211-
'vendor/compatibility-matrix-usage',
212211
],
213212
},
214213
],
@@ -221,6 +220,7 @@ const sidebars = {
221220
'vendor/testing-pricing',
222221
'vendor/testing-supported-clusters',
223222
'vendor/testing-cluster-addons',
223+
'vendor/compatibility-matrix-usage',
224224
'vendor/testing-how-to',
225225
'vendor/testing-ingress',
226226
],

0 commit comments

Comments
 (0)