Details
-
Type: extRequest
-
Status: Closed
-
Priority: Major
-
Resolution: Done
-
Fix Version/s: 2021
-
Component/s: FIWARE-TECH-HELP
-
Labels:None
-
Sender Email:
-
HD-Chapter:Data
-
HD-Enabler:CEP
Description
Hi Samuel,
Glad to hear you are using the CEP in your case study.
You can refer to the segmentation key value when you assign values to the
derived event attributes. The syntax is: context.<segmentation-key-name>.
So if your segmentation context name is idContext, then you can refer to
its value by context.idContext
It would be great if you could help us and post this question in
Stackoverflow. This way other users in the community could see it when
they are looking for answers on CEP.
If you agree to do so, please add the tags: fiware and cep and send me a
link to the question.
Thank you in advanced,
Tali
Tali Yatzkar Haham
Smart Decision Solutions
IBM Research - Haifa, Israel
tali@il.ibm.com 972-4-8296320
From: Samuel Moreira <genesis.samuel@gmail.com>
To: Tali Yatzkar-Haham/Haifa/IBM@IBMIL
Date: 05/01/2016 08:22 PM
Subject: Complex Event Processing (CEP)
Hi Tali,
I am having problems in creating a specific case study in cep, and i was
hopping that you could help me.
Context of my case study:
I have multiple devices that read temperatures and are constantly (e.g.
every minute) sending those temperature reports. What i am trying to do
is, send alarms(events) when the devices have low battery, when they get
temperatures out bounds, or if they don't report any activity for a while.
I was able to do almost everything that i describe above.
- Send event, when a device has low battery - Check;
- Send event, when a device detects temperatures out bounds - Check;
- Send event when a device don't report any activity in 60 min - having
problems;
So my problems with the last one, is that i don't know which was the
device that didn't report for a while. I created a EPA (absence type), and
it has a composite context. The temporal context it starts when receives a
temperature report and then waits 60 min for another temperature report.
And the segmentation context is the id of the device.
I assume that as this EPA is from the absence type, we don't have a way to
pass the device id, to the derivation event ( event with the device id
triggered when it doesn't report for 60 min ).
Is there any way to get this working?
Thanks.
Regards,
Samuel Moreira
Since January 1st, old domains won't be supported and messages sent to any domain different to @lists.fiware.org will be lost.
Please, send your messages using the new domain (Fiware-tech-help@lists.fiware.org) instead of the old one.
_______________________________________________
Fiware-tech-help mailing list
Fiware-tech-help@lists.fiware.org
https://lists.fiware.org/listinfo/fiware-tech-help
[Created via e-mail received from: Tali Yatzkar-Haham <TALI@il.ibm.com>]
Activity
- All
- Comments
- History
- Activity
- Transitions