Skip to Content

Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40
From version 187.1
edited by CarlijnKokkeler
on 2023/10/23 14:45
Change comment: There is no comment for this version
To version 505.2
edited by CarlijnKokkeler
on 2024/05/06 13:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -207 - Aligned State
1 +220 - Patch Parade
Content
... ... @@ -1,97 +1,82 @@
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!**
6 6  
7 -== **State Generation** ==
8 +== **Feedback Items** ==
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.
10 +//__Integration pattern information__//
11 +Integration pattern information of the selected message type has been added to the pop-up that is shown in Capture when creating a new integration.
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)
13 +[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]]
22 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 -Added support for `#JsonPath` usage in SpEL expressions
15 +//__Message queue history__//
16 +All events that relate to message queues (delete message, delete all messages or delete queue) are logged in the Manage phase instead of the Deploy phase.
25 25  
18 +[[image:Main.Images.Release Blog.WebHome@release-220-manage-history.png]]
26 26  
27 -== **Metrics Storage Duration** ==
28 -
29 -
30 -
20 +//__Search boxes__//
21 +Search boxes in the properties overview are now shown by default.
31 31  
32 -== **Feedback Items** ==
23 +[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]]
33 33  
34 -//__Alerting manual pause__//
35 -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.
25 +//__Set as mapped__//
26 +It is now possible to choose whether to set/unset all attributes of an entity as mapped in design.
36 36  
37 -//__Ordering of graphs in Manage__//
38 -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).
28 +[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]]
39 39  
40 -//__UTC times in Grafana panels__//
41 -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 +//__SSL settings__//
31 +Changes can now be deployed on SSL level without creating a new version of a flow in Create.
42 42  
43 -//__Update flow designer version__//
44 -The framework used in the flow designer has been updated, improving performance.
33 +//__Machine deletion__//
34 +When trying to delete a machine that still has containers linked to it, the user will be presented with a pop-up explaining why the machine cannot be deleted.
45 45  
46 -//__Carwash track TLS versions in logging__//
47 -A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
36 +[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]]
48 48  
49 -//__Moving channels in the flow designer__//
50 -Moving already attached channels in the flow designer has been made sligthly easier.
38 +//__JMS header handling__//
39 +Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new runtime image(LINK) has been released.
51 51  
52 -//__Topic sizes description change__//
53 -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.
41 +== **Bug Fixes** ==
42 +//__Annotation styling__//
43 +It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability.
54 54  
55 -//__Password change notification__//
56 -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.
45 +[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]]
57 57  
58 -//__Password comparison__//
59 -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.
47 +//__Filter rejection warnings__//
48 +A discard channel is required for filter components when “Throw exception on rejection” value is set to false.
60 60  
61 -//__Inactive user alerting__//
62 -Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
50 +[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]]
63 63  
64 -//__Alphabetical sorting on user level in HTTP statistics__//
65 -Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
52 +//__Manage Explore__//
53 +An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage.
66 66  
55 +//__Page refreshing__//
56 +Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment.
67 67  
68 -== **Bug Fixes** ==
58 +//__Message redelivery__//
59 +An issue has been fixed where large messages would be shown at the bottom of the page instead of the right side of the page.
69 69  
70 -//__Flow designer styling__//
71 -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 +//__Deployment plan__//
62 +We have implemented changes that should prevent a discrepantion between the overview of runtimes to be deployed shown at the beginning of a deployment plan (or at individual machine-type steps) and the actual execution of relevant steps.
72 72  
73 -//__Partial search for messages__//
74 -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 +//__Overview pages__//
65 +We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase.
75 75  
76 -//__Disk usage after cloud template update__//
77 -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 +//__Memory check__//
68 +Machines deleted in Design are excluded from the memory health check in Deploy, so that no unnecessary memory changes have to be done to delete machines.
78 78  
79 -//__Error handling migration__//
80 -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.
81 -
82 82  == **Fancy Forum Answers** ==
83 83  
84 84  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:
85 85  
86 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
87 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
88 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
89 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
90 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
74 +* [[Create an overview of DataFlows without any datatraffic>>https://my.emagiz.com/p/question/172825635703811872||target="blank"]]
75 +* [[Flowtest does not work>>https://my.emagiz.com/p/question/172825635703811773||target="blank"]]
76 +* [[Debugger blocks all other traffic>>https://my.emagiz.com/p/question/172825635703812013||target="blank"]]
91 91  
78 +== **Key Takeaways** ==
92 92  
93 -== **Key takeaways** ==
94 -
95 95  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:
96 96  
97 97  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
... ... @@ -98,10 +98,9 @@
98 98  * If you have feedback or ideas for us, talk to the Platypus
99 99  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
100 100  * Clear your browser cache (Ctrl + Shift + Del)
101 -* Check out the release notes [here]
86 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.219 - Creation Carousel.WebHome||target="blank"]]
102 102  * Start thinking about how the license tracker can aid your development
103 103  * Start thinking about major, minor, and patch
104 -* Upgrade to the latest build number
105 105  * Keep making great integrations
106 106  
107 107  Let's stay in touch and till next time!
... ... @@ -109,6 +109,11 @@
109 109  {{info}}
110 110  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
111 111  
112 -~*~* Indicates a next-generation-architecture only feature.
113 -{{/info}})))((({{toc/}}))){{/container}}
96 +{{/info}}
97 +)))
98 +
99 +(((
100 +{{toc/}}
101 +)))
114 114  {{/container}}
103 +{{/container}}