Skip to Content

Changes for page 232 - Bug Busters

Last modified by Carlijn Kokkeler on 2024/11/04 11:23
From version 108.1
edited by Carlijn Kokkeler
on 2023/09/18 11:00
Change comment: There is no comment for this version
To version 307.1
edited by Carlijn Kokkeler
on 2024/08/26 15:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -205 - World Explorers
1 +228 - Monitoring Mania
Content
... ... @@ -1,71 +1,19 @@
1 -{{container}}
2 -{{container layoutStyle="columns"}}(((
3 -[[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
1 +During our recent sprint cycle, we have done several improvements to the monitoring graphs in Manage. Moreover, we have done several improvements in deploy architecture and flow testing. Please find out all our changes & bug fixes below.
4 4  
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.
3 +Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.228 - Monitoring Mania||target="blank"]].
6 6  
7 -== **Mandatory Cloud Template Upgrade - Next-generation models ** ==
5 +====Minor changes====
6 +* Community - Release Notes: The legacy release notes tab has been removed.
7 +* Create - Flow Testing: Test messages can now be edited or removed while in the edit mode of the flow testing functionality.
8 +* Deploy - Architecture: The SSL section in runtime settings has more elaborate helptext. (#1277)
9 +* Deploy - Architecture: A pop-up with a warning will be shown when containers are configured with less memory than recommended. (#1423)
10 +* Deploy - Deployment Plan: The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.
11 +* Deploy - History: We added logging for when properties are deleted from the unused properties screen. (#1428)
12 +* Deploy - Missing Properties Overview: Setting the value of a missing property will now automatically remove it from the missing properties overview. Besides that, search and sort functionality have been added to the missing properties overview. (#1436)
13 +* Manage - Monitoring: We have done many improvements to the Monitoring graphs. Find out all improvements in our [[release blog>>Main.Release Information.Release Blogs.228 - Monitoring Mania||target="blank"]]. (#866)
8 8  
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.
10 -
11 -== **Feedback Items** ==
12 -
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.
15 -
16 -{{info}}Note that when no problem is found, the migration process of that runtime will start automatically.{{/info}}
17 -
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.
20 -
21 -//__Show values on the runtime level in Deploy Architecture__//
22 -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.
23 -
24 -{{info}}To get to the values we use different calculation methods per type of runtime, as certain runtime types have various reasons for existence.
25 -* JMS - The number of queues in the active release.
26 -* Messaging Container - The number of messaging integrations in the active release.
27 -* Messaging Connector - The number of messaging integrations related to this system in the active release.
28 -* API Gateway Container - The number of operations in the active release.
29 -* Event Streaming Container - The number of event processors in the active release.
30 -
31 -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}}
32 -
33 -== **Bug Fixes** ==
34 -
35 -//__Gain the ability again to configure certificates in Deploy Architecture again__//
36 -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.
37 -
38 -//__Ensure that differing container configurations deploy the correct configuration__//
39 -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.
40 -
41 -//__Remove queurying options in Manage__//
42 -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.
43 -
44 -== **Fancy Forum Answers** ==
45 -
46 -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:
47 -
48 -* [[Getting files from subfolders (FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]
49 -
50 -== **Key takeaways** ==
51 -
52 -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:
53 -
54 -* If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
55 -* If you have feedback or ideas for us, talk to the Platypus
56 -* Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
57 -* Clear your browser cache (Ctrl + Shift + Del)
58 -* Check out the release notes [here]
59 -* Start thinking about how the license tracker can aid your development
60 -* Start thinking about major, minor, and patch
61 -* Upgrade to the latest build number
62 -* Keep making great integrations
63 -
64 -Let's stay in touch and till next time!
65 -
66 -{{info}}
67 -~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
68 -
69 -~*~* Indicates a next-generation-architecture only feature.
70 -{{/info}})))((({{toc/}}))){{/container}}
71 -{{/container}}
15 +====Bug fixes====
16 +* Create - Flow Designer: We removed legacy properties in connections through the eMagiz Mendix connector. This means that you will not get blocked anymore when deploying to Production. (#1065)
17 +* Create - Flow Designer: The copy paste functionality in the flow designer does not change the configuration of existing flow components anymore. (#1392)
18 +* Create - Flow Testing: It is now possible to reuse the test messages created in other flows within the routing and vice versa. (#1274)
19 +* Deploy - Architecture: We fixed a bug where new machines could be deployed with exceeding memory. (#1295)