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.

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

[serverless] Update slugs/ids of alerting rule topics #3933

Open
30 tasks
colleenmcginnis opened this issue May 28, 2024 · 0 comments
Open
30 tasks

[serverless] Update slugs/ids of alerting rule topics #3933

colleenmcginnis opened this issue May 28, 2024 · 0 comments

Comments

@colleenmcginnis
Copy link
Contributor

Description

@lcawl suggested that we remove "alert" from the slugs and IDs for the alerting rule topics:

  • create-anomaly-alert-rule.mdx
    • slug
    • id
    • filename
  • create-custom-threshold-alert-rule.mdx
    • slug
    • id
    • filename
  • create-elasticsearch-query-alert-rule.mdx
    • filename
  • create-error-count-threshold-alert-rule.mdx
    • slug
    • id
    • filename
  • create-failed-transaction-rate-threshold-alert-rule.mdx
    • slug
    • id
    • filename
  • create-inventory-threshold-alert-rule.mdx
    • slug
    • id
    • filename
  • create-latency-threshold-alert-rule.mdx
    • slug
    • id
    • filename
  • create-slo-burn-rate-alert-rule.mdx
    • slug
    • id
    • filename

When we do this, we'll need to:

  • Update any topics that point to the old slug IDs.
  • Check the doclink service and update it was required.
  • Implement redirects.

cc @dedemorton

Resources

N/A

Which documentation set does this change impact?

Serverless only

Feature differences

N/A

What release is this request related to?

N/A

Collaboration model

The documentation team

Point of contact.

Main contact: @dedemorton @colleenmcginnis

Stakeholders: @lcawl @elastic/docs-engineering

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant