| Summary: | Allow to analyze on different properties - new symptom database format | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Valentina Popescu <popescu> |
| Component: | Hyades | Assignee: | Alex Nan <apnan> |
| Status: | CLOSED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 2000 | ||
| Whiteboard: | closed460 | ||
|
Description
Valentina Popescu
Alex, this is one of the AC line items that should be done for the Hyades 1.3 - end of March I am also sending you a note with a detailed description of the feature To better leverage the various existing correlation technology as a common technology building block and have a better understanding about the existing usage cases and history, it became obvious, that we need to build a set of base correlation pattern in the context of our MAPE loop in the area of M (base event filtering) and A (event collection , sequences patterns and thresholds). The reader might review these base patterns and comment how complete we are expressing event correlation rules to derive higher level situation descriptions. There are four documents which are somehow related... Document 1. Is a revised version of the Correlation Pattern Document Document 2. Is a first proposal of Language Specification for ACT. It supports the first document digging down into more details. There might be some inconsistencies between docu 1 and 2, but this is work in progress, and probably not relevant for a first discussion Document 3 describe the two architectural models of ACT in the usage of TEC and WBI/BAM Document 4 is a presentation for docu 1 and some further discussion about tooling etc.. Reading 1,2 and 4 gives an input for ACT of course open for discussions. Document 3 is recommended as model to be built for potential exploiters before we dig down and add requrirements for ACT. It actually helps define and distinguish what is event correlation and what is something domain specific (something else as a consumer ). Simply to avoid overloading ACT... *** This bug has been marked as a duplicate of 50761 *** house keeping As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open. |