Changes for page 226 - Alerting Alchemy

Last modified by CarlijnKokkeler on 2024/07/30 16:40

From 179.1 to 180.1 From 603.1 to 604.1

From version 180.1

edited by CarlijnKokkeler
on 2023/10/12 14:08

Change comment: There is no comment for this version

To version 603.1

edited by Erik Bakker
on 2024/07/16 14:38

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--206 - Situational Deployment
++225 - Pop-up Party

Author

@@ -1,1 +1,1 @@
--XWiki.CarlijnKokkeler
++XWiki.ebakker

Content

@@ -1,114 +1,81 @@
  {{container}}
--{{container layoutStyle="columns"}}(((
++{{container layoutStyle="columns"}}
++(((
  [[image:Main.Images.Release Blog.WebHome@release-blog-intro.png]]
--**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.
++**Hi there, eMagiz developers!** In this release, a new runtime image (LINK) will be available, including changes to our infinispan cache manager, SMB inbound channel adapter, and heap memory configuration. Moreover, we have made progress on our alerting improvement plans and have improved and added several pop-up screens. Find out all we released below!
--== **Release Date Change** ==
--As of release 208, released on November 9th, 2023, we will change our release date to Thursday morning starting at 05:00 AM CET (3:00 UTC). We opted for this change as it allows us to control better and manage our releases to uphold the quality standards you have gotten used to from us. Should you have any questions, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]].
--
--== **Deployment Plan** ==
--
--//__Improved deployment plan to make the process better and more predictable__//
--The algorithm for generating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. When stopping a machine, the JMS server is now stopped first, and when executing the deployment plan, the JMS server is deployed first. This way, the JMS server is troubled minimally. Next to this, the start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
--
--//__Editing release properties__//
--With this release, it will be possible to change the description of a property by editing the property.
--
--//__Container memory settings__//
--A change in memory settings triggers redeployment of the container now.
--
--//__Properties tab__//
--We have removed the deprecated tab Properties in the Deploy phase.
--
--//__Cleanup old images__//
--When a release is removed, the related unused images in the on-premises machines will be removed as well.
--
--//__Performance improvements for loading releases__//
--Performance improvements have been implemented for loading releases in Deploy. Releases should now load faster than before. All functionality should remain exactly the same as before.
--
--== **Store Improvements** ==
--
--//__Message definition elements order__//
--We fixed an issue that the order of message definition elements was changed after being imported.
--
--//__Importing a store item with synchronous message definitions__//
--We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should correspond with the exported message definitions.
--
--//__Importing store items containing static copies__//
--We fixed an issue that store items were missing static copies. Now, store items with static copies are imported correctly.
--
--//__Importing store content__//
--We fixed an issue that blocked you from importing Store content in the Design phase. The message definitions and message mappings are now imported correctly as the original content in the item of the Store.
--
--//__Store disclaimer__//
--Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message that states that the model owner should accept the disclaimer.
--
  == **Feedback Items** ==
++//__Alerting notification settings__//
--//__Alerting manual pause__//
--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.
++//__Process containers__//
++If a model does not have a license for a pattern, the model contact now has the option to delete the process container of that given pattern.
--//__Ordering of graphs in Manage__//
--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).
++//__Design settings__//
++When pressing Apply settings in Design Settings, a confirmation screen will now be shown to present the changes that will be taken into effect for each environment.
--//__UTC times in Grafana panels__//
--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.
++[[image:Main.Images.Release Blog.WebHome@release-225-design-settings.png]]
--//__Update flow designer version__//
--The framework used in the flow designer has been updated to the latest version.
++//__Untested images__//
++ A warning will be shown when a release is activated on production with a new runtime image version which has not been tested on acceptance before.
++
++[[image:Main.Images.Release Blog.WebHome@release-225-image-warning.png]]
--//__Carwash track TLS versions in logging__//
--A new logging feature will be released, enabling us to make better choices in deprecating old encryption standards.
++//__Infinispan Cache Manager__//
++We added support for the Infinispan Cache Manager to perform clustering through JGroups' GossipRouter. For this, a new runtime image LINK is available.
++
++//__Infinispan Cache Manager error message__//
++We improved the error message when configuring an Infinispan Cache Manager with ‘TCP-ping’ transport type, when the list of peer hosts are passed in invalid format. For this, a new runtime image LINK is available.
--//__Moving channels in the flow designer__//
--Moving already attached channels in the flow designer has been made sligthly easier.
++//__Flow bump__//
++When bumping a new version of the flows that are using a resource, you can specify which version type you want to create, Major, Minor or Patch version. You can also give more information in a description.
++
++[[image:Main.Images.Release Blog.WebHome@release-225-resources-update.png]]
--//__Topic sizes description change__//
--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.
++//__Unused support objects__//
++Support objects are now shown in two sections, namely 'Support objects' and 'Unused support objects'.
--//__Password change notification__//
--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.
++[[image:Main.Images.Release Blog.WebHome@release-225-unused-support-object.png]]
++
++//__Deleting routes__//
++For clarity purposes, a confirmation pop-up will be shown when deleting routes.
--//__Password comparison__//
--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.
++[[image:Main.Images.Release Blog.WebHome@release-225-routes.png]]
--//__Inactive user alerting__//
--Inactivated users are now removed from all alert settings (included “disabled“ settings) to avoid undesirable notifications.
--
--//__Alphabetical sorting on user level in HTTP statistics__//
--Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive.
--
--//__SOAP Web services path__//
--Developers with Admin rights are now able to edit the 'SOAP Web services path' in the SSL settings.
--
++//__Debug queue__//
++The 'Open debug queue' button in the queue browser enables the user to directly open the debug queue when it exists instead of having to search for it.
++
++[[image:Main.Images.Release Blog.WebHome@release-225-open-debug-queue.png]]
++
  == **Bug Fixes** ==
++//__Internal server error__//
++The internal server error pop-up is not received anymore when moving to Create in a model which has an Event Streaming license but is not using it.
--//__Flow designer styling__//
--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.
++//__Namespace update__//
++Editing a namespace used in a message definition automatically updates the message definition & transformations.
--//__Partial search for messages__//
--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".
++//__Error pop-up__//
++We fixed an issue where a pop-up was shown with an incorrect error while editing the message mapping of a synchronous flows.
--//__Disk usage after cloud template update__//
--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.
++//__SMB inbound channel adapter__//
++The SMB inbound channel adapter failed to retrieve files when the remote directory pointed to a path with multiple directories in it, unless they were seperated with '}}' instead of '{{/'. This has been resolved, meaning that remote directories that contain multiple folders in its path can (and should) contain '/' again. For this, a new runtime image LINK is available.
--//__Error handling migration__//
--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.
++//__Heap memory__//
++The initial committed heap memory of runtimes has been lowered to better match actual usage. For this, a new runtime image LINK is available.
++//__Classpath conflicts__//
++We updated transitive runtime dependencies to prevent potential conflicts on the classpath for extended images.
++
  == **Fancy Forum Answers** ==
  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:
--* [[JSON Web Tokens (JWT authentication)>>https://my.emagiz.com/p/question/172825635703606919||target="blank"]]
--* [[Determining container sizes & reading architecture pages>>https://my.emagiz.com/p/question/172825635703594204||target="blank"]]
--* [[SFTP connectivity - supported algorithms>>https://my.emagiz.com/p/question/172825635703607141||target="blank"]]
--* [[Deploy property release results in missing flows in runtime>>https://my.emagiz.com/p/question/172825635703607354||target="blank"]]
--* [[MessageDeliveryException: Dispatcher has no subscribers>>https://my.emagiz.com/p/question/172825635703619797||target="blank"]]
++* [[Transaction failed and has been rolled back>>https://my.emagiz.com/p/question/172825635703888662||target="blank"]]
++* [[How to calculate HMAC-SHA1 signature for webhook verification>>https://my.emagiz.com/p/question/172825635703888844||target="blank"]]
++* [[How can you convert an json array to xml with the new approach?>>https://my.emagiz.com/p/question/172825635700357885||target="blank"]]
++== **Key Takeaways** ==
--== **Key takeaways** ==
--
  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:
  * If you have questions surrounding our Program Increment Planning, please get in touch with [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
@@ -115,10 +115,9 @@
  * If you have feedback or ideas for us, talk to the Platypus
  * Please inform us of new additions to the store ([[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]) so we can all benefit from these.
  * Clear your browser cache (Ctrl + Shift + Del)
--* Check out the release notes [here]
++* Check out the release notes [[here>>doc:Main.Release Information.Portal.224 - Summer Sonata.WebHome||target="blank"]]
  * Start thinking about how the license tracker can aid your development
  * Start thinking about major, minor, and patch
--* Upgrade to the latest build number
  * Keep making great integrations
  Let's stay in touch and till next time!
@@ -126,6 +126,11 @@
  {{info}}
  ~* Indicates a Beta feature. If you would like to get access to this beta feature, please contact [[productmanagement@emagiz.com>>mailto:academy@emagiz.com]]
--~*~* Indicates a next-generation-architecture only feature.
--{{/info}})))((({{toc/}}))){{/container}}
++{{/info}}
++)))
++
++(((
++{{toc/}}
++)))
  {{/container}}
++{{/container}}

Changes for page 226 - Alerting Alchemy

Summary

Details

Navigation