Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 175.1
edited by CarlijnKokkeler
on 2023/10/12 12:38
Change comment: There is no comment for this version
To version 505.2
edited by CarlijnKokkeler
on 2024/05/06 13:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +220 - Patch Parade
Content
... ... @@ -1,108 +1,81 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}(((
2 +{{container layoutStyle="columns"}}
3 +(((
3 3  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
4 4  
5 -**Hi there, eMagiz developers!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.
6 +**Hi there, eMagiz developers!**
6 6  
7 -== **Release Date Change** ==
8 -As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM. We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
8 +== **Feedback Items** ==
9 9  
10 -== **Deployment Plan** ==
10 +//__Integration pattern information__//
11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
11 11  
12 -//__Improved deployment plan to make the process better and more predictable__//
13 -The algorithm for generating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines.
13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
14 14  
15 -//__Editing release properties__//
16 -With this release, it will be possible to change the description of a property by editing the property.
15 +//__Message queue history__//
16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
17 17  
18 -//__Container memory settings__//
19 -A change in memory settings triggers redeployment of the container now.
18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
20 20  
21 -//__Properties tab__//
22 -We have removed the deprecated tab Properties in the Deploy phase.
20 +//__Search boxes__//
21 +Search boxes in the properties overview are now shown by default.
23 23  
24 -//__Cleanup old images__//
25 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
26 26  
27 -//__Performance improvements for loading releases__//
28 -Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
25 +//__Set as mapped__//
26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
29 29  
30 -== **Store Improvements** ==
28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
31 31  
32 -//__Message definition elements order__//
33 -We fixed an issue that the order of message definition elements was changed after being imported.
30 +//__SSL settings__//
31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create.
34 34  
35 -//__Importing a store item with synchronous message definitions__//
36 -We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
33 +//__Machine deletion__//
34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted.
37 37  
38 -//__Importing store items containing static copies__//
39 -We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
40 40  
41 -//__Importing Store content__//
42 -We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
38 +//__JMS header handling__//
39 +Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new runtime image(LINK) has been released.
43 43  
44 -//__Store disclaimer__//
45 -Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
41 +== **Bug Fixes** ==
42 +//__Annotation styling__//
43 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
46 46  
47 -== **Feedback Items** ==
45 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
48 48  
49 -//__Alerting manual pause__//
50 -A few releases ago we changed the behavior of alerting in the deployment plan. Now each time when a deployment plan is executed the alerting will be automatically re-enabled when the deployer closes the deployment plan or closes the web browser. The majority of the users are happy with the new behavior, but there are some use cases that you do not want start the alerting immediately. With this release, if alerting has been paused manually, this will not be activated automatically after a release deployment.
47 +//__Filter rejection warnings__//
48 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
51 51  
52 -//__Ordering of graphs in Manage__//
53 -The graphs in Manage are now ordered according to importance. This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).
50 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
54 54  
55 -//__UTC times in Grafana panels__//
56 -All Grafana panels now show UTC times, which are normally used in eMagiz, instead of local (browser) time zones. This way, it is easier to match graphs with logging events or alerts.
52 +//__Manage Explore__//
53 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
57 57  
58 -//__Update flow designer version__//
59 -The framework used in the flow designer has been updated to the latest version.
55 +//__Page refreshing__//
56 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
60 60  
61 -//__Carwash track TLS versions in logging__//
62 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
58 +//__Message redelivery__//
59 +An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page.
63 63  
64 -//__Moving channels in the flow designer__//
65 -Moving already attached channels in the flow designer has been made sligthly easier.
61 +//__Deployment plan__//
62 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps.
66 66  
67 -//__Topic sizes description change__//
68 -In the change description (and History) when altering the topic size of a topic the new and old value were switched around creating confusion, this has been resolved.
64 +//__Overview pages__//
65 +We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase.
69 69  
70 -//__Password change notification__//
71 -When an account password change request is made, even when this fails, a mail is sent to the account owner to inform the owner about the action.
67 +//__Memory check__//
68 +Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines.
72 72  
73 -//__Password comparison__//
74 -When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password corresponds with a password in the database.
75 -
76 -//__Inactive user alerting__//
77 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
78 -
79 -//__Alphabetical sorting on user level in HTTP statistics__//
80 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
81 -
82 -//__SOAP Web services path__//
83 -Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
84 -
85 -== **Bug Fixes** ==
86 -
87 -//__Flow designer styling__//
88 -The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
89 -
90 -//__Partial search for messages__//
91 -It is now possible to search on messages partially in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
92 -
93 -//__Disk usage after cloud template update__//
94 -In the last cloud template update there was an issue with disk performance. This has been resolved in this release. You can manually upgrade your cloud template, or rely on automatic updates.
95 -
96 -//__Error handling migration__//
97 -If there is no custom error handling, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow. This has been fixed by adding a migration step, where we set the error channel of all inbounds in a flow to “errorChannel” if the custom error handling is set to false.
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 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
74 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
75 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
76 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
104 104  
105 -== **Key takeaways** ==
78 +== **Key Takeaways** ==
106 106  
107 107  Thanks to all who helped build and those who tested and gave feedback to improve the product. To end this post, here are some key takeaways for you:
108 108  
... ... @@ -110,10 +110,9 @@
110 110  * If you have feedback or ideas for us, talk to the Platypus
111 111  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
112 112  * Clear your browser cache (Ctrl + Shift + Del)
113 -* Check out the release notes [here]
86 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
114 114  * Start thinking about how the license tracker can aid your development
115 115  * Start thinking about major, minor, and patch
116 -* Upgrade to the latest build number
117 117  * Keep making great integrations
118 118  
119 119  Let's stay in touch and till next time!
... ... @@ -121,6 +121,11 @@
121 121  {{info}}
122 122  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
123 123  
124 -~*~* Indicates a next-generation-architecture only feature.
125 -{{/info}})))((({{toc/}}))){{/container}}
96 +{{/info}}
97 +)))
98 +
99 +(((
100 +{{toc/}}
101 +)))
126 126  {{/container}}
103 +{{/container}}