简体   繁体   English

WSO2 BAM事件跟踪和关联

[英]WSO2 BAM event tracing and correlation

I'm interested in WSO2 Business Activity Monitor. 我对WSO2业务活动监视器感兴趣。 I read several documentations but I still wondering if WSO2 BAM can handle my following Business Activity Monitoring use case: 我阅读了一些文档,但是我仍然想知道WSO2 BAM是否可以处理以下业务活动监视用例:

Example

System A produces an event with a new transactionID "ORK78954". 系统A产生一个带有新transactionID“ ORK78954”的事件。

System B produces (1min later) another event the the same transactionID "ORK78954" 系统B产生(1分钟后)另一个事件,该事件具有相同的transactionID“ ORK78954”

System C doesn't produce an event with transactionID "ORK78954" in the next 5 minutes. 系统C在接下来的5分钟内不会产生带有transactionID为“ ORK78954”的事件。

Of course, I don't know which transactionsIDs are used. 当然,我不知道使用了哪些transactionID。 WSO2 has to use RegEx etc. on the transactionID field on the event. WSO2必须在事件的transactionID字段上使用RegEx等。 System A, B, C not inside WSO ESB, they "only" fire events into BAM. 系统A,B,C不在WSO ESB内部,它们“仅”将火灾事件导入BAM。

Can WSO2 alert me, that System A produced an event (with a transactionID "ORK78954") that never reached System C? WSO2可以提醒我系统A产生了从未到达系统C的事件(带有transactionID“ ORK78954”)吗?

When not out of the box, do you think it is possible to write an own CEP window for this purpose? 如果不是开箱即用,您是否可以为此目的编写自己的CEP窗口?

I got the following answer from WSO2: 我从WSO2得到以下答复:

This requirement can be supported by the WSO2 Complex Event Processor(CEP) or through the embedded CEP component of the WSO2 Business Activity Monitor (BAM). WSO2复杂事件处理器(CEP)或WSO2业务活动监视器(BAM)的嵌入式CEP组件均可支持此要求。 Each external system can publish the relevant event to a corresponding stream in WSO2 CEP or WSO2 BAM. 每个外部系统都可以将相关事件发布到WSO2 CEP或WSO2 BAM中的相应流。 Then using the Siddhi queries (The underlying sql like query language of the event engine) a time windows can be defined that match the allowed duration the message should reach the next system. 然后,使用Siddhi查询(事件引擎的基础sql之类的查询语言),可以定义一个时间窗口,该时间窗口与消息到达下一系统的允许持续时间匹配。 Then within the same window construct of the Siddhi query the expired events could be compared for a matching event in the second stream. 然后,在Siddhi查询的同一窗口构造中,可以比较过期事件以获取第二个流中的匹配事件。 If there is no matching event in the second stream then we could send it to another stream where we can configure an output event adapter to send the alert. 如果第二个流中没有匹配事件,那么我们可以将其发送到另一个流,在这里我们可以配置输出事件适配器来发送警报。 For more information please refer: http://eranga-wso2.blogspot.com/2015/02/wso2-complex-event-processor.html http://eranga-wso2.blogspot.com/2015/02/configuring-email-event-adapter-in-wso2.html 有关更多信息,请参阅: http : //eranga-wso2.blogspot.com/2015/02/wso2-complex-event-processor.html http://eranga-wso2.blogspot.com/2015/02/configuring-email -event-adapter-in-wso2.html

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM