Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 189.1
edited by CarlijnKokkeler
on 2023/10/23 14:49
Change comment: There is no comment for this version
To version 488.1
edited by CarlijnKokkeler
on 2024/04/23 16:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +219 - Creation Carousel
Content
... ... @@ -1,101 +1,63 @@
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!** We have done much work for state generation, so that you can derive more information from your data! Examples are enrichment, aggregation, change detection and duplicate detection. State generation functionality is only accessible for models with an add-on state generation license. Next to state generation, several improvements regarding the alignment of components have been made. Moreover, performance improvements and bug fixes have been implemented. Lastly, a change in the metrics storage duration has been performed.
6 +**Hi there, eMagiz developers!** This release, we have a new version of our eMagiz Mendix connector available, that will support Mendix version 10 and higher. Furthermore, we have improved our functionality to enable users to seamlessly import OpenAPI specifications with URL paths of up to 300 characters in length. Lastly, we have done many bug fixes, one of which will ensure that SFTP sessions will be closed again after completion. For this fix, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been published.
6 6  
7 -== **State Generation** ==
8 -
9 -//__New components__//
10 -The following components have been added:
11 -* Aggregator: reverse of the splitter, used to combine multiple messages into a single one.
12 -* Infinispan metadata outbound channel adapter: Used to (temporarily) store metadata, which can be used to enrich messages, or make decisions in filters or scripts.
13 -* Content enricher: used to add properties to the payload of messages, similar to what the header enricher can do for headers.
14 -* Duplicate detector: Support object used to detect duplicate messages for a certain key on an inbound channel of a flow component. Duplicates can be marked or discarded.
15 -* Infinispan support objects, supporting the aggregator, metadata outbound channel adapter and content enricher.
16 -
17 -//__SpEL functions & JSON__//
18 -Added SpEL functions for:
19 -* Encoding & decoding Base64, Hex and hmac.
20 -* Date retrieval (currentDateTime, currentEpochMilli, currentEpochSecond).
21 -* Date conversion (DateTime to Epoch, Epoch to DateTime, DateTime formatter and DateTime parser).
22 -
23 -Added support for SpEL property accessors for XML and JSON, meaning that you can read message payloads in SpEL expressions easily. For example, to retrieve the value for 'id' in the following JSON String: `{"id":"123"}`, this SpEL expression suffices: `payload.id`.
24 -
25 -Added support for `#JsonPath` usage in SpEL expressions.
26 -
27 -//__New image version 2.0.0__//
28 -The above functionality are features of the new image version 2.0.0. Important to note is that the library used for Code Mappings has been changed. Changed the library used for Code Mappings. Any customer with Gen3 runtimes and code mappings is required to reset their infra flows prior to deploying on image 2.0.0.
29 -
30 -
31 -== **Metrics Storage Duration** ==
32 -
33 -
34 -
35 -
36 36  == **Feedback Items** ==
37 37  
38 -//__Alerting manual pause__//
39 -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.
10 +//__eMagiz Mendix connector__//
11 +We released a new version of our eMagiz Mendix connector that will support Mendix version 10 and higher.
40 40  
41 -//__Ordering of graphs in Manage__//
42 -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).
13 +//__Improved OpenAPI import__//
14 +The path length that eMagiz supports when importing OpenAPI specifications is now increased to a maximum of 300 characters.
43 43  
44 -//__UTC times in Grafana panels__//
45 -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.
16 +//__Flow test stack trace__//
17 +If a flow test creates a log line with level ‘Warning’ or ‘Error’ and there is a stack trace created, then we show the stack trace inside the log message on a separate tab.
46 46  
47 -//__Update flow designer version__//
48 -The framework used in the flow designer has been updated, improving performance.
19 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-stack-trace.png]]
49 49  
50 -//__Carwash track TLS versions in logging__//
51 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
21 +{{info}}With the release of Spring 6 in our previous release, some users reported that their filters have begun logging warnings about discarding messages even though the filter is configured to not throw an exception on rejection. For flows that process high numbers of messages (and potentially discard a lot of messages as well) this can significantly disturb the overview of the logs in the manage phase.
52 52  
53 -//__Moving channels in the flow designer__//
54 -Moving already attached channels in the flow designer has been made sligthly easier.
23 +To mitigate this, you can change the filter that throws the warning so it specifically refers to a discard channel. Given the chosen configuration, we advice to use the nullChannel option. This will silently drop the message without registering a warning in the log. In case you find the warning in the log a nice addition, we suggest to add an explicit discard channel leading to a logging outbound channel adapter. This log component can then be configured to throw a warning.
55 55  
56 -//__Topic sizes description change__//
57 -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.
25 +In the next release, we will aid you by adding a validation check that will force you to select a discard channel when it is currently not selected once you edit the flow to create a new version. More on this in the next release blog. {{/info}}
58 58  
59 -//__Password change notification__//
60 -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.
27 +== **Bug Fixes** ==
28 +//__Error handling__//
29 +When migrating to the current generation architecture, the default error handling will now also be migrated correctly, so that no manual changes have to be done for this.
61 61  
62 -//__Password comparison__//
63 -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.
31 +//__Volume mapping passwords__//
32 +Passwords for network volumes are now securely hidden in the runtime’s machine after deploying a new release.
64 64  
65 -//__Inactive user alerting__//
66 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
34 +//__Create integration removal__//
35 +When removing an integration from Create, the Create phase is now correctly updated.
67 67  
68 -//__Alphabetical sorting on user level in HTTP statistics__//
69 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
37 +//__Legacy statistics__//
38 +Legacy pages are now correctly hidden when running on the current runtime architecture.
70 70  
40 +//__Unused properties__//
41 +Users should not be able to edit or delete eMagiz properties, and so these eMagiz properties will now not be shown in the 'Unused property overview' anymore.
71 71  
72 -== **Bug Fixes** ==
43 +//__Enumeration values__//
44 +Users are now able to add and edit enumeration values while editing event processor flows in the Create phase.
73 73  
74 -//__Flow designer styling__//
75 -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.
46 +[[image:Main.Images.Release Blog.WebHome@release-219-creation-carousel-event-processor.png]]
76 76  
77 -//__Partial search for messages__//
78 -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".
48 +//__SFTP sessions__//
49 +SFTP session factories did not close their connection after it was complete. This could cause connection starvation on the SFTP server, and was especially noticable when using the SFTP Session Factory without caching, as that factory opens a new connection for every call. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V304.WebHome||target="blank"]] has been released.
79 79  
80 -//__Disk usage after cloud template update__//
81 -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.
82 -
83 -//__Error handling migration__//
84 -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.
85 -
86 86  == **Fancy Forum Answers** ==
87 87  
88 88  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:
89 89  
90 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
91 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
92 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
93 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
94 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
55 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
56 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
57 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
95 95  
59 +== **Key Takeaways** ==
96 96  
97 -== **Key takeaways** ==
98 -
99 99  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:
100 100  
101 101  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -102,10 +102,9 @@
102 102  * If you have feedback or ideas for us, talk to the Platypus
103 103  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
104 104  * Clear your browser cache (Ctrl + Shift + Del)
105 -* Check out the release notes [here]
67 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
106 106  * Start thinking about how the license tracker can aid your development
107 107  * Start thinking about major, minor, and patch
108 -* Upgrade to the latest build number
109 109  * Keep making great integrations
110 110  
111 111  Let's stay in touch and till next time!
... ... @@ -113,6 +113,11 @@
113 113  {{info}}
114 114  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
115 115  
116 -~*~* Indicates a next-generation-architecture only feature.
117 -{{/info}})))((({{toc/}}))){{/container}}
77 +{{/info}}
78 +)))
79 +
80 +(((
81 +{{toc/}}
82 +)))
118 118  {{/container}}
84 +{{/container}}