Symptoms for Cloud Profile

["Vaught, Jeffrey A" <Jeffrey.Vaught@ca.com>]

Below is a list of possible Symptom types for Cloud management.

Two concerns were mentioned on the call today:

1.   Lack of taxonomy – Is there an existing taxonomy that could be used for the symptom type (and/or prescription type)?

2.   Symptom boundary – How do we decide what should be a symptom and what shouldn’t be a symptom?  For example, resource performance notifications (ie: cpu1 on server xyz is 39% utilized) doesn’t seem like a good candidate for a symptom.  Can we articulate a ‘rule’ for what should be a symptom?

 

Please offer your thoughts.

 

 

 

SymptomType	Description	Possible Content elements
urn:servicemanagement:quota-threshold	A quota for a resource has been breached, or is about to be breached.  Example: Provider emitted symptom triggers consumer syndrome/protocol to revise quota.	xs:anyURI – serviceid xs:int – remaining-quota-percent
urn:servicemanagement:planned-outage	A planned service outage is imminent.  Example: Provider emitted symptom triggers consumer syndrome/protocol to mitigate outage.	xs:anyURI – serviceid xs:int – expected-duration
urn:servicemanagement:unplanned-outage	A service is suddenly unavailable. Example: Provider emitted symptom triggers consumer syndrome/protocol to mitigate outage.	xs:anyURI – serviceid xs:int – expected-duration
urn:servicemanagement:cost-threshold	A service cost threshold has been breached, or is about to be breached. Example: Provider emitted symptom triggers consumer syndrome/protocol to reduce consumption or renegotiate service agreement.	xs:anyURI – serviceid xs:int – remaining-percent xs:boolean – is-above-threshold
urn:servicemanagement:sla-violation	An SLA violation has occurred or is about to occur. Example: Consumer emitted symptom triggers provider syndrome/protocol to notify/escalate service owner.	xs:anyURI – serviceid xs:string – violation-metric