Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 148.1
edited by Carlijn Kokkeler
on 2023/10/24 12:33
Change comment: There is no comment for this version
To version 282.1
edited by Carlijn Kokkeler
on 2024/07/29 13:59
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +226 - Alerting Alchemy
Content
... ... @@ -1,33 +1,12 @@
1 -In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components and we did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
1 +During our recent sprint cycle, we have worked to release ..
2 2  
3 -Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]].
4 4  
5 -=====Minor changes=====
6 -
7 -* Design - Message Mapping: The button 'Import from Store' will directly open the store.
8 -* Create - Flow Designer: Performance improvements for the Flow Designer have been implemented.
9 -* Create - Flow Designer: When importing items from the store, flow fragments that are hidden in Design will be listed under the versions in Create. (#1044)
10 -* Create - Flow Designer: Resources without names won't trigger error messages when users select components. (#950)
11 -* Create - Flow Designer: We added a migration step, such that the error channel is set to “errorChannel” of all inbounds in a flow if the custom error handling is set to false.
12 -* Create - Flow Designer: The performance of highlighting resources of selected components is improved in Read-only mode.
13 -* Deploy - Releases: When release is removed, the related unused images in the on-premises machines will be removed as well.
14 -* Deploy - Release Properties: Special characters such as a backslash do not break properties after deployment. (#1028)
15 -* Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. (#1045)
16 -* Manage - Monitoring: Extended user session times for 3rd generation runtime dashboards.
17 -* Manage - Triggers: When creating a new trigger the order of the cancel and next buttons has been switched.
18 -* Manage - Data Sink: The data sink page has been moved to the “Explore” tab. (#946)
19 -* Manage - Alerting: For gen3 models, you will no longer receive alert messages for every error message, every log message of 'level' ERROR, and for memory usage above 80%. For gen3 models with event streaming, the threshold to receive the 'Topic approaching maximum size' alert has been increased from 95% of the configured size used to 110%. The gen3 configurable trigger for error messages has been extended with the option to check whether the 'last-exception' message contained a certain text. This can be combined with the header-value match.
20 -* All - Buttons: The save and cancel buttons are placed slightly further apart to avoid misclicking. (#1022)
21 -* All - Systems: The positioning of Systems across Design, Create and Deploy phases are now synchronized to the position of their respective System in the Capture phase. (#687)
22 -
23 -====Bug fixes====
24 -
25 -* Create & Deploy - Styling: The styling of the event streaming canvas in the Create and Deploy phases has been slightly altered to make topic and event-processor names more readable. (#1055)
26 -* Deploy - Architecture: Containers are set inactive when they are removed in Design and unused.
27 -* Deploy - Releases: We fixed an issue that a lot of error popups were shown when you promoted a release version to a next environment. (#1087)
28 -* Manage - Triggers: Besides checking the error header, the error trigger is configured to check if an error message contains a term.
29 -
30 -
31 -=====Infra and image changes=====
32 -
33 -* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
5 +====Minor changes====
6 +* Create - Flow Designer: The Infinispan Cache Manager has been updated to provide an additional 'transport type' to offer more means for creating a clustered setup, provide clearer helptexts, and include validation on fields depending on the selected 'transport type'.
7 +* Design - Tenant: The technical name of a tenant cannot be changed once the tenant has been transferred to Create.
8 +* Create - Tenant: A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy.
9 +* Deploy - Architecture: The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header.
10 +* Deploy - Architecture: The machine health indicator and other progress bars have been improved visually.
11 +* Deploy - Properties: A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal.
12 +* Manage - Alerting: Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. Find out more information in our [[release blog>>Main.Release Information.Release Blogs.226 - Alerting Alchemy||target="blank"]] and our [[new alerting microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]].