different color/notification icons about xenadmin

[kc284]

This number is the total number for all things requiring the user's attention and/or further action, not just alerts, but also failed events and updates. If all is ok, it's not deemed necessary to distract the user, hence successful events are not included in the count. The red colour was chosen in order to make it more visible. If you want to use different colours, you'll need to decide how the various types of notifications weigh against each other and it's still likely to convey the user the wrong impression.

[fraggan]

I get notification at the bottom regardless of priority of the message. Even when the snapshot has finished I get the red circle. It would have been nice of the color was green in that case, or not showing at all. Hence my post here. So 3 different collors/circles and the options to chose in options to only show red, yellow or green maybe can be a solution? I do wanna know if the backup/snapshot finished successfully or not.

[kc284]

If you got a red circle it means something has gone wrong; successful events do not cause the red circle to appear. Have you checked the Notifications > Events window to see what happened?
By the way, the behaviour I am describing is for the current repo, i.e. Citrix XenCenter; I can't account for any modifications XCP-ng Center may have made.

[fraggan]

I got the red circle even with something that went ok, like the snapshot, below. I'm using xen-center in windows 7 from the latest xcp-ng release 7.5

[kc284]

Aaahh, that's not a successful event, that's an alert of "Minor" severity. At the moment alerts are always shown regardless of their severity.
I'd say the issue here is not the colour of the red circle but (a) whether this particular one should be "Information" rather than "Minor" and (b) whether the red circle should appear for "Information" alerts.

[kc284]

As mentioned above, alerts are always shown regardless of their severity and at the moment we're not planning to change this, hence I'm closing this issue.