Skip to Content

Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00
From version 701.1
edited by Erik Bakker
on 2024/08/26 16:18
Change comment: There is no comment for this version
To version 792.1
edited by Carlijn Kokkeler
on 2024/11/18 12:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -228 - Monitoring Mania
1 +234 - Alert Adventures
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -3,107 +3,43 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** This release we have done many improvements to the monitoring graphs in Manage. Moreover, we have made some improvements to the missing properties and unused properties overviews and did several bug fixes. Find out all improvements & bug fixes below!
6 +**Hi there, eMagiz developers!** In this release, our new error alerting will be available! Please find out more about it here (LINK). Apart from this, .
7 7  
8 -== **Manage Graphs Improvements** ==
9 -
10 -//__Generic improvements__//
11 -
12 -* Pressing the 'show main dashboard' button returns back to the unfiltered master dashboard.
13 -* For detailed views the 'show main dashboard' button is on the left.
14 -* Graphs on a page share the same crosshair.
15 -
16 -[[image:Main.Images.Release Blog.WebHome@release-228-maindashboard.png]]
17 -
18 -
19 -//__Specific improvements__//
20 -
21 -* The following graphs now show the unit of measurement per time frame (i.e. bytes/2h)
22 -** Queue Statistics - Overview
23 -*** Message Througput
24 -** Event Streaming Statistics - Overview
25 -*** Bytes In
26 -*** Bytes Out
27 -*** Messages In
28 -
29 -[[image:Main.Images.Release Blog.WebHome@release-228-eventsteamingstats.png]]
30 -
31 -* The following graph now shows an improved unit of measurement
32 -** Runtime Statistics - Key Metrics
33 -*** Log events are counted as a sum instead of a maximum per data point.
34 -* The following data measurement graphs indicate whether the component was on or off when hovering over the data points.
35 -** Runtime Statistics - Other Metrics
36 -*** Data measurements
37 -** Queue Statistics - Other Metrics
38 -*** Data measurements
39 -
40 -
41 -* The Memory and CPU usage table in the Runtime statistics displays the maximum value in a given time period that is selected.
42 -
43 -* The styling on HTTP statistics when there are no (un)successful requests within a timeframe has been improved.
44 -* For selection dropdowns the selected variables are locked to the top for easy deselection.
45 -
46 -[[image:Main.Images.Release Blog.WebHome@release-228-runtime statistics.png]]
47 -
48 48  == **Feedback Items** ==
9 +//__Error alerting__//
10 +Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, following our queue alerting design that has been [[released>>doc:Main.Release Information.Release Blogs.226 - Alerting Alchemy.WebHome||target="blank"]] a couple of months ago. The new error alerting feature allows you to trigger an alert on all incoming errors, or choose to trigger when specific filters on the error’s headers, message or class have been met. Furthermore, you can select the specific runtime the error originated from as one of the filters as well.
49 49  
50 -//__Failover deployment plan__//
51 -The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.
12 +{{info}}Please take into consideration the following migration actions:
13 +* All existing error message alert triggers from the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture models will be automatically migrated to the new alerting feature.
14 +* All fields will be mapped directly to their corresponding new fields on a 1:1 basis, with one exception:
15 +** The 'Description' field has been replaced by the new 'Instructions' field (note: the 'Description' field no longer exists).
16 +** The values of the old description field will be transferred into the instructions field
17 +* Additionally, a new field, 'Name', has been introduced for identification purposes. The 'Name' field will be included in email notifications when a trigger is activated.
18 +** This field will be automatically populated with a default name (e.g., "Error Trigger 1").
19 +** **Users are advised to review and update these names to appropriately reflect each trigger's purpose**.
20 +* If an error message alert trigger has the following specific configuration, its trigger conditions will be migrated such that alerts are triggered for **all** incoming error messages:
21 +** "Check header" is disabled.
22 +** "Check error message" is enabled.
23 +** The "Error message contains" field includes only a single character.
24 +* The new feature introduces duplicate detection when saving an individual error trigger. This duplicate detection is not performed during the migration process. Please check your migrated error triggers to avoid receiving duplicate error alerts.{{/info}}
52 52  
53 -//__Edit mode flow testing__//
54 -Test messages can now be edited or removed while in the edit mode of the flow testing functionality.
26 +{{warning}}To keep a better overview, we recommend you to remove your old dynamic triggers after the new error triggers are activated, these have already been disabled by our migration process. The same applies for your queue-related triggers. These triggers can be found under the ‘Other’ tab on the alert triggers page.{{/warning}}
55 55  
56 -//__Missing properties overview__//
57 -Setting the value of a missing property will now automatically remove it from the missing properties overview. Besides that, search and sort functionality have been added to the missing properties overview.
58 -[[image:Main.Images.Release Blog.WebHome@release-228-missing-properties.png]]
28 +{{warning}}Please check out our LINK microlearning for an elaborate explanation of our new error alerting. {{/warning}}
59 59  
60 -//__Legacy release notes__//
61 -The legacy release notes tab has been removed.
62 -
63 -//__SSL helptext__//
64 -The SSL section in runtime settings has more elaborate helptext.
65 -
66 -[[image:Main.Images.Release Blog.WebHome@release-228-ssl-enabled.png]]
30 +//__Error alerting__//
31 +When selecting an attribute in a datamodel, the selected attribute and associated entity are now highlighted.
67 67  
68 -//__Memory warning__//
69 -A pop-up with a warning will be shown when containers are configured with less memory than recommended.
70 -
71 -[[image:Main.Images.Release Blog.WebHome@release-228-memory-settings.png]]
72 -
73 -//__Reuse test messages__//
74 -It is now possible to reuse the test messages created in other flows within the routing and vice versa.
75 -
76 -//__Unused properties__//
77 -We added logging for when properties are deleted from the unused properties screen.
78 -
79 -[[image:Main.Images.Release Blog.WebHome@release-228-unused-properties.png]]
33 +[[image:Main.Images.Release Blog.WebHome@release-234-cdm.png]]
80 80  
81 -//__Styling component__//
82 -The styling of the "File Item Reader Message Source" component configuration pop-up has been improved.
83 -
84 -//__Volume mappings helptext__//
85 -The helptext of volume mappings has been improved.
86 -
87 -[[image:Main.Images.Release Blog.WebHome@release-228-volume.png]]
88 -
89 89  == **Bug Fixes** ==
90 -//__Legacy properties__//
91 -We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production.
92 92  
93 -//__Exceeding memory__//
94 -We fixed a bug where new machines could be deployed with exceeding memory.
95 95  
96 -//__Copy paste__//
97 -The copy paste functionality in the flow designer does not change the configuration of existing flow components anymore.
98 -
99 99  == **Fancy Forum Answers** ==
100 100  
101 101  As always, this is a gentle reminder to ask questions via the Q&A forum. The Q&A forum is available in the eMagiz iPaaS portal, so we can all benefit from the knowledge within the community. For some inspiration, take a look at these forum answers:
102 102  
103 -* [[Character array is missing "e" notation exponential mark>>https://my.emagiz.com/p/question/172825635703914491||target="blank"]]
104 -* [[Error when creating XSD>>https://my.emagiz.com/p/question/172825635703914508||target="blank"]]
105 -* [[Warning log - "Invalid cookie header">>https://my.emagiz.com/p/question/172825635703927026||target="blank"]]
106 -* [[Param_path variable remains empty when including question mark>>https://my.emagiz.com/p/question/172825635703939749||target="blank"]]
42 +* [[JSON-TO-JSON java.lang.NumberFormatException in string field>>https://my.emagiz.com/p/question/172825635703991104||target="blank"]]
107 107  
108 108  == **Key Takeaways** ==
109 109  
... ... @@ -113,7 +113,7 @@
113 113  * If you have feedback or ideas for us, talk to the Platypus
114 114  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
115 115  * Clear your browser cache (Ctrl + Shift + Del)
116 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.228 - Monitoring Mania.WebHome||target="blank"]]
52 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.233 - Policy Polish.WebHome||target="blank"]]
117 117  * Start thinking about how the license tracker can aid your development
118 118  * Start thinking about major, minor, and patch
119 119  * Keep making great integrations