OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

saf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (SAF-11) Symptom Grouping/Linking



    [ http://tools.oasis-open.org/issues/browse/SAF-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24844#action_24844 ] 

Stavros Isaiadis  commented on SAF-11:
--------------------------------------

We were discussing about related symptoms, incident id, and case reference. I personally like this triple as each one seems to handle different needs:

- RelatedSymptoms provide means to refer to other symptoms using metadata to denote the kind of relationship, e.g. supersedes, causality, repetition etc. This would be set by the emitter
- IncidentID, is a rudimentary form of relating symptoms based on the emitter's understanding, e.g. emitting symptoms that are all related to a server down incident.
- CaseID, is a more comprehensive grouping of symptoms based on the diagnosticians' (and other experts') more complete understanding and holistic picture. As such, a case is not the same as an incident, and it can be used to link to external case management systems.

The first two seem to be straightforward, both in their functionality and in the consensus within the group

> Symptom Grouping/Linking
> ------------------------
>
>                 Key: SAF-11
>                 URL: http://tools.oasis-open.org/issues/browse/SAF-11
>             Project: OASIS Symptoms Automation Framework (SAF) TC
>          Issue Type: Task
>            Reporter: Jeffrey Vaught
>            Assignee: Alvin Black
>            Priority: Critical
>
> In the pre standards phase of this work, it was suggested that some form of "Group Id" or "Linking Tag" be included at the top level of the Symptom to indicate that this Symptom was in someway related to other Symptoms and that this relationship was identifiable by the creator of the Symptom.
> Notes
> •	Jeff: Could capture in the signature, but emitter is uniquely positioned to provide.
> •	Alvin: On/Off (state).  Alarmid.
> •	Vivian: Prototypes show this is important for performance.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]