Skip to Content

Changes for page Send Mail

Last modified by Erik Bakker on 2023/09/29 08:51
From version 15.1
edited by Erik Bakker
on 2023/08/23 15:00
Change comment: There is no comment for this version
To version 16.1
edited by Erik Bakker
on 2023/09/11 13:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SpEL Expressions
1 +Monitor partition size and consumer lag
Content
... ... @@ -1,5 +1,5 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -This exercise will provide you with practical guidance on the use of SpEL expressions within the eMagiz platform.
2 +This exercise will provide you with practical guidance on the interpretation of the event streaming statistics overview and specifically around partition size and consumer lag.
3 3  
4 4  Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
... ... @@ -6,19 +6,18 @@
6 6  == 1. Prerequisites ==
7 7  
8 8  * Completed previous exercises and microlearnings
9 -* Access to an eMagiz model
9 +* Access to an eMagiz model with an Event Streaming license
10 +* At least one configured topic on which something produces data and some other thing consumes data
10 10  
11 11  == 2. Exercise ==
12 12  
13 -Import the following store elements related to SpEL expressions in a flow and determine what they intend to achieve within the flow.
14 +Navigate to Manage -> Monitoring -> Event Streaming Statistics for the model you have selected to execute this exercise with. In here analyze the partition size and consumer lag that you see on at least one topic.
14 14  
15 -* [[Contains>>doc:Main.eMagiz Store.Accelerators.Contains - SpEL.WebHome||target="blank"]]
16 -* [[Current Date Time>>doc:Main.eMagiz Store.Accelerators.Current DateTime - SpEL.WebHome||target="blank"]]
17 -* [[Elvis Operator>>doc:Main.eMagiz Store.Accelerators.Elvis Operator - SpEL.WebHome||target="blank"]]
16 +{{info}}Given that the implementation of the prerequisites can differ the results of what you see can also differ. In our case we use example data that is part of our Sales Demo model to feed the Vehicle Event topic. An event processor determines subsequently based on the type of event whether a vehicle alert needs to be generated. This accounts for the difference in partition size between both topics. The event processor itself is shown as a consumer group and we can conclude that due to the high volume of messages placed on the Vehicle Event topic we see that a consumer lag is reported.{{/info}}
18 18  
19 19  == 3. Solution ==
20 20  In this short movie, you will find the workout of this exercise. Take a moment to review this one and compare it to your solution.
21 21  
22 -{{video attachment="advanced-data-handling-spel-expressions.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
21 +{{video attachment="advanced-monitoring-eventstreaming-partition-size-and-consumer-lag-exercise.mp4" reference="Main.Videos.Microlearning.WebHome"/}}
23 23  
24 24  )))((({{toc/}}))){{/container}}{{/container}}