diff --git a/.github/workflows/comment-on-asciidoc-changes.yml b/.github/workflows/comment-on-asciidoc-changes.yml new file mode 100644 index 000000000..8e5f836b1 --- /dev/null +++ b/.github/workflows/comment-on-asciidoc-changes.yml @@ -0,0 +1,21 @@ +--- +name: Comment on PR for .asciidoc changes + +on: + # We need to use pull_request_target to be able to comment on PRs from forks + pull_request_target: + types: + - synchronize + - opened + - reopened + branches: + - main + - master + - "9.0" + +jobs: + comment-on-asciidoc-change: + permissions: + contents: read + pull-requests: write + uses: elastic/docs-builder/.github/workflows/comment-on-asciidoc-changes.yml@main diff --git a/cloud-account/multifactor-authentication.md b/cloud-account/multifactor-authentication.md index 25741b898..3f52bbdd4 100644 --- a/cloud-account/multifactor-authentication.md +++ b/cloud-account/multifactor-authentication.md @@ -58,7 +58,7 @@ To enable multifactor authentication using an authenticator app, you must verify You can remove a multifactor authentication method after it’s added by clicking **Remove**. -Before you remove an authentication method, you must set up an alternate method. If you can’t use any of your configured authentication methods — for example, if your device is lost or stolen — then [contact support](../troubleshoot/troubleshoot/cloud.md). +Before you remove an authentication method, you must set up an alternate method. If you can’t use any of your configured authentication methods — for example, if your device is lost or stolen — then [contact support](../troubleshoot/troubleshoot/index.md). ## Frequently asked questions [ec-account-security-mfa-faq] diff --git a/deploy-manage/cloud-organization/billing/billing-faq.md b/deploy-manage/cloud-organization/billing/billing-faq.md index a5171dff0..70210fb00 100644 --- a/deploy-manage/cloud-organization/billing/billing-faq.md +++ b/deploy-manage/cloud-organization/billing/billing-faq.md @@ -68,7 +68,7 @@ $$$faq-payment$$$What are the available payment methods on Elastic Cloud? : For month-to-month payments only credit cards are accepted. We also allow payments by bank transfer for annual subscriptions. $$$faq-contact$$$Who can I contact for more information? -: If you have any further questions about your credit card statement, billing, or receipts, send an email to `ar@elastic.co` or open a [Support case](../../../troubleshoot/troubleshoot/cloud.md) using the *Billing issue* category. +: If you have any further questions about your credit card statement, billing, or receipts, please send an email to `ar@elastic.co` or open a [Support case](../../../troubleshoot/troubleshoot/index.md) using the *Billing issue* category. $$$faq-charge$$$Why is my credit card charged? : If you are on a monthly plan, the charge is a recurring fee for using Elastic Cloud. The fee is normally charged at the start of each month, but it can also be charged at other times during the month. If a charge is unsuccessful, we will try to charge your card again at a later date. @@ -86,10 +86,10 @@ $$$faq-chargednotusing$$$Why am I being charged if I don’t use any of my deplo : Even if you have no activity on your account and you haven’t logged into the [Elastic Cloud Console](https://cloud.elastic.co?page=docs&placement=docs-body), your active deployments still incur costs that we need to charge you for. To avoid being charged for active but unused deployments, you can simply delete them. Your account will stay active with no charges, and you can always spin up more capacity when you need it. $$$faq-deleteaccount$$$How can I delete my Elastic Cloud account? -: To have your account removed, you can contact support through the Elastic Cloud [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) or use one of these [alternative contact methods](../../../troubleshoot/troubleshoot/cloud.md). For details about our data erasure policy, check [Privacy Rights and Choices](https://www.elastic.co/legal/privacy-statement#privacy-rights-and-choices?page=docs&placement=docs-body) in our General Privacy Statement. +: To have your account removed, you can contact support through the Elasticsearch Service [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) or use one of these [alternative contact methods](../../../troubleshoot/troubleshoot/index.md). For details about our data erasure policy, check [Privacy Rights and Choices](https://www.elastic.co/legal/privacy-statement#privacy-rights-and-choices?page=docs&placement=docs-body) in our General Privacy Statement. $$$faq-refund$$$Can I get a refund? -: Charges are non-refundable, but after you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, use the Elastic Cloud Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Getting help](../../../troubleshoot/troubleshoot/cloud.md). +: Charges are non-refundable, but once you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, please use the Elasticsearch Service Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Contact us](../../../troubleshoot/troubleshoot/index.md). $$$faq-included$$$What is included in my paid Elastic Cloud Hosted deployment? : All subscription tiers for Elastic Cloud Hosted include the following free allowance: diff --git a/raw-migrated-files/cloud/cloud/ec-about.md b/raw-migrated-files/cloud/cloud/ec-about.md index 51342ef8d..48821e47a 100644 --- a/raw-migrated-files/cloud/cloud/ec-about.md +++ b/raw-migrated-files/cloud/cloud/ec-about.md @@ -7,6 +7,6 @@ The information in this section covers: * [Elasticsearch Service Hardware](https://www.elastic.co/guide/en/cloud/current/ec-reference-hardware.html) * [Elasticsearch Service Regions](https://www.elastic.co/guide/en/cloud/current/ec-reference-regions.html) * [Service Status](../../../deploy-manage/cloud-organization/service-status.md) -* [Getting help](../../../troubleshoot/troubleshoot/cloud.md) +* [Getting help](../../../troubleshoot/troubleshoot/index.md) * [Restrictions and known problems](../../../deploy-manage/deploy/elastic-cloud/restrictions-known-problems.md) diff --git a/raw-migrated-files/cloud/cloud/ec-deployment-no-op.md b/raw-migrated-files/cloud/cloud/ec-deployment-no-op.md index 2dfea43a7..0c090e9f0 100644 --- a/raw-migrated-files/cloud/cloud/ec-deployment-no-op.md +++ b/raw-migrated-files/cloud/cloud/ec-deployment-no-op.md @@ -14,7 +14,7 @@ Re-saving the deployment configuration without making any changes is often all t **Seeing multiple warnings?** -If multiple health warnings appear for one of your deployments, or if your deployment is unhealthy, we recommend [Getting help](../../../troubleshoot/troubleshoot/cloud.md) through the Elastic Support Portal. +If multiple health warnings appear for one of your deployments, or if your deployment is unhealthy, we recommend [Getting help](../../../troubleshoot/troubleshoot/index.md) through the Elastic Support Portal. **Warning about system changes** diff --git a/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md b/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md index 8e6e61784..1a30da32e 100644 --- a/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md +++ b/raw-migrated-files/cloud/cloud/ec-faq-getting-started.md @@ -34,7 +34,7 @@ This frequently-asked-questions list helps you with common questions while you g : Scale your clusters both up and down from the user console, whenever you like. The resizing of the cluster is transparently done in the background, and highly available clusters are resized without any downtime. If you scale your cluster down, make sure that the downsized cluster can handle your {{es}} memory requirements. Read more about sizing and memory in [Sizing {{es}}](https://www.elastic.co/blog/found-sizing-elasticsearch). $$$faq-subscriptions$$$Do you offer support? - : Yes, all subscription levels for Elasticsearch Service include support, handled by email or through the Elastic Support Portal. Different subscription levels include different levels of support. For the Standard subscription level, there is no service-level agreement (SLA) on support response times. Gold and Platinum subscription levels include an SLA on response times to tickets and dedicated resources. To learn more, check [Getting Help](../../../troubleshoot/troubleshoot/cloud.md). + : Yes, all subscription levels for Elasticsearch Service include support, handled by email or through the Elastic Support Portal. Different subscription levels include different levels of support. For the Standard subscription level, there is no service-level agreement (SLA) on support response times. Gold and Platinum subscription levels include an SLA on response times to tickets and dedicated resources. To learn more, check [Getting Help](../../../troubleshoot/troubleshoot/index.md). $$$faq-where$$$Where is Elasticsearch Service hosted? : We host our {{es}} clusters on Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure. Check out which [regions we support](https://www.elastic.co/guide/en/cloud/current/ec-reference-regions.html) and what [hardware we use](https://www.elastic.co/guide/en/cloud/current/ec-reference-hardware.html). New data centers are added all the time. diff --git a/raw-migrated-files/cloud/cloud/ec-monitoring.md b/raw-migrated-files/cloud/cloud/ec-monitoring.md index 278689b8d..2e9d502d7 100644 --- a/raw-migrated-files/cloud/cloud/ec-monitoring.md +++ b/raw-migrated-files/cloud/cloud/ec-monitoring.md @@ -96,7 +96,7 @@ In a production environment, we highly recommend storing your logs and metrics i ## Dedicated logs and metrics [ec-es-health-dedicated] -In a production environment, it’s important set up dedicated health monitoring in order to retain the logs and metrics that can be used to troubleshoot any health issues in your deployments. In the event of that you need to [contact our support team](../../../troubleshoot/troubleshoot/cloud.md), they can use the retained data to help diagnose any problems that you may encounter. +In a production environment, it’s important set up dedicated health monitoring in order to retain the logs and metrics that can be used to troubleshoot any health issues in your deployments. In the event of that you need to [contact our support team](../../../troubleshoot/troubleshoot/index.md), they can use the retained data to help diagnose any problems that you may encounter. You have the option of sending logs and metrics to a separate, specialized monitoring deployment, which ensures that they’re available in the event of a deployment outage. The monitoring deployment also gives you access to Kibana’s stack monitoring features, through which you can view health and performance data for all of your deployment resources. diff --git a/raw-migrated-files/cloud/cloud/ec-scenario_why_are_shards_unavailable.md b/raw-migrated-files/cloud/cloud/ec-scenario_why_are_shards_unavailable.md index 79bc791da..5cd5ae589 100644 --- a/raw-migrated-files/cloud/cloud/ec-scenario_why_are_shards_unavailable.md +++ b/raw-migrated-files/cloud/cloud/ec-scenario_why_are_shards_unavailable.md @@ -22,7 +22,7 @@ If a cluster has unassigned shards, you might see an error message such as this :alt: Unhealthy deployment error message ::: -If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/troubleshoot/cloud.md). +If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/troubleshoot/index.md). ## Analyze unassigned shards using the {{es}} API [ec-analyze_shards_with-api] @@ -186,7 +186,7 @@ Here’s how to resolve the most common causes of unassigned shards reported by * [Maximum retry times exceeded](../../../troubleshoot/monitoring/unavailable-shards.md#ec-max-retry-exceeded) * [Max shard per node reached the limit](../../../troubleshoot/monitoring/unavailable-shards.md#ec-max-shard-per-node) -If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/troubleshoot/cloud.md). +If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/troubleshoot/index.md). ### Disk is full [ec-disk-full] diff --git a/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md b/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md index aed231d01..33b6861d9 100644 --- a/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md +++ b/raw-migrated-files/cloud/cloud/ec-scenario_why_is_my_node_unavailable.md @@ -23,7 +23,7 @@ Some actions described here, such as stopping indexing or Machine Learning jobs, For production deployments, we recommend setting up a dedicated monitoring cluster to collect metrics and logs, troubleshooting views, and cluster alerts. -If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/troubleshoot/cloud.md). +If your issue is not addressed here, then [contact Elastic support for help](../../../troubleshoot/troubleshoot/index.md). ## Full disk on single-node deployment [ec-single-node-deployment-disk-used] @@ -53,7 +53,7 @@ If your issue is not addressed here, then [contact Elastic support for help](../ * Increase the disk size on your Hot data and Content tier (scale up). ::::{note} -If your {{es}} cluster is unhealthy and reports a status of red, then increasing the disk size of your Hot data and Content tier may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then [reach out to Elastic support](../../../troubleshoot/troubleshoot/cloud.md) and we will assist you with scaling up. +If your {{es}} cluster is unhealthy and reports a status of red, then increasing the disk size of your Hot data and Content tier may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then [reach out to Elastic support](../../../troubleshoot/troubleshoot/index.md) and we will assist you with scaling up. :::: @@ -100,7 +100,7 @@ If your {{es}} cluster is unhealthy and reports a status of red, then increasing * Increase the disk size (scale up). ::::{note} -If your {{es}} cluster is unhealthy and reports a status of red, the scale up configuration change to increasing disk size on the affected data tiers may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then [reach out to Elastic support](../../../troubleshoot/troubleshoot/cloud.md) and we will assist you with scaling up. +If your {{es}} cluster is unhealthy and reports a status of red, the scale up configuration change to increasing disk size on the affected data tiers may fail. You might need to delete some data so the configuration can be edited. If you want to increase your disk size without deleting data, then [reach out to Elastic support](../../../troubleshoot/troubleshoot/index.md) and we will assist you with scaling up. :::: diff --git a/serverless/pages/search-your-data-semantic-search-elser.asciidoc b/serverless/pages/search-your-data-semantic-search-elser.asciidoc similarity index 89% rename from serverless/pages/search-your-data-semantic-search-elser.asciidoc rename to serverless/pages/search-your-data-semantic-search-elser.asciidoc index 02712bc16..f33b6b592 100644 --- a/serverless/pages/search-your-data-semantic-search-elser.asciidoc +++ b/serverless/pages/search-your-data-semantic-search-elser.asciidoc @@ -6,4 +6,4 @@ // This page is not included in the index file, so it is not visible in the navigation menu anymore. HTTP redirects will be set up. -ℹ️ Refer to <> for an overview of semantic search in {es-serverless}. \ No newline at end of file +ℹ️ Refer to <> for an overview of semantic search in {es-serverless}. diff --git a/troubleshoot/toc.yml b/troubleshoot/toc.yml index ef0416e76..4126cdb56 100644 --- a/troubleshoot/toc.yml +++ b/troubleshoot/toc.yml @@ -1,7 +1,6 @@ project: 'Troubleshoot' toc: - file: troubleshoot/index.md - - file: troubleshoot/cloud.md - file: elasticsearch/elasticsearch-reference.md children: - file: elasticsearch/fix-common-cluster-issues.md diff --git a/troubleshoot/troubleshoot/cloud.md b/troubleshoot/troubleshoot/cloud.md deleted file mode 100644 index 8356fd26c..000000000 --- a/troubleshoot/troubleshoot/cloud.md +++ /dev/null @@ -1,65 +0,0 @@ ---- -mapped_pages: - - https://www.elastic.co/guide/en/cloud/current/ec-get-help.html ---- - -# Troubleshoot [ec-get-help] - -With your Elasticsearch Service subscription, you get access to support from the creators of Elasticsearch, Kibana, Beats, Logstash, and much more. We’re here to help! - - -## How do I open a support case? [ec_how_do_i_open_a_support_case] - -All roads lead to the Elastic Support Portal, where you can access to all your cases, subscriptions, and licenses. - -As an Elasticsearch Service customer, you will receive an email with instructions how to log in to the Support Portal, where you can track both current and archived cases. If you are a new customer who just signed up for Elasticsearch Service, it can take a few hours for your Support Portal access to be set up. If you have questions, reach out to us at `support@elastic.co`. - -::::{note} -With the release of the new Support Portal, even if you have an existing account, you might be prompted to update your password. -:::: - - -There are three ways you can get to the portal: - -* Go directly to the Support Portal: [http://support.elastic.co](http://support.elastic.co) -* From the Elasticsearch Service Console: Go to the [Support page](https://cloud.elastic.co/support?page=docs&placement=docs-body) or select the support icon, that looks like a life preserver, on any page in the console. -* Contact us by email: `support@elastic.co` - - If you contact us by email, please use the email address that you registered with, so that we can help you more quickly. If you are using a distribution list as your registered email, you can also register a second email address with us. Just open a case to let us know the name and email address you would like to be added. - - -When opening a case, there are a few things you can do to get help faster: - -* Include the deployment ID that you want help with, especially if you have several deployments. The deployment ID can be found on the overview page for your cluster in the [Elasticsearch Service Console](https://cloud.elastic.co?page=docs&placement=docs-body). -* Describe the problem. Include any relevant details, including error messages you encountered, dates and times when the problem occurred, or anything else you think might be helpful. -* Upload any pertinent files. - - -## What level of support can I expect? [ec_what_level_of_support_can_i_expect] - -Support is governed by the [Elasticsearch Service Standard Terms of Service](https://www.elastic.co/legal/terms-of-service/cloud). The level of support you can expect to receive applies to your Elasticsearch Service environment only and depends on your subscription level: - -Elasticsearch Service Standard subscriptions -: Support is provided by email or through the Elastic Support Portal. The main focus of support is to ensure your Elasticsearch Service deployment shows a green status and is available. There is no guaranteed initial or ongoing response time, but we do strive to engage on every issue within three business days. We do not offer weekend coverage, so we respond Monday through Friday only. To learn more, check [Working with Elastic Support Elasticsearch Service Standard](https://www.elastic.co/support/welcome/cloud). - -Elasticsearch Service Gold and Platinum subscriptions -: Support is handled by email or through the Elastic Support Portal. Provides guaranteed response times for support issues, better support coverage hours, and support contacts at Elastic. Also includes support for how-to and development questions. The exact support coverage depends on whether you are a Gold or Platinum customer. To learn more, check [Elasticsearch Service Premium Support Services Policy](https://www.elastic.co/legal/support_policy/cloud_premium). - -::::{note} -If you are in free trial, you are also eligible to get the Elasticsearch Service Standard level support for as long as the trial is active. -:::: - - -If you are on an Elasticsearch Service Standard subscription and you are interested in moving to Gold or Platinum support, please [contact us](https://www.elastic.co/cloud/contact). We also recommend that you read our best practices guide for getting the most out of your support experience: [https://www.elastic.co/support/welcome](https://www.elastic.co/support/welcome). - - -## Join the community forums [ec_join_the_community_forums] - -Elasticsearch, Logstash, and Kibana enjoy the benefit of having vibrant and helpful communities. You have our assurance of high-quality support and single source of truth as an Elasticsearch Service customer, but the Elastic community can also be a useful resource for you whenever you need it. - -::::{tip} -As of May 1, 2017, support for Elasticsearch Service **Standard** customers has moved from the Discuss forum to our link: [Elastic Support Portal](https://support.elastic.co). You should receive login instructions by email. We will also monitor the forum and help you get into the Support Portal, in case you’re unsure where to go. -:::: - - -If you have any technical questions that are not for our Support team, hop on our [Elastic community forums](https://discuss.elastic.co/) and get answers from the experts in the community, including people from Elastic. diff --git a/troubleshoot/troubleshoot/index.md b/troubleshoot/troubleshoot/index.md index a98cd75f0..f6b810de7 100644 --- a/troubleshoot/troubleshoot/index.md +++ b/troubleshoot/troubleshoot/index.md @@ -2,6 +2,7 @@ mapped_urls: - https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/get-support-help.html - https://www.elastic.co/guide/en/starting-with-the-elasticsearch-platform-and-its-solutions/current/troubleshooting-and-faqs.html + - https://www.elastic.co/guide/en/cloud/current/ec-get-help.html --- # Troubleshoot @@ -13,4 +14,13 @@ mapped_urls: % Use migrated content from existing pages that map to this page: % - [ ] ./raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/get-support-help.md -% - [ ] ./raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md \ No newline at end of file +% - [ ] ./raw-migrated-files/tech-content/starting-with-the-elasticsearch-platform-and-its-solutions/troubleshooting-and-faqs.md +% - next one added by marciw manually for tracking +% - [ ] ./raw-migrated-files/cloud/cloud/ec-get-help.md (especially IDs -- no generated list because page was incorrectly mapped to a new v3 page instead of as a many-to-one for this page) + +% WIP sections added by marciw +% see https://docs.elastic.dev/content-architecture/content-type/troubleshooting/entrypoint +% ## one for each grouping +% ## Additional resources [troubleshoot-additional-resources] +% ## Contact us [troubleshoot-contact-us] +% ### Working with support \ No newline at end of file