Wiki source code of 183 - Rainbow World
Last modified by Carlijn Kokkeler on 2024/05/22 13:45
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
20.1 | 1 | Release that updates the manage statistics sections for our new monitoring stack. On top of that, we have released a new cloud template and released several other functionalities. |
| |
1.1 | 2 | |
| |
20.1 | 3 | Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.Rainbow World.WebHome||target="blank"]]. |
| |
4.1 | 4 | |
| |
29.1 | 5 | ====New features==== |
| |
20.1 | 6 | * Manage - Monitoring: For customers deploying flows on the next generation eMagiz runtime, a new interactive graphing widget is introduced, allowing users to easily zoom into graphs, filter graph content, view graphs over any time range and navigate to the detail view of a resource, runtime or queue. |
| |
25.1 | 7 | ** Manage - Monitoring - HTTP Statistics: For models with containers deployed on the next generation eMagiz runtime: |
| 8 | *** A new dashboard is introduced, providing an overview of failed and successful requests over all resources allowing users to identify problems more easily. | ||
| 9 | *** A detail view for resources is introduced to show requests per user, request methods, response status and response times. | ||
| 10 | *** API statistics has been renamed to HTTP statistics. | ||
| |
26.1 | 11 | ** Manage - Monitoring - Runtime statistics: For models with containers deployed on the next generation eMagiz runtime: |
| 12 | *** A new dashboard is introduced, providing an overview of memory and CPU usage of all runtimes allowing users to identify problematic runtimes more easily. | ||
| 13 | *** A detail view for runtimes is introduced to show memory usage, CPU usage, log events, threads, data measurements, as well as fifteen new graphs providing detailed JVM metrics. | ||
| 14 | ** Manage - Monitoring - Queue statistics: For models with containers deployed on the next generation eMagiz runtime: | ||
| 15 | *** A new dashboard is introduced, providing an overview of the messages in queue, as well as queue throughput over all queues users to identify problematic queues more easily. | ||
| 16 | *** A detail view for queues is introduced to show the total messages added to queue, messages in queue, message throughput, queue consumers, data measurements as well as fourteen new graphs providing detailed queue metrics. | ||
| |
23.1 | 17 | * Deploy - Cloud Templates: New Cloud Templates are available for single-lane environments to execute a maintenance update. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates.WebHome||target="blank"]] for more information. |
| 18 | * Create - Settings: Un-transfer specific event processors from Create. (#465) | ||
| |
24.1 | 19 | * Deploy - On-premises: Releases can be securely deployed for your on-premise installations when running on our next generation eMagiz architecture. |
| |
12.1 | 20 | |
| |
29.1 | 21 | ====Minor changes==== |
| |
20.1 | 22 | * Deploy: Flows for which have the current version is an auto-saved version won't be included into a release when executing "batch update" or "update flows to latest version". In turn the user will be notified which flows could not be updated automatically and should be checked manually. (#701) |
| 23 | * Deploy - Architecture: For runtimes on the new monitoring stack that run on-premises, volumes can be registered in order to persist data and/or to access the hosts file system. | ||
| 24 | * Store: The download counter will only be increased if the importing party is a normal user and not a system admin. | ||
| |
1.1 | 25 | |
| |
16.1 | 26 | ====Bug fixes==== |
| |
20.1 | 27 | * Deploy - Property: Selecting runtime when creating, editing or copying properties passes validation as expected. (#739) |
| 28 | * Manage - Log entries: We fixed a problem when you filter log entries by runtime name in the Manage phase. (#746) | ||
| 29 | * Create - Flow Designer: Going back and forth when exporting a flow fragment does not break exported resources anymore. | ||
| 30 | * Flow Designer - Store: It is now again possible to export a flow fragment to a store item which was previously exported from another flow. | ||
| 31 | * Design - Store: The chosen message format (XML/JSON/EDI) from the store item is imported correctly in your model. | ||
| |
16.1 | 32 |