Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 185.1
edited by CarlijnKokkeler
on 2023/10/23 14:44
Change comment: There is no comment for this version
To version 608.1
edited by Erik Bakker
on 2024/07/16 14:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +225 - Pop-up Party
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.CarlijnKokkeler
1 +XWiki.ebakker
Content
... ... @@ -1,96 +1,88 @@
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!** In this release, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below!
6 6  
7 -== **State Generation** ==
8 +== **Feedback Items** ==
9 +//__Alerting notification settings__//
8 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.
11 +//__Process containers__//
12 +If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern.
16 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 -* 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`.
23 -* Added support for `#JsonPath` usage in SpEL expressions
14 +//__Design settings__//
15 +When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
24 24  
17 +[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
25 25  
26 -== **Metrics Storage Duration** ==
19 +//__Untested images__//
20 + A warning will be shown when a release is activated on **Production** with a new runtime image version which has not been tested on acceptance before.
27 27  
22 +[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
28 28  
24 +{{warning}}
25 +The following restrictions apply to this functionality:
29 29  
27 +* When accepting the risk you accept the risk for the **whole** model.
28 +* If any release based on the same runtime image is already activated on Acceptance you will **not** be warned.
29 +{{/warning}}
30 30  
31 -== **Feedback Items** ==
31 +//__Infinispan Cache Manager__//
32 +We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
33 +
34 +//__Infinispan Cache Manager error message__//
35 +We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
32 32  
33 -//__Alerting manual pause__//
34 -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.
37 +//__Flow bump__//
38 +When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
39 +
40 +[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
35 35  
36 -//__Ordering of graphs in Manage__//
37 -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).
42 +//__Unused support objects__//
43 +Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
38 38  
39 -//__UTC times in Grafana panels__//
40 -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.
45 +[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
46 +
47 +//__Deleting routes__//
48 +For clarity purposes, a confirmation pop-up will be shown when deleting routes.
41 41  
42 -//__Update flow designer version__//
43 -The framework used in the flow designer has been updated, improving performance.
50 +[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
44 44  
45 -//__Carwash track TLS versions in logging__//
46 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
47 -
48 -//__Moving channels in the flow designer__//
49 -Moving already attached channels in the flow designer has been made sligthly easier.
50 -
51 -//__Topic sizes description change__//
52 -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.
53 -
54 -//__Password change notification__//
55 -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.
56 -
57 -//__Password comparison__//
58 -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.
59 -
60 -//__Inactive user alerting__//
61 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
62 -
63 -//__Alphabetical sorting on user level in HTTP statistics__//
64 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
65 -
66 -
52 +//__Debug queue__//
53 +The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
54 +
55 +[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
56 +
67 67  == **Bug Fixes** ==
58 +//__Internal server error__//
59 +The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
68 68  
69 -//__Flow designer styling__//
70 -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.
61 +//__Namespace update__//
62 +Editing a namespace used in a message definition automatically updates the message definition & transformations.
71 71  
72 -//__Partial search for messages__//
73 -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".
64 +//__Error pop-up__//
65 +We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
74 74  
75 -//__Disk usage after cloud template update__//
76 -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.
67 +//__SMB inbound channel adapter__//
68 +The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
77 77  
78 -//__Error handling migration__//
79 -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.
70 +//__Heap memory__//
71 +The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
80 80  
73 +//__Classpath conflicts__//
74 +We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V311.WebHome||target="blank"]] is available.
75 +
81 81  == **Fancy Forum Answers** ==
82 82  
83 83  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:
84 84  
85 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
86 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
87 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
88 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
89 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
80 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
81 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
82 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
90 90  
84 +== **Key Takeaways** ==
91 91  
92 -== **Key takeaways** ==
93 -
94 94  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:
95 95  
96 96  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -97,10 +97,9 @@
97 97  * If you have feedback or ideas for us, talk to the Platypus
98 98  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
99 99  * Clear your browser cache (Ctrl + Shift + Del)
100 -* Check out the release notes [here]
92 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
101 101  * Start thinking about how the license tracker can aid your development
102 102  * Start thinking about major, minor, and patch
103 -* Upgrade to the latest build number
104 104  * Keep making great integrations
105 105  
106 106  Let's stay in touch and till next time!
... ... @@ -108,6 +108,11 @@
108 108  {{info}}
109 109  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
110 110  
111 -~*~* Indicates a next-generation-architecture only feature.
112 -{{/info}})))((({{toc/}}))){{/container}}
102 +{{/info}}
103 +)))
104 +
105 +(((
106 +{{toc/}}
107 +)))
113 113  {{/container}}
109 +{{/container}}