elastic · stefnestor · Nov 19, 2024 · Nov 15, 2024 · Nov 18, 2024 · Nov 19, 2024
diff --git a/docs/reference/cluster/allocation-explain.asciidoc b/docs/reference/cluster/allocation-explain.asciidoc
@@ -159,6 +159,8 @@ node.
 <5> The decider which led to the `no` decision for the node.
 <6> An explanation as to why the decider returned a `no` decision, with a helpful hint pointing to the setting that led to the decision. In this example, a newly created index has <<indices-get-settings,an index setting>> that requires that it only be allocated to a node named `nonexistent_node`, which does not exist, so the index is unable to allocate.
 
+See this https://www.youtube.com/watch?v=5z3n2VgusLE[fixing "node does not match index setting" video] for an example troubleshooting walkthrough.
+
 [[maximum-number-of-retries-exceeded]]
 ====== Maximum number of retries exceeded
 
@@ -235,7 +237,7 @@ primary shard that was previously allocated.
 ----
 // NOTCONSOLE
 
-TIP: If a shard is unassigned with an allocation status of `no_valid_shard_copy`, then you should <<fix-cluster-status-recover-nodes,make sure that all nodes are in the cluster>>. If all the nodes containing in-sync copies of a shard are lost, then you can <<fix-cluster-status-restore,recover the data for the shard>>.
+If a shard is unassigned with an allocation status of `no_valid_shard_copy`, then you should <<fix-cluster-status-recover-nodes,make sure that all nodes are in the cluster>>. If all the nodes containing in-sync copies of a shard are lost, then you can <<fix-cluster-status-restore,recover the data for the shard>>. See this https://www.youtube.com/watch?v=6OAg9IyXFO4[fixing "no_valid_shard_copy" video] for an example troubleshooting walkthrough.
 
 ===== Unassigned replica shard
 

diff --git a/docs/reference/ilm/error-handling.asciidoc b/docs/reference/ilm/error-handling.asciidoc
@@ -9,7 +9,8 @@ If {ilm-init} cannot resolve the error automatically, execution is halted
 until you resolve the underlying issues with the policy, index, or cluster.
 
 See this https://www.youtube.com/watch?v=VCIqkji3IwY[{ilm-init} health video] 
-for example troubleshooting walkthrough.
+for example troubleshooting walkthrough of live issues and this https://www.youtube.com/watch?v=onrnnwjYWSQ[{ilm-init} history video]
+for example troubleshooting walkthrough of historical issues.
 
 For example, you might have a `shrink-index` policy that shrinks an index to four shards once it
 is at least five days old: 

diff --git a/docs/reference/snapshot-restore/repository-s3.asciidoc b/docs/reference/snapshot-restore/repository-s3.asciidoc
@@ -6,6 +6,9 @@ You can use AWS S3 as a repository for {ref}/snapshot-restore.html[Snapshot/Rest
 *If you are looking for a hosted solution of Elasticsearch on AWS, please visit
 https://www.elastic.co/cloud/.*
 
+See this https://www.youtube.com/watch?v=ACqfyzWf-xs[connecting an AWS S3 repository video]
+for an example setup walkthrough.
+
 [[repository-s3-usage]]
 ==== Getting started
 

diff --git a/docs/reference/troubleshooting/common-issues/diagnose-unassigned-shards.asciidoc b/docs/reference/troubleshooting/common-issues/diagnose-unassigned-shards.asciidoc
@@ -8,5 +8,6 @@ In order to diagnose the unassigned shards in your deployment use the following
 
 include::{es-ref-dir}/tab-widgets/troubleshooting/data/diagnose-unassigned-shards-widget.asciidoc[]
 
-
+See this https://www.youtube.com/watch?v=v2mbeSd1vTQ[monitoring Allocation health video]
+for an example troubleshooting walkthrough.
 
diff --git a/docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc b/docs/reference/troubleshooting/common-issues/red-yellow-cluster-status.asciidoc
@@ -19,6 +19,8 @@ operate to have a green health status.
 In many cases, your cluster will recover to green health status automatically.
 If the cluster doesn't automatically recover, then you must <<fix-red-yellow-cluster-status,manually address>>
 the remaining problems so management and cleanup activities can proceed.
+See this https://www.youtube.com/watch?v=v2mbeSd1vTQ[monitoring Allocation health video]
+for an example troubleshooting walkthrough.
 
 [discrete]
 [[diagnose-cluster-status]]
@@ -90,6 +92,8 @@ PUT _cluster/settings
 }
 ----
 
+See this https://www.youtube.com/watch?v=MiKKUdZvwnI[fixing "no allocations are allowed" video] for example troubleshooting walkthrough.
+
 [discrete]
 [[fix-cluster-status-recover-nodes]]
 ===== Recover lost nodes
@@ -262,3 +266,5 @@ POST _cluster/reroute
 ----
 // TEST[s/^/PUT my-index\n/]
 // TEST[catch:bad_request]
+
+See this https://www.youtube.com/watch?v=6OAg9IyXFO4[fixing "no_valid_shard_copy" video] for an example troubleshooting walkthrough.
diff --git a/docs/reference/troubleshooting/diagnostic.asciidoc b/docs/reference/troubleshooting/diagnostic.asciidoc
@@ -11,7 +11,7 @@ It works against all {es} versions.
 This information can be used to troubleshoot problems with your cluster. For examples of issues that you can troubleshoot using Support Diagnostic tool output, refer to https://www.elastic.co/blog/why-does-elastic-support-keep-asking-for-diagnostic-files[the Elastic blog].
 
 You can generate diagnostic information using this tool before you contact https://support.elastic.co[Elastic Support] or 
-https://discuss.elastic.co[Elastic Discuss] to minimize turnaround time. 
+https://discuss.elastic.co[Elastic Discuss] to minimize turnaround time. See this https://www.youtube.com/watch?v=Bb6SaqhqYHw[Capture an {es} diagnostic video] for an example walkthrough.
 
 [discrete]
 [[diagnostic-tool-requirements]]
Original file line number	Diff line number	Diff line change
Expand Up		@@ -8,5 +8,6 @@ In order to diagnose the unassigned shards in your deployment use the following

		include::{es-ref-dir}/tab-widgets/troubleshooting/data/diagnose-unassigned-shards-widget.asciidoc[]


		See this https://www.youtube.com/watch?v=v2mbeSd1vTQ[monitoring Allocation health video]
		for an example troubleshooting walkthrough.
stefnestor marked this conversation as resolved. Outdated Show resolved Hide resolved