Skip to Content
Last modified by Carlijn Kokkeler on 2024/04/18 13:11
From version 157.1
edited by Carlijn Kokkeler
on 2023/10/10 14:06
Change comment: There is no comment for this version
To version 151.1
edited by Erik Bakker
on 2023/09/13 07:02
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -206 - Situational Deployment
1 +205 - World Explorers
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -2,55 +2,53 @@
2 2  {{container layoutStyle="columns"}}(((
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.
5 +**Hi there, eMagiz developers!** We have processed additional feedback on the Manage phase to ensure you can more easily create overviews of your statistics, displaying all information correctly and improving the migration process to the next-generation architecture in the Create phase slightly. On top of that, we have improved the scalability of our new generation monitoring stack and the alerting structure. We will also release a new cloud template for our next-generation infrastructure to comply with technical requirements from our cloud provider.
6 6  
7 -== **Deployment Plan** ==
7 +== ** Mandatory Cloud Template Upgrade - Next-generation models ** ==
8 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.
9 +As can be seen on our [[status page>>https://status.emagiz.com/incidents/dbh6g9w3ks7q||target="blank"]], we will release a new cloud template for our next-generation models (both single and double lane) that will change a configuration in these templates to comply with technical and operational requirements from our cloud provider. The announcement of the status page itself holds more detail for those to whom it pertains.
11 11  
12 -//__Editing release properties__//
13 -With this release, it will be possible to change the description of a property by editing the property.
11 +== **Feedback Items** ==
14 14  
15 -//__JMS memory setting check__//
16 -A change in memory settings triggers redeployment of the container now.
13 +//__Improved Validation when migrating to the next-generation architecture__//
14 +To improve the migration process to the next-generation architecture, we now show a list of all reported problems, allowing the user to resolve them before migrating to the next-generation architecture.
17 17  
18 -//__Properties tab__//
19 -We have removed the deprecated tab Properties in the Deploy phase.
20 -
21 -//__Cleanup old images__//
22 -When a release is removed, the related unused images in the on-premises machines will be removed as well.
16 +{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
23 23  
24 -== **Store Improvements** ==
25 -
18 +//__Improved HTTP Statistics__//
19 +To improve the filtering and refresh functionality we offer on this overview, we have made several changes in this release that will improve the behavior of this overview.
26 26  
27 -== **Feedback Items** ==
21 +//__"Topic Full" alert restriction changed__//
22 +With this release, we will change the "Topic Full" trigger point in our standard set of alerts once a model uses the Event Streaming functionality. Before, the alert would trigger on 80%, but as we saw, this is too early to make the alert useful in the context of our customers. As a result, the threshold has been raised to 95% to accommodate real-life situations better.
28 28  
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.
24 +//__Improved performance Manage Dashboards__//
25 +We have improved the efficiency of retrieving the data shown in the Manage Dashboards for the next-generation architecture.
31 31  
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).
27 +//__Show values on the runtime level in Deploy Architecture__//
28 +We have improved the values shown on the runtime (i.e., container) level in Deploy Architecture so you can better assess whether the memory configuration is still suitable for your deployed solution.
34 34  
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.
30 +{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
31 +* JMS - The number of queues in the active release.
32 +* Messaging Container - The number of messaging integrations in the active release.
33 +* Messaging Connector - The number of messaging integrations related to this system in the active release.
34 +* API Gateway Container - The number of operations in the active release.
35 +* Event Streaming Container - The number of event processors in the active release.
37 37  
38 -//__Update flow designer version__//
39 -The framework used in the flow designer has been updated to the latest version.
37 +There might be multi-tenant and multi-runtime situations that do not always get to the exact number; however, this is a great improvement compared to showing no values.{{/info}}
40 40  
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.
39 +== **Bug Fixes** ==
43 43  
44 -//__Moving channels in the flow designer__//
45 -Moving already attached channels in the flow designer has been made sligthly easier.
41 +//__Improved information Queue Statistics__//
42 +Given several constraints, it could happen that specific queues needed to be correctly displayed within the Manage phase on your model, making it tough to manage them. This has been resolved with this release.
46 46  
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.
44 +//__Gain the ability again to configure certificates in Deploy Architecture again__//
45 +In restricting the configuration options on the certificate level in one of our latter releases, it became impossible for normal users to add and edit certificates within Deploy Architecture. To resolve this problem we have now released a fix to resolve this issue, giving people the ability again to add and edit certificates under Deploy Architecture.
49 49  
50 -
51 -
52 -== **Bug Fixes** ==
47 +//__Ensure that differing container configurations deploy the correct configuration__//
48 +When you run in a multi-runtime configuration and change the actual flows that need to run on container A vs. container B, it happened before that all flows were still being deployed on all runtimes. With this release, we will feed this information correctly to our infrastructure to ensure the correct and configured flows are deployed on the proper containers.
53 53  
50 +//__Remove queurying options in Manage__//
51 +To avoid errors and loading problems when analyzing your statistics in Manage, we have removed the option to select a default time range spanning more than seven days. This is to guarantee the stability of the solution and to avoid users getting unnecessary errors.
54 54  
55 55  == **Fancy Forum Answers** ==
56 56