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

New concise, consistent alert reason messages #1478

Closed
vinaychandrasekhar opened this issue Jan 20, 2022 · 2 comments · Fixed by #1723
Closed

New concise, consistent alert reason messages #1478

vinaychandrasekhar opened this issue Jan 20, 2022 · 2 comments · Fixed by #1723
Assignees
Labels
Team:Docs Label for the Observability docs team v8.1.0

Comments

@vinaychandrasekhar
Copy link

vinaychandrasekhar commented Jan 20, 2022

Description

improvements to and standardization of alert reason messages across Observability. The messages are now limited in length while conveying the same bits of important information. Documentation update needs might be minor. Please ensure any screenshots that show the older messages are replaced with newer screenshots.

"Master" GH ticket is here.

Collaboration

  • The product team will provide the initial content and the docs team will edit / review

Contact Person:
@fkanout

Suggested Target Release

8.1

Stakeholders

@vinaychandrasekhar
@emma-raffenne
@jasonrhodes

@vinaychandrasekhar vinaychandrasekhar added the Team:Docs Label for the Observability docs team label Jan 20, 2022
@colleenmcginnis
Copy link
Contributor

@vinaychandrasekhar I couldn't find any references to specific alert messages in the Alerting docs except for the screenshot that is already being updated in #1723.

Are there other references I'm missing that you'd expect to be updated?

@vinaychandrasekhar
Copy link
Author

None that I can recollect @colleenmcginnis

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Docs Label for the Observability docs team v8.1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants