Skip to content

Update CMX history info to discuss Queued Timeout status #3276

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 6, 2025
Merged

Update CMX history info to discuss Queued Timeout status #3276

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
36e96d7
Update CMX history info to discuss Queued Timeout status
squizzi May 28, 2025
45d9d3e
docs edits
paigecalvert May 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 10 additions & 5 deletions docs/vendor/compatibility-matrix-usage.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,11 +9,16 @@ historical information about both clusters and VMs, as shown below:
![Compatibility Matrix History Page](/images/compatibility-matrix-history.png)
[View a larger version of this image](/images/compatibility-matrix-history.png)

Only _terminated_ clusters and VMs that have been deleted or errored are displayed on the **History** page.

The top of the **History** page displays the total number of terminated clusters and VMs
in the selected time period as well as the total cost and usage time for
the terminated resources.
The **History** page displays clusters and VMs with one of the following statuses:
* Terminated
* Error
Copy link
Contributor

@paigecalvert paigecalvert May 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • Error

I saw this below on this page: "- Status: The status of the resource. For example terminated or error."

I added "error" to this list because it looked like another one of the possible statuses for the history page

* Queued Timeout. A Queued Timeout status indicates that the cluster or VM was automatically removed after being in a _queued_ state for more than 24 hours.

The top of the **History** page displays the total number of non-running clusters
and VMs in the selected time period as well as the total cost and usage time
for the non-running resources. The total cost is calculated at termination and
is based on the time the resource was running. Clusters and VMs that never
entered the _running_ state are not included in the total cost and usage time.

The table includes cluster and VM entries with the following columns:
- **Name:** The name of the cluster or VM.
Expand Down