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

Improve messages for events and alerts #566

Open
julienlim opened this issue Feb 24, 2018 · 3 comments
Open

Improve messages for events and alerts #566

julienlim opened this issue Feb 24, 2018 · 3 comments
Assignees

Comments

@julienlim
Copy link
Member

julienlim commented Feb 24, 2018

Problem Description

  • Messages are too verbose and need to be actionable.
  • Alerts should clear when the issue is no longer present.
  • Alerts disrupt the user experience and should only be used in important and critical situations, e.g. host down, brick is running out of space, etc.

Recommendations

  • Unmanage and Import message should appear as an event (not an alert)
  • There should be a Import / Manage cluster event message when cluster is successfully imported. There is none today (in Tendrl 1.6.0)

Current Message:

Cluster 44f8f6f3-a103-437b-a3e1-701db25c5382 moved to un-managed state. The archived monitoring data available at: /usr/share/tendrl/graphite/archive/clusters/44f8f6f3-a103-437b-a3e1-701db25c5382_2018-02-22T19:30:26.102943

Recommendation for Message:

<cluster> unmanaged.  Archived monitoring data to: <node>:<path>

Current Message:

Node node3.localdomain is UP

Recommendation for Message:

<node>  in <cluster_name>  is up

Note: Assumes node is always in a cluster as unmanaged node would not be in a cluster (and not have alert and event messages)

Current Message:

Health status of cluster: gluster-195d43d86fd38ba5929e44529d1fa0b985f42f03946e0bb5ada6999805556674 changed from unhealthy to healthy

Recommendation for Message:

<cluster> is healthy

A more comprehensive list of recommendations can be found at Tendrl Log Messaging Recommendations.

@r0h4n @nthomas-redhat @shtripat @Tendrl/qe @jjkabrown1 @mcarrano

@r0h4n
Copy link
Contributor

r0h4n commented Mar 21, 2018

@GowthamShanmugam any updates?

@GowthamShanmugam
Copy link
Contributor

@r0h4n i am not started to fix this issue

@GowthamShanmugam
Copy link
Contributor

This issue is fixed, we can close this issue

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

3 participants