Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 551.1
edited by CarlijnKokkeler
on 2024/06/17 12:09
Change comment: There is no comment for this version
To version 157.1
edited by CarlijnKokkeler
on 2023/10/10 14:06
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -223 - TBD
1 +206 - Situational Deployment
Content
... ... @@ -1,49 +1,64 @@
1 1  {{container}}
2 -{{container layoutStyle="columns"}}
3 -(((
2 +{{container layoutStyle="columns"}}(((
4 4  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
5 5  
6 -**Hi there, eMagiz developers!**
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 +
7 +== **Deployment Plan** ==
8 +
9 +//__Improved deployment plan to make the process better and more predictable__//
10 +The algorithm for genarating 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.
11 +
12 +//__Editing release properties__//
13 +With this release, it will be possible to change the description of a property by editing the property.
14 +
15 +//__JMS memory setting check__//
16 +A change in memory settings triggers redeployment of the container now.
17 +
18 +//__Properties tab__//
19 +We have removed the deprecated tab Properties in the Deploy phase.
7 7  
8 -== **Feedback Items** ==
9 -//__SwaggerUI default__//
10 -Model contacts are now able to select a default SwaggerUI environment from the API management settings in the Design phase. The environment selected here will be the first and the default value of SwaggerUI server dropdown.
21 +//__Cleanup old images__//
22 +When a release is removed, the related unused images in the on-premises machines will be removed as well.
11 11  
12 -[[image:Main.Images.Release Blog.WebHome@release-223-default-swaggerui.png]]
24 +== **Store Improvements** ==
25 +
13 13  
14 -== **Bug Fixes** ==
15 -//__Cron triggers__//
16 -Cron triggers now allow for hours, days and months prepended by a 0, for example 05.
27 +== **Feedback Items** ==
17 17  
18 -[[image:Main.Images.Release Blog.WebHome@release-222-cron-triggers.png]]
29 +//__Alerting manual pause__//
30 +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.
19 19  
20 -//__Trigger activation__//
21 -Previously, when users were logged out from eMagiz during the execution of the deployment plan, it seemed that the portal reactived triggers, but this was not done. From now on, users are blocked from being logged out during deployment execution, so that triggers are re-enabled after the deployment plan has been executed.
32 +//__Ordering of graphs in Manage__//
33 +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).
22 22  
23 -//__Multiple users deploying__//
24 -Users are blocked from deploying at the same time on the same environment on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture.
35 +//__UTC times in Grafana panels__//
36 +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.
25 25  
26 -[[image:Main.Images.Release Blog.WebHome@release-222-users-deploying.png]]
38 +//__Update flow designer version__//
39 +The framework used in the flow designer has been updated to the latest version.
27 27  
28 -//__Invalid memory configurations__//
29 -We have improved machine health calculations to prevent the creation of a machine with invalid memory configurations.
41 +//__Carwash track TLS versions in logging__//
42 +A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
30 30  
31 -//__Property value synchronization__//
32 -Property values displayed in the Flow Designer and property values of your active release are now synchronized correctly.
44 +//__Moving channels in the flow designer__//
45 +Moving already attached channels in the flow designer has been made sligthly easier.
33 33  
34 -//__JMS number__//
35 -The number on the JMS container correctly displays the amount of queues present in Design.
47 +//__Topic sizes description change__//
48 +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.
36 36  
37 -[[image:Main.Images.Release Blog.WebHome@release-222-jms.png]]
50 +
51 +
52 +== **Bug Fixes** ==
38 38  
54 +
39 39  == **Fancy Forum Answers** ==
40 40  
41 41  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:
42 42  
43 -* [[SunCertPathBuilderException using a Keystore>>https://my.emagiz.com/p/question/172825635703850115||target="blank"]]
44 -* [[Name of User in header>>https://my.emagiz.com/p/question/172825635703850290||target="blank"]]
59 +* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
45 45  
46 -== **Key Takeaways** ==
61 +== **Key takeaways** ==
47 47  
48 48  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:
49 49  
... ... @@ -51,9 +51,10 @@
51 51  * If you have feedback or ideas for us, talk to the Platypus
52 52  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
53 53  * Clear your browser cache (Ctrl + Shift + Del)
54 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.222 - Flee Frustration.WebHome||target="blank"]]
69 +* Check out the release notes [here]
55 55  * Start thinking about how the license tracker can aid your development
56 56  * Start thinking about major, minor, and patch
72 +* Upgrade to the latest build number
57 57  * Keep making great integrations
58 58  
59 59  Let's stay in touch and till next time!
... ... @@ -61,11 +61,6 @@
61 61  {{info}}
62 62  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
63 63  
64 -{{/info}}
65 -)))
66 -
67 -(((
68 -{{toc/}}
69 -)))
80 +~*~* Indicates a next-generation-architecture only feature.
81 +{{/info}})))((({{toc/}}))){{/container}}
70 70  {{/container}}
71 -{{/container}}