Skip to content

[Internal]: ECH - Plan for production page is not redirected correctly #2980

@kunisen

Description

@kunisen

Description

https://www.elastic.co/guide/en/cloud/current/ec-planning.html is supposed to be redirected to https://www.elastic.co/docs/deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning per below

 docs-content git:(main) ag "https://www.elastic.co/guide/en/cloud/current/ec-planning"                                             
deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md
3:  - https://www.elastic.co/guide/en/cloud/current/ec-planning.html

➜  docs-content git:(main) cat deploy-manage/deploy/elastic-cloud/elastic-cloud-hosted-planning.md | head
---
mapped_pages:
  - https://www.elastic.co/guide/en/cloud/current/ec-planning.html
applies_to:
  deployment:
    ess: ga
products:
  - id: cloud-hosted
---

But when clicking thru, it's redirected to https://www.elastic.co/docs/deploy-manage/production-guidance/elasticsearch-in-production-environments.

Why it matters?

Two reasons

  • A) It's a doc redirection bug.
  • B) It causes impact more than a redirection bug.

:: Details about A) - redirection bug

Also, it's linked in cloud.elastic.co. where this wrong redirection will cause confusion to customers and users.

Image

:: Details about B) - more than redirection bug

Due to this redirection bug, users are not able to get to the correct ECH - Plan for production page, where they will lose the ability to understand how to plan for High Availability for their production environment on cloud. (Only ES is not enough, so we have had a dedicated cloud page). And correspondingly, they will get into trouble if they don't configure HA, (we have essential system maintenance all the time and w/o HA, they will experience service outage and data loss), and they will lose trust to Elastic.

Resources

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

n/a

What release is this request related to?

N/A

Serverless release

n/a

Collaboration model

The documentation team

Point of contact.

Main contact: @kunisen

Stakeholders:

Metadata

Metadata

Assignees

Labels

Team:AdminIssues owned by the Admin Docs TeamdocumentationImprovements or additions to documentationsupportabilityability enable self-service or support of product

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions