Wiki source code of 226 - Alerting Alchemy
Version 636.1 by CarlijnKokkeler on 2024/07/29 13:15
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.1 | 1 | {{container}} |
| |
254.1 | 2 | {{container layoutStyle="columns"}} |
| 3 | ((( | ||
| |
401.1 | 4 | [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]] |
| |
1.1 | 5 | |
| |
623.1 | 6 | **Hi there, eMagiz developers!** In this release, |
| |
567.1 | 7 | |
| |
464.1 | 8 | == **Feedback Items** == |
| |
623.1 | 9 | //__Queue alerting__// |
| |
625.1 | 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: |
| |
623.1 | 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. | ||
| |
629.1 | 18 | |
| |
628.1 | 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. |
| |
624.1 | 20 | |
| |
626.1 | 21 | {{info}}Please note that the new queue alerting will not yet be available for queues with message redelivery. {{/info}} |
| |
636.1 | 22 | |
| |
635.1 | 23 | {{info}}Please check out our [[Standard Alerting eMagiz microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-manage-alerting-gen3||target="blank"]] for an elaborate explanation of our new alerting design. {{/info}} |
| |
626.1 | 24 | |
| |
631.1 | 25 | [[image:Main.Images.Release Blog.WebHome@release-226-alerting.png]] |
| 26 | |||
| |
625.1 | 27 | //__Tenant technical name__// |
| |
627.1 | 28 | The technical name of a tenant cannot be changed once the tenant has been transferred to Create. |
| 29 | |||
| |
625.1 | 30 | //__Tenant transfer__// |
| |
627.1 | 31 | A tenant cannot be untransferred from Create if the connector container of that tenant is still active in Deploy. |
| 32 | |||
| |
625.1 | 33 | //__Property placeholder__// |
| |
627.1 | 34 | A property placeholder which contains a tenant name will be hidden in case its values and the technical name of the tenant are equal. |
| |
625.1 | 35 | |
| |
633.1 | 36 | //__Machine pop-up__// |
| 37 | * The machine pop-up in Deploy Architecture now shows the name of the machine in the pop-up header. | ||
| 38 | * The machine health indicator has been improved visually. | ||
| 39 | * Several progress bars have been improved visually. | ||
| 40 | |||
| 41 | [[image:Main.Images.Release Blog.WebHome@release-226-machine-name.png]] | ||
| 42 | |||
| |
634.1 | 43 | //__Infinispan Cache Manager__// |
| 44 | The Infinispan Cache Manager has been updated to: | ||
| 45 | * Provide an additional 'transport type' to offer more means for creating a clustered setup; | ||
| 46 | * Provide clearer helptexts explaining which of the options is needed and what its effect is; | ||
| 47 | * Include validation on fields depending on the selected 'transport type'. | ||
| |
633.1 | 48 | |
| |
1.1 | 49 | == **Fancy Forum Answers** == |
| 50 | |||
| |
30.1 | 51 | 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: |
| |
1.1 | 52 | |
| |
601.1 | 53 | * [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]] |
| 54 | * [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]] | ||
| 55 | * [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]] | ||
| |
1.1 | 56 | |
| |
348.1 | 57 | == **Key Takeaways** == |
| |
1.1 | 58 | |
| |
149.1 | 59 | 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: |
| |
1.1 | 60 | |
| |
30.1 | 61 | * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] |
| |
1.1 | 62 | * If you have feedback or ideas for us, talk to the Platypus |
| |
151.1 | 63 | * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. |
| |
1.1 | 64 | * Clear your browser cache (Ctrl + Shift + Del) |
| |
620.1 | 65 | * Check out the release notes [[here>>doc:Main.Release Information.Portal.225 - Pop-up Party.WebHome||target="blank"]] |
| |
1.1 | 66 | * Start thinking about how the license tracker can aid your development |
| 67 | * Start thinking about major, minor, and patch | ||
| 68 | * Keep making great integrations | ||
| 69 | |||
| 70 | Let's stay in touch and till next time! | ||
| |
582.1 | 71 | |
| |
580.2 | 72 | {{info}} |
| 73 | ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] | ||
| |
574.46 | 74 | |
| |
580.2 | 75 | {{/info}} |
| |
254.1 | 76 | ))) |
| 77 | |||
| 78 | ((( | ||
| 79 | {{toc/}} | ||
| 80 | ))) | ||
| |
1.1 | 81 | {{/container}} |
| |
254.1 | 82 | {{/container}} |