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: RE: Syndrome composition - interpreting an xquery signature in an editor


An xquery signature provided by BofA WILL work properly with CA’s diagnostician, and vica versa.  But, CA’s editor will not be able to parse/interpret the signature correctly.

Maybe that’s Ok?

 

Fyi – a generic XQuery editor isn’t going to help much.  It won’t understand that “3” is a frequency threshold and “30” is a time interval.

The xquery was simplified to get my point across.

 

From: Isaiadis, Stavros [mailto:stavros.isaiadis@baml.com]
Sent: Wednesday, May 25, 2011 4:42 AM
To: Vaught, Jeffrey A; saf@lists.oasis-open.org
Subject: RE: Syndrome composition - interpreting an xquery signature in an editor

 

Hi Jeff,

 

The editor thing is particularly difficult; the possibilities are infinite when it comes to conditions identified and relationships between the symptoms in a syndrome. The editor to XQuery path seems much easier, but for the reverse I think the editor should keep some other structure in place (as was proposed in the near past, was it Alvin or you?).

 

I think some Eclipse visual plugins are doing a similar think, they keep a “proprietary” file to “render” information in an editor, and from there they can export to standard formats –but the reverse is typically not possible without the original “proprietary” file as well.

 

We can also just rely on some existing XQuery editors which really make life easy but not to the point we would have liked.

 

Cheers,

 

Stavros

 

PS. By the way, I think the xquery below needs more complex algorithm to identify the condition you mentioned :-)

 

 

From: Vaught, Jeffrey A [mailto:Jeffrey.Vaught@ca.com]
Sent: 23 May 2011 15:05
To: saf@lists.oasis-open.org
Subject: [saf] Syndrome composition - interpreting an xquery signature in an editor

 

It was on my task list to provide an example where interpreting an XQuery with time & frequency elements would be very difficult (for an editor, for example).

 

Symptoms below.

We will be searching for 3 or more occurrences within 30 second interval of application/responsetime/threshold/breach where Subject is identical.

<?xml version="1.0" encoding="UTF-8"?>
<SymptomStore>
 
<Symptom>
   
<SymptomId>com/ca/symptom/1</SymptomId>
   
<SymptomType>application/responsetime/threshold/breach</SymptomType>
   
<CreationDate>2011-05-23T10:00:00</CreationDate>
   
<Confidence>ModerateConfidence</Confidence>
   
<Reporter>com/ca/application/apm</Reporter>
   
<Subject>APP1@server1.ca.com</Subject>
   
<Content></Content>
 
</Symptom>
 
<Symptom>
       
<SymptomId>com/ca/symptom/2</SymptomId>
       
<SymptomType>system/process/memory/threshold/breach</SymptomType>
       
<CreationDate>2011-05-23T10:01:00</CreationDate>
       
<Confidence>ModerateConfidence</Confidence>
       
<Reporter>com/ca/system/nsm</Reporter>
       
<Subject>APP1@server1.ca.com</Subject>
       
<Content></Content>
 
</Symptom>
 
<Symptom>
       
<SymptomId>com/ca/symptom/3</SymptomId>
       
<SymptomType>system/process/memory/threshold/breach</SymptomType>
       
<CreationDate>2011-05-23T10:02:00</CreationDate>
       
<Confidence>ModerateConfidence</Confidence>
       
<Reporter>com/ca/system/nsm</Reporter>
       
<Subject>APP2@server2.ca.com</Subject>
       
<Content></Content>
 
</Symptom>
   
<Symptom>
       
<SymptomId>com/ca/symptom/4</SymptomId>
       
<SymptomType>application/responsetime/threshold/breach</SymptomType>
       
<CreationDate>2011-05-23T10:00:15</CreationDate>
       
<Confidence>ModerateConfidence</Confidence>
       
<Reporter>com/ca/application/apm</Reporter>
       
<Subject>APP1@server1.ca.com</Subject>
       
<Content></Content>
   
</Symptom>
   
<Symptom>
       
<SymptomId>com/ca/symptom/5</SymptomId>
       
<SymptomType>application/responsetime/threshold/breach</SymptomType>
       
<CreationDate>2011-05-23T10:00:20</CreationDate>
       
<Confidence>ModerateConfidence</Confidence>
       
<Reporter>com/ca/application/apm</Reporter>
       
<Subject>APP1@server1.ca.com</Subject>
       
<Content></Content>
   
</Symptom>
</SymptomStore>

 

Here is one possible xquery.  Note: Some liberties were taken to keep simple.

let $s := doc('file:///c:/docs/_symptoms/symptomstore.xml')/SymptomStore/Symptom[SymptomType='application/responsetime/threshold/breach' and Subject='APP1@server1.ca.com']
let $freq := count($s)
return
 
if ($freq >= 3) then (
   
if ((fn:seconds-from-dateTime($s[$freq]/CreationDate) - fn:seconds-from-dateTime($s[1]/CreationDate)) <= 30) then (
     
$s
    )
   
else
    ()
  )
 
else
  ()
 
How is it possible to consistently extract the time interval (30) and the frequency (3) from such an xquery, for the purposes of rendering in an editor?

 

 

 

 


This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law.
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses.

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link:
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.



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