Hi Alvin, all,
We were trying to clarify the incident id field yesterday and specifically find strong cases where a symptom could be part of multiple incidents. You have previously said:
The “symptom participating in multiple incidents” seems like it would come up very often. The most obvious scenario to me is for any broad symptom that could have multiple possible causes (which may actually be completely
separate incidents).
For example:
A “Service not available” symptom could belong to a symptom chain for multiple causes:
A) “Virus detected” symptom
B) “Network unavailable” symptom
C) “Server on fire” symptom
Or, if we want to use a more abstract example:
“I have a headache” symptom:
A) “Did not get any sleep last night” symptom
B) “Axe buried in my head” symptom
C) “I just read another one of Alvin’s emails” symptom
I can see the value in the above; do we assume the emitter will know and supply all these incident Ids? Cause then it will have to be a bit smarter than we have thought.
Is this a matter of merely having a collection of incident Ids? I assume it is, and I think right now that’s how it is in the spec.
Any more thoughts or comments on this one so that we can put it to rest?
Cheers,
Stavros