Changes for page 226 - Alerting Alchemy
Last modified by CarlijnKokkeler on 2024/07/30 16:40
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -2 07- AlignedState1 +226 - Alerting Alchemy - Content
-
... ... @@ -1,70 +1,56 @@ 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 donemuch work for state generation, so that you can derive more information from your data! Examplesareenrichment, aggregation, change detection and duplicatedetection. State generation functionality isonly 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, 6 6 7 -== **State Generation** == 8 +== **Feedback Items** == 9 +//__Queue alerting__// 10 +Alerting for message queues has been improved for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, which includes the following improvements: 11 +* New UI that shows all queues and the alerting that is active on them. 12 +* Every queue in the model will be automatically added to the list of queues in Manage - Alerting. 13 +* Triggers of a queue will be automatically enabled or disabled based on whether that queue is included in the release. 14 +* Added 2 new trigger types "inactivity check" and "periodic activity check" that replace the "queue throughput" alert. 15 +** These checks can now run for a (very) long time, whereas the "queue throughput" was limited by 1 hour. 16 +* The alert generation has been solidified to reduce the likelihood that your alerting is affected with false positives or false negatives during eMagiz maintenance. 17 +* When the same check of multiple queues trigger at the same time, the alerts will be aggregated into a single summarized email instead of a single email per alert. 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. 19 +If your model is running on the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture, you will be migrated on the day of release. eMagiz will transfer the queue alerts that you have currently configured to the closest match in the new alerting stack. Models that are in the process of migrating to the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture during the time of the release of this feature will be able to pre-configure their new queue alert triggers, but will not be able to make active use of them until the runtime migration has finished. 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). 21 +{{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}} 22 22 23 - Added support for SpEL propertyaccessors for XMLand JSON,meaningthat you can read messagepayloadsin SpELexpressionseasily. Forexample, toretrievethe valuefor'id' inthe followingJSON String: `{"id":"123"}`, this SpEL expressionsuffices: `payload.id`.23 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]] 24 24 25 -Added support for `#JsonPath` usage in SpEL expressions. 25 +//__Tenant technical name__// 26 + The technical name of a tenant cannot be changed once the tenant has been transferred to Create. 26 26 27 -//__ New imageversion2.0.0__//28 - Theabovefunctionalitiesare featuresofthenewimage version2.0.0. Important to note isthat thelibrary used for CodeMappingshas beenchanged. Changedthe library used forCode Mappings. Any customerwithGen3 runtimes and code mappingsisrequired to reset theirinfraflows prior to deploying on image 2.0.0.28 +//__Tenant transfer__// 29 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. 29 29 30 -//__ Component pages__//31 - Pagesto add thenew componentshavebeencreated.Forms have been creatednicely withproper help texts.TheEHCachecachemanagerhasbeen removed.31 +//__Property placeholder__// 32 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal. 32 32 33 -== **Metrics Storage Duration** == 34 -Manage - Monitoring: We will change the retention of monitoring data of different environments. For minute level data, it will be kept for test, acceptance and production environments for 5, 7 and 30 days respectively. Then the minute level data will be reduced to hour level data then will be stored for test, acceptance and production for 3, 6 and 12 months respectively. 34 +//__Machine pop-up__// 35 +* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. 36 +* The machine health indicator has been improved visually. 37 +* Several progress bars have been improved visually. 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release-blog-207-aligned-state-metrics-storage.png]] 37 - 38 -== **Feedback Items** == 39 - 40 -//__Import from store__// 41 -Design - Message Mapping: The button 'Import from Store' will directly open the store instead of showing a pop asking whether the store should be opened. 42 - 43 -//__Save and cancel buttons__// 44 -The Save and Cancel buttons have been placed slightly further apart from each other to avoid misclicking. 45 - 46 -//__User session times__// 47 -Manage - Monitoring: The user session times for 3rd generation runtime dashboards have been extended, so that the user is not thrown out of the model when using the Manage phase for longer than an hour. 48 - 39 +[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]] 49 49 50 50 51 51 == **Bug Fixes** == 52 52 53 - 54 - 55 55 == **Fancy Forum Answers** == 56 56 57 57 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: 58 58 59 -* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]] 60 -* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]] 61 -* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]] 62 -* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]] 63 -* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]] 48 +* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] 49 +* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] 50 +* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] 64 64 52 +== **Key Takeaways** == 65 65 66 -== **Key takeaways** == 67 - 68 68 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: 69 69 70 70 * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] ... ... @@ -71,10 +71,9 @@ 71 71 * If you have feedback or ideas for us, talk to the Platypus 72 72 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 73 73 * Clear your browser cache (Ctrl + Shift + Del) 74 -* Check out the release notes [here] 60 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]] 75 75 * Start thinking about how the license tracker can aid your development 76 76 * Start thinking about major, minor, and patch 77 -* Upgrade to the latest build number 78 78 * Keep making great integrations 79 79 80 80 Let's stay in touch and till next time! ... ... @@ -82,6 +82,11 @@ 82 82 {{info}} 83 83 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 84 84 85 -~*~* Indicates a next-generation-architecture only feature. 86 -{{/info}})))((({{toc/}}))){{/container}} 70 +{{/info}} 71 +))) 72 + 73 +((( 74 +{{toc/}} 75 +))) 87 87 {{/container}} 77 +{{/container}}