Skip to content
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

[version-3-4] Fix Download cluster logs URL in troubleshooting.md (#1535) #1539

Merged
merged 1 commit into from
Sep 12, 2023
Merged

[version-3-4] Fix Download cluster logs URL in troubleshooting.md (#1535) #1539

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions docs/docs-content/troubleshooting/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ Use the following troubleshooting resources to help you address issues that may
## Download Cluster Logs
At times it might be required to work with the Spectro Cloud support team to troubleshoot an issue. Spectro Cloud provides the ability to aggregate logs from the clusters it manages. Problems that occur during the orchestration life cycle may require access to the various containers, nodes, and Kube system logs. Spectro Cloud automates this log collection process and provides an easy download option from the Spectro Cloud UI console. Hence reduces the burden on the operator to login into various cluster nodes individually and fetch these logs.

Follow the link for more details: [Download Cluster Logs](/clusters/#downloadclusterlogs)
Follow the link for more details: [Download Cluster Logs](/clusters/#download-cluster-logs)

## Event Stream

Expand All @@ -53,4 +53,4 @@ Spectro Cloud maintains specific milestones in a life cycle and presents them as

For example, failure to create a virtual machine in AWS due to the vCPU limit being exceeded would cause this error is shown to the end-users. They could choose to bring down some workloads in the AWS cloud to free up space. The next time a VM creation task is attempted, it would succeed and the condition would be marked as a success.

<br />
<br />