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 -22 0-PatchParade1 +226 - Alerting Alchemy - Content
-
... ... @@ -3,82 +3,56 @@ 3 3 ((( 4 4 [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] 5 5 6 -**Hi there, eMagiz developers!** In thelast few weeks,we worked hard onsolvingseveralfeedbackitemsand bugfixes.Ontop of that,wehavereleasedanew[[runtimeimage>>doc:Main.ReleaseInformation.Runtime Images.V306.WebHome||target="blank"]]thatensuresthatKafka outbound channeladapterscan nowalso parsejms_destinationand jms_replyToheaders.Withoutfurtherado,letuslookatourimprovements andbugfixesbelow.6 +**Hi there, eMagiz developers!** The past few weeks we have worked hard to release our new queue alerting design. Please find out all new features in our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning. Note that the new queue alerting will not yet be availalbe for queues with message redelivery. Next to alerting, we have worked on tenant items, machine pop-ups and progress bars, as well as the Infinispan Cache Manager. Find out all below! 7 7 8 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. 9 9 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. 19 +[[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]] 12 12 13 -[[image:Main.Images.Release Blog.WebHome@release-220-integration-pattern.png]] 14 14 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. 22 +{{info}}Please check out our [[Standard Alerting eMagiz>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] microlearning for an elaborate explanation of our new queue alerting design. {{/info}} 17 17 18 -[[ima ge:Main.Images.ReleaseBlog.WebHome@release-220-manage-history.png]]24 +eMagiz will migrate your dynamic queue alerts on the **release day** when you are **fully** or **partially** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. When doing so, we will configure the new queue alert in a similar fashion to best match its current behaviour. Note that the queue alerting will only function for models that are **fully** migrated to the [[current runtime architecture>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]]. Should you want to change or create new queue alerts, you can do so starting the day **after** the release to avoid conflicts with our migration. 19 19 20 -//__Search boxes__// 21 -Search boxes in the properties overview are now shown by default. 26 +{{warning}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/warning}} 22 22 23 -[[image:Main.Images.Release Blog.WebHome@release-220-search-boxes.png]] 28 +//__Tenant technical name__// 29 +The technical name of a tenant cannot be changed once the tenant has been transferred to Create. 24 24 25 -//__ Set asmapped__//26 - Itisnowpossible to choosewhethertoset/unsetallattributesof anentityasmappedindesign.31 +//__Tenant transfer__// 32 +A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. 27 27 28 -[[image:Main.Images.Release Blog.WebHome@release-220-mapped-entity.png]] 34 +//__Property placeholder__// 35 +A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal. 29 29 30 -//__SSL settings__// 31 -Changes can now be deployed on SSL level without creating a new version of a flow in Create. 37 +//__Machine pop-up__// 38 +* The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. 39 +* The machine health indicator has been improved visually. 40 +* Several progress bars have been improved visually. 32 32 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. 42 +[[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]] 43 + 44 +//__Infinispan Cache Manager__// 45 +The Infinispan Cache Manager has been updated to: 46 +* Provide an additional 'transport type' to offer more means for creating a clustered setup; 47 +* Provide clearer helptexts explaining which of the options is needed and what its effect is; 48 +* Include validation on fields depending on the selected 'transport type'. 35 35 36 -[[image:Main.Images.Release Blog.WebHome@release-220-machine-deletion.png]] 37 - 38 -== **Bug Fixes** == 39 -//__Annotation styling__// 40 -It is now possible to use enters in Annotations, so that multiple line spaces can be added, ensuring better readability. 41 - 42 -[[image:Main.Images.Release Blog.WebHome@release-220-edit-annotation.png]] 43 - 44 -//__Filter rejection warnings__// 45 -A discard channel is required for filter components when “Throw exception on rejection” value is set to false. 46 - 47 -[[image:Main.Images.Release Blog.WebHome@release-220-discard-channel.png]] 48 - 49 -//__Manage Explore__// 50 -An issue has been fixed where navigating to the Explore tab in Manage would sometimes redirect users to the homepage. 51 - 52 -//__Page refreshing__// 53 -Switching between environments refreshes the Queue browser and Redelivery pages correctly for the selected environment. 54 - 55 -//__JMS header handling__// 56 -Kafka outbound channel adapters can now also parse jms_destination and jms_replyTo headers. For this, a new [[runtime image>>doc:Main.Release Information.Runtime Images.V306.WebHome||target="blank"]] has been released. 57 - 58 -//__Message redelivery__// 59 -An issue has been fixed where large messages would be shown at the bottom of the Redelivery page instead of the right side of the page. 60 - 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. 63 - 64 -//__Overview pages__// 65 -We fixed an issue that you could not navigate to the last page of some overview pages in Manage phase. 66 - 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. 69 - 70 -//__Copy password__// 71 -The copy to clipboard button now copies the actual value of passwords instead of the masked value of them. 72 - 73 -//__Gateway infra flows__// 74 -We fixed the incorrect generation of gateway infra flows for models using the OAuth 2.0 security scheme in Spring 6. 75 - 76 76 == **Fancy Forum Answers** == 77 77 78 78 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: 79 79 80 -* [[ SwaggerUI:503 ServiceUnavailable>>https://my.emagiz.com/p/question/172825635703824607||target="blank"]]81 -* [[ PATCH callwithoutRESTtemplate>>https://my.emagiz.com/p/question/172825635703824685||target="blank"]]54 +* [[no output-channel or replyChannel header available>>https://my.emagiz.com/p/question/172825635703901361||target="blank"]] 55 +* [[last flow unknown error with SFTP connection in Entry>>https://my.emagiz.com/p/question/172825635703901485||target="blank"]] 82 82 83 83 == **Key Takeaways** == 84 84 ... ... @@ -88,7 +88,7 @@ 88 88 * If you have feedback or ideas for us, talk to the Platypus 89 89 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 90 90 * Clear your browser cache (Ctrl + Shift + Del) 91 -* Check out the release notes [[here>>doc:Main.Release Information.Portal.22 0-PatchParade.WebHome||target="blank"]]65 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.226 - Alerting Alchemy.WebHome||target="blank"]] 92 92 * Start thinking about how the license tracker can aid your development 93 93 * Start thinking about major, minor, and patch 94 94 * Keep making great integrations