XMLWordPrintable

    • Market Problem
    • 80% To Do, 0% In Progress, 20% Done
    • False
    • Hide

      None

      Show
      None
    • subs-cost

      In the context of the app eventing rock, let's start sending some basic notifications:

       

      Prio Notification
      1 Splunk/ServiceNow/e-mail: cluster has no cost model*
      1 Splunk/ServiceNow/e-mail: Cost Management operator not sending data (“data is stale”)*
      2 Splunk: Cost model added/removed/assigned
      3 Splunk: data from CostM operator received
      3 Splunk: data from CostM operator processed

       

      • A spike on data aggregation will be needed to determine the capabilities of the eventing service. E. g. sending this over Splunk requires no aggregation (send as many times as needed, per cluster); sending over e-mail probably a 1-day aggregation of all the clusters

      Does the notification service support aggregation or should we aggregate on our end?

      Mock: https://marvelapp.com/prototype/23a3c1a6/screen/70998385

      Docs: https://core-platform-apps.pages.redhat.com/notifications-docs/dev/index.html

       

      Goals

      As an admin, I want to be able to set up events and send a message to the customer (i.e. via email), when the event is triggered

      Problem:

      In order to control costs proactively, the user needs to know that a budget has been surpassed, or that there is a change in the account that is significant (i.e. that there are new VM that can be optimized, or that there is something strange happening in the account that needs attention).

      Make the user aware of what is going on in relationship to budgets:

      • Notify the customer if the forecast goes over the budget (or a percentage of it)
      • Notify the customer if the actual costs goes over the budget
      • Notify the customer if the forecast or actual costs goes way below the budget (i.e. Only 20% after 50% of the month)

      Optimization opportunities should also be notified

      • Notify the customer when RI are going to finish
      • Notify the customer if there is a new reservation opportunity

      Making sure that the account is safe and healthy:

      • Notify the customer when there is an unexpected change in the services used
      • Notify the customer if the usage patterns vary (i.e. suddenly the use of networking increases 5x)

      Notify changes in the landscape

      • Notify the customer if AWS releases a new service

      Why is this important?:

      This moves our tool from an analysis tool to a management tool, as the operator can use our tool to understand that there is some action needed.

      Examples

      • As an admin, I can set up a message to be sent via email or any other means to the user when the costs or forecasts go over the budget.
      • As a user, I receive the notifications (via email or any other means) when the event is generated, with the information that allows me to know what had happened and a link to the page where the information is visible.
      • As a user, I receive the notifications in as many channels as possible being able to select which ones I prefer
        • Email at a minimum
        • Options for SMS, Slack, SNS
          **

              Unassigned Unassigned
              pgarciaq@redhat.com Pau Garcia Quiles
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: