Skip to content

UAS Portal Sharing Meeting Minutes

Meeting Info

Date 2022-09-08
Topic Discussion about UAS Portal
Host Scarlett Zhang
Attendee Monitoring & Status China Team
Note Taker Wendy Fu
Duration 3 hours and a half

Meeting Minutes

Alert Page - Notification level

Bug Fix

  • Search bar bug -- can not match notification according to "Service".

Enhancement

  • Only two columns have icons, a little strange.
  • Is column "Name" really necessary?
  • Notification id is too long and makes no sense.

Alert Page - Pools/Clusters level

Bug Fix

  • Aggregation have some bugs.

pool_level host_level

Dependence on EMS/MCT

  • Get event close status from EMS to judge whether alert is recovered.

Significant Enhancement

  • Pool level is too simple, no more message for customers.
    • analysis info repeat with teams message
    • no fail rate
    • add some summary
  • Add a page which focus on one pool, show customers more information and longer time, such as how many notifications happened, when they recover and so on.

Enhancement

  • Pools' name should align with the line no matter how long the name is.
  • It's difficult to operate follow tips, the show time should be longer.
    pool_tip
  • Chart legend should be placed on top and displayed horizon.
    legend_display
  • Let the arrow replace the follow checkbox will be better.
    checkbox
  • This time component cause confusion.
    time_component
  • Prod: change link direction to the same link. (have jira task)
    change_link
  • Icon have no use.
    icon
  • Notification Details: Handle (make no sense to customers) --> notification type & teams --> Webex Teams
  • How to implement the maintained info display?
    1. point implement
    maintain_point
    2. line implement
    maintain_line
  • Change line have the same color with EMS maintain line.
    recommend style
    change_line
  • Is Time Zone in Notification Details necessary?
  • Notification Details show the useless message, such as message id and time.
  • Status -- timeout is not good.
  • Sometimes one host one check make confusion.
  • Short alert is difficult to focus on. (time range adjust can fix this problem)

Tag escalation rule Page

Dependence on EMS/MCT

  • How to realize change tags (from MCT) in UAS portal? Some suggestions
    • authorization
    • record the user who makes the change
    • get relation hosts number from, MCT to reminder user

Enhancement

  • "Attributes" show in a different way.
  • Using green rectangles too much, makes confusion.
  • Delete tag combinations. tag_combinations
  • Add some blocks on rule detail page, to distinguish different function.
  • Change the position of deleting & add button.

Tag Match rue Page

Bug Fix

  • When this page closes, we should clear the cache.

rule_test

Significant Enhancement

  • Create attributes based on host.
  • Create attribute in current page by dropdown (editable, filterable, searchable) rather than dialog. The selected attribute can be seen in the page. After selecting, show verify button. New dialog show attributes, this page can also add new attributes. reference: ServiceNow, MCT(Subscribe)

Enhancement

  • Delete check box "all" on "Add GraphQL Attribute -- service name".
  • Change NA to "/".
  • Show service name according to user role.
  • Show recommended attributes(come from client not system level) when adding customized attributes.
  • "Conditions" change to label and can not be edited.
  • Change the name of "tag match rule" & "tag escalation rule"(delete tag).
  • Change "Tag escalation" name to "escalation(rule)".
  • When no tag escalation match, use modal to implement add new escalation rule.
  • Add star on required info.
  • "Tag escalation" better to show by table rather than dropdown.