Changes for page 240 - Spring Cleaning

Last modified by Erik Bakker on 2025/03/10 10:00

From version 725.1
edited by Carlijn Kokkeler
on 2024/09/27 09:35
Change comment: There is no comment for this version
To version 679.2
edited by Carlijn Kokkeler
on 2024/08/26 12:36
Change comment: Update document after refactoring.

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -230 - Petite Peaks
1 +228 - Monitoring Mania
Content
... ... @@ -3,33 +3,39 @@
3 3  (((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!** In this release, we have some small improvements and bug fixes. First of all, the pop-up when adding an integration to an existing API in Design has been improved. Secondly, queues with illegal characters will not cause errors anymore. Thirdly, an issue has been fixed where a deployment step would get blocked. Please find out all below!
6 +**Hi there, eMagiz developers!** This release
7 7  
8 -{{info}}Please note that during this deployment, Kafka metrics will be unavailable and lost for the duration of the deployment. After the deployment is complete, Kafka metrics will resume and be reflected in the monitoring graphs, but no metrics will be present corresponding to the deployment period.{{/info}}
9 -
10 10  == **Feedback Items** ==
11 -//__Add integration__//
12 -When adding an integration to an existing API in Design, the pop-up now shows that a new integration is being added, instead of an existing integration being edited.
9 +//__Grafana improvements__//
10 +* The throughput now shows the unit of measurement in the Queue statistics.
11 +* The units of measurement have been improved in the following graphs:
12 +** Runtime detail: Log events are counted as a sum instead of a maximum per data point. Data measurements show if a runtime is on or off.
13 +** Queue detail: Data measurements show if a queue is on or off.
14 +** Event streaming: The Bytes in and out are not a rate per seconds but dynamic based on the time frame selected. The messages in are counted not based on per second but also dynamic based on the time frame selected.
13 13  
14 -[[image:Main.Images.Release Blog.WebHome@release-230-add-integration.png]]
16 +[[image:Main.Images.Release Blog.WebHome@release-228-eventsteamingstats.png]]
15 15  
16 -//__Failover__//
17 -We have introduced a new failover feature, allowing you to enable failover on messaging flows with minimal setup required. Including in this feature is a new deployment plan step to automatically balance all of your failover connectors based on your configuration. The old failover deployment step has been deprecated and replaced by the aforemention new deployment plan step. Please find out more [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]].
18 -
19 -== **Bug Fixes** ==
20 -//__Queues with illegal characters__//
21 -Existing queues with illegal characters will not generate errors anymore. They can now be searched, deleted, explored, wiretapped, etc. in Manage -> Explore.
18 +* The Memory and CPU usage table in the Runtime statistics displays the maximum value in a given time period that is selected.
19 +* Pressing the 'show main dashboard' button returns back to the unfiltered master dashboard.
20 +* For detailed views the 'show main dashboard' button is on the left.
21 +* Graphs on a page share the same crosshair.
22 +* The styling on HTTP statistics when there are no (un)successful requests within a timeframe has been improved.
23 +* For selection dropdowns the selected variables are locked to the top for easy deselection.
22 22  
23 -//__Blocked deployment step__//
24 -We fixed an issue that blocked executing a deployment step in some occasions when an earlier step was not succeeded on time.
25 +[[image:Main.Images.Release Blog.WebHome@release-228-runtime statistics.png]]
26 +[[image:Main.Images.Release Blog.WebHome@release-228-maindashboard.png]]
25 25  
28 +
29 +== **Bug Fixes** ==
30 +//__Legacy properties__//
31 +We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production.
32 +
26 26  == **Fancy Forum Answers** ==
27 27  
28 28  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:
29 29  
30 -* [[Error being stamped on the wrong "last flow">>https://my.emagiz.com/p/question/172825635703952578||target="blank"]]
31 -* [[AMQP broker hostname for JMS-host instead of IP>>https://my.emagiz.com/p/question/172825635703965465||target="blank"]]
32 -* [[Calling a soap webservice that is secured with a client certificate>>https://my.emagiz.com/p/question/172825635703965402||target="blank"]]
37 +* [[Messages are not being delivered correctly to the SFTP location>>https://my.emagiz.com/p/question/172825635703914167||target="blank"]]
38 +* [[Uploading XSD>>https://my.emagiz.com/p/question/172825635703914284||target="blank"]]
33 33  
34 34  == **Key Takeaways** ==
35 35  
... ... @@ -39,7 +39,7 @@
39 39  * If you have feedback or ideas for us, talk to the Platypus
40 40  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
41 41  * Clear your browser cache (Ctrl + Shift + Del)
42 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.230 - Petite Peaks.WebHome||target="blank"]]
48 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.227 - Fix Frenzy.WebHome||target="blank"]]
43 43  * Start thinking about how the license tracker can aid your development
44 44  * Start thinking about major, minor, and patch
45 45  * Keep making great integrations