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 06-SituationalDeployment1 +225 - TBD - Content
-
... ... @@ -1,45 +1,24 @@ 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!** In the last few weeks, we have done much work for the Deploy phase. On top of that, we have worked on several store functionalities. Next to this, we have several smaller feedback items from our hackathon efforts that are now released to you.6 +**Hi there, eMagiz developers!** 6 6 7 -== **Deployment Plan** == 8 8 9 -//__Improved deployment plan to make the process better and more predictable__// 10 -The algorithm for genarating a default deployment plan is improved to keep jms downtime and alerting to a minimum. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for aws and on-premises machines. 11 - 12 -//__Editing release properties__// 13 -With this release, it will be possible to change the description of a property by editing the property. 14 - 15 -//__JMS memory setting check__// 16 -A change in memory settings triggers redeployment of the container now. 17 - 18 -//__Properties tab__// 19 -We have removed the deprecated tab Properties in the Deploy phase. 20 - 21 -//__Cleanup old images__// 22 - 23 -== **Store Improvements** == 24 - 25 - 26 26 == **Feedback Items** == 10 +//__Alerting notification settings__// 11 +The Notification settings on the left menu of the Alerting tab in the Manage phase, have been moved to the Triggers page. This change has been made in preparation of an upcoming feature. 27 27 28 -//__Alerting manual pause__// 29 -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. 13 +[[image:Main.Images.Release Blog.WebHome@release-225-triggers.png]] 30 30 31 -//__ Orderingof graphsinManage__//32 - ThegraphsinManagearenoworderedaccordingtoimportance.Thismeans thatruntimestatisticsaresortedby "ProcessCPU usage" (highestfirst),queue statisticsare sorted by "Messagesin queue" (highest first), andHTTP statistics aresorted by "Unsuccessful requests" (highest first).15 +//__Process containers__// 16 +If a model does not have license for a pattern, the model contact now has the option to delete the process container of that given pattern. 33 33 34 -//__UTC times in Grafana panels__// 35 -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. 18 +== **Bug Fixes** == 36 36 37 -//__Update flow designer version__// 38 -The framework used in the flow designer has been updated to the latest version. 39 39 40 40 41 - 42 -== **Bug Fixes** == 43 43 44 44 45 45 == **Fancy Forum Answers** == ... ... @@ -46,9 +46,9 @@ 46 46 47 47 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: 48 48 49 -* [[ Gettingfilesfromsubfolders(FTP)>>https://my.emagiz.com/p/question/172825635703568575||target="blank"]]28 +* [[Preparing Image for <runtime> failed: Reached the number of attempt.>>https://my.emagiz.com/p/question/172825635703888610||target="blank"]] 50 50 51 -== **Key takeaways** ==30 +== **Key Takeaways** == 52 52 53 53 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: 54 54 ... ... @@ -56,10 +56,9 @@ 56 56 * If you have feedback or ideas for us, talk to the Platypus 57 57 * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these. 58 58 * Clear your browser cache (Ctrl + Shift + Del) 59 -* Check out the release notes [here] 38 +* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]] 60 60 * Start thinking about how the license tracker can aid your development 61 61 * Start thinking about major, minor, and patch 62 -* Upgrade to the latest build number 63 63 * Keep making great integrations 64 64 65 65 Let's stay in touch and till next time! ... ... @@ -67,6 +67,11 @@ 67 67 {{info}} 68 68 ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]] 69 69 70 -~*~* Indicates a next-generation-architecture only feature. 71 -{{/info}})))((({{toc/}}))){{/container}} 48 +{{/info}} 49 +))) 50 + 51 +((( 52 +{{toc/}} 53 +))) 72 72 {{/container}} 55 +{{/container}}