Normalized Notification Mechanism

XMLWordPrintable

    • Type: Task
    • Resolution: No Action
    • Priority: Major
    • None
    • Hide

      Two proposals:
      MikeB - As part of a SAF "profile", ie: Cloud Computing profile, define a specific payload such as WEF, CBE, or our own. Will also need to define the transport, ie: WS-Eventing, WSDM, as part of the profile.

      Jeff - Symptoms delivery would seem to be out-of-scope for the normative spec. We aren't limiting symptoms content to a particular event format (WEF, etc). Not to say we couldn't include examples in a primer. Recommend closing.

      Show
      Two proposals: MikeB - As part of a SAF "profile", ie: Cloud Computing profile, define a specific payload such as WEF, CBE, or our own. Will also need to define the transport, ie: WS-Eventing, WSDM, as part of the profile. Jeff - Symptoms delivery would seem to be out-of-scope for the normative spec. We aren't limiting symptoms content to a particular event format (WEF, etc). Not to say we couldn't include examples in a primer. Recommend closing.
    • Hide

      Stavros, Vivian, Dave, Alvin, Jeff consented to closing this issue. Out of scope for our current Spec.

      Show
      Stavros, Vivian, Dave, Alvin, Jeff consented to closing this issue. Out of scope for our current Spec.

      When we are ready to do symptom delivery mechanisms. The options are: Eventing, WEF, SNMP, our own, ...
      Which published event format includes the best information for Symptoms open content?

            Assignee:
            Unassigned
            Reporter:
            Jeffrey Vaught (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: