-
Notifications
You must be signed in to change notification settings - Fork 106
Adds applies_to tags to Troubleshoot > Elastic Cloud #880
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.
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,7 @@ | ||
--- | ||
navigation_title: "Serverless" | ||
applies_to: | ||
serverless: all | ||
--- | ||
|
||
# Troubleshoot {{serverless-full}} | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
--- | ||
navigation_title: "Deployment health warnings" | ||
applies_to: | ||
deployment: | ||
ess: all | ||
Comment on lines
+4
to
+5
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This page should have an equivalent in the Elastic Cloud Enterprise section (it's even in the mapped page of this file), but I'm not seeing it in the preview. If you choose to duplicate + adjust it for ECE, then no need to change the applies_to tags for this one. But in the meantime or if treated separately/later, maybe we could just add "ece: all" as well here. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hey @marciw I could be misremembering, but I think we worked on consolidating these duplicates intentionally? If that's the case and we don't plan on having a separate ECE topic, then I'll go ahead and add the There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @natasha-moore-elastic eek, I think this is a byproduct of a change in the structure early on... I'd say go ahead and add |
||
ece: all | ||
mapped_pages: | ||
- https://www.elastic.co/guide/en/cloud/current/ec-deployment-no-op.html | ||
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-deployment-no-op.html | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,9 @@ | ||
--- | ||
navigation_title: "Node bootlooping" | ||
applies_to: | ||
deployment: | ||
ess: all | ||
Comment on lines
+4
to
+5
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same comment as before, this page should also have an ECE equivalent. |
||
ece: all | ||
mapped_pages: | ||
- https://www.elastic.co/guide/en/cloud/current/ec-config-change-errors.html | ||
- https://www.elastic.co/guide/en/cloud-enterprise/current/ece-config-change-errors.html | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The name of this tool is misleading, it doesn't have anything to do with our own Serverless offering. See https://www.elastic.co/guide/en/esf/current/aws-elastic-serverless-forwarder.html
This page should be under Troubleshooting > ingest tools. And
applies_to
should be stack: all and serverless: allThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't aware of that, thanks @florent-leborgne! cc @marciw
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@natasha-moore-elastic @florent-leborgne thank you both -- I can handle this in a separate PR