Changes for page 234 - Alert Adventures

Last modified by Carlijn Kokkeler on 2024/11/18 15:29

From version 84.1

edited by Erik Bakker
on 2023/05/26 08:40

Change comment: There is no comment for this version

To version 83.1

edited by Erik Bakker
on 2023/05/22 15:20

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -9,8 +9,9 @@
  * Create - Flow designer: Added a validation for HTTP outbound gateways and HTTP outbound channel adapters that will create an alert if both Encoding mode and a REST template is set for the component.
  * Deploy - Releases: We improved the performance of preparing and deploying releases, by optimizing the algorithm that decides if runtime images needs to be rebuild or not.
  * Deploy - Releases: We improved resource validation when preparing releases. You will get notified when a flow resource was updated in one flow, but not in another flow in your release. Only applies to third generation runtimes.
--* Deploy - Architecture: When pressing "Apply to Environment" in Deploy -> Architecture there is no hard dependencies anymore on the (active) release when running in the next generation architecture. This makes it more clear and tangible what function is necessary for what goal.
++* Deploy - Architecture: You can apply your changes to environment without having an active release.
  * Manage - Alerting: Updated the eMagiz control tower with an improved way to determine whether metrics for a runtime are missing.
++(control tower, so Gen3 only)
  * General: Updated the monitoring stack so alerts can be paused, reducing the alerts that are received during eMagiz infra deployments.
  ====Bug fixes====