Changes for page 235 - Last Log

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-207 - Aligned State
	1	+235 - Last Log

Content

...	...	@@ -1,46 +1,16 @@
1		-In the last sprint cycle, we focused on delivering state generation components. On top of that, we made several improvements regarding the alignment of components, and did some performance improvements and bug fixes. Moreover, we made a change in the metrics storage duration.
	1	+In this release, our new log alerting will be available! Please find out more about it **LINK**. Furthermore, we have implemented improvements for SMB and did some performance improvements. Lastly, from now on we no longer support our legacy Mendix connector (< version 4.x).
2	2
3		-Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.207 - Aligned State .WebHome||target="blank"]].
	3	+Please find out more on our [[Release blog>>Main.Release Information.Release Blogs.235 - Last Log||target="blank"]].
4	4
5		-=====New features=====
6		-* State generation: New state generation features have been added. Please check out [[V2.0.0>>https://docs.emagiz.com/bin/view/Main/Release%20Information/Runtime%20Images/V2.0.0/]] from the [[runtime images>>Main.Release Information.Runtime Images||target="blank"]] for more information.
	5	+====Minor changes====
	6	+* Manage - Alerting: We have added log message alert triggers to our new alerting stack for the [[current runtime>>doc:Main.eMagiz Academy.Fundamentals.fundamental-runtime-generation3||target="blank"]] architecture. This new feature allows you to trigger on all incoming log messages with an error log-level, or trigger for log messages with a specific log message and log level (info, warning or error) combination. Furthermore, you can specify the specific runtime the log message originated from as one of the filters as well. Please check out our [[release blog>>Main.Release Information.Release Blogs.235 - Last Log||target="blank"]] for the migration actions, and our new **ML LINK** about the design.
	7	+* Manage - Alerting: We have improved the visibility of titles of larger columns in the new Alerting page.
	8	+* Create - Flow Designer: Some configuration options have been added to our SMB connectors that will solidify the connections with a SMB share:
	9	+** It is now possible to add a local filter to the SMB inbound channel adapter.
	10	+** It is now possible to add a 'Request handler advice chain' to the SMB outbound channel adaptor, SMB outbound gateway, FTP outbound gateway and SFTP outbound gateway.
	11	+* All: We no longer support our legacy Mendix connector (< version 4.x).
7	7
8		-=====Minor changes=====
9		-
10		-* Design - Channels: Moving already attached channels in the flow designer has been made sligthly easier. (#845)
11		-* Create - Framework: The framework used in the flow designer has been updated, improving performance.
12		-* Deploy - Architecture: The description users see when adapting the topic retention size has been changed to be less confusing.
13		-* Deploy - Deployment plan: The algorithm for genarating a default deployment plan is improved to keep JMS downtime and alerting to a minimum. (#1009)
14		-* Deploy - Deployment plan: A change in the memory settings of a container triggers a redeployment of the container. (#993)
15		-* Deploy - Properties: We removed the deprecated tab Properties in the Deploy phase.
16		-* Deploy - Release properties: The description of a property can be changed by editing the property. (#1064)
17		-* Deploy - Release: The start/stop/restart machine deployment steps are now also executed correctly for AWS and on-premises machines.
18		-* Deploy - Release: When a release is removed, the related unused images in the on-premises machines will be removed as well.
19		-* Deploy - Release: Performance improvements have been implemented for loading releases in Deploy.
20		-* Manage - Alerting: If alerting has been paused manually, it will not be activated automatically after a release deployment. (#1024)
21		-* Manage - Alerting: Inactivated users should be removed from all alert settings (including “disabled“ settings) to avoid undesirable notifications.
22		-* Manage - Monitoring: Graphs showing problematic runtimes, queues and requests have been updated to be sorted by “Process CPU usage”, “Messages in queue” and “Unsuccessful requests” by default respectively for 3rd generation runtimes. (#1069)
23		-* Manage - Monitoring: The 3rd generation runtime dashboards have been changed to show data on UTC time zone by default. (#1070)
24		-* Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063)
25		-* Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.
26		-* Administration - My account: When changing a password, it is compared to a list of known database breaches for security. A warning is shown when the password is found in a database.
27		-
28		-
29		-
30	30	====Bug fixes====
31		-
32		-* Design - Store: 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.
33		-* Design - Store: We fixed an issue that the orders of message definition elements were changed after being imported.
34		-* Design - Store: We fixed an issue that importing a store item with synchronous message definitions went wrong. Now, the imported message definitions should be the same with the exported message definitions.
35		-* Design - Store: We fixed an issue that static copies were missing when importing store items. (#888)
36		-* Design - Store: Users who are not the model owner no longer see the eMagiz Store disclaimer popup, instead they see a popup containing a message. (#1027)
37		-* Create - Errors - We fixed an issue that, when migrating to Gen3, the error channel to “errorChannel” is only created for the first inbound in an entry flow.
38		-* Create - Styling: The styling of the left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.
39		-* Deploy - Cloud Template: An issue with disk performance in the last cloud template update has been resolved in this release. Please check out the cloud template [[release notes>>Main.Release Information.Cloud Templates||target="blank"]] for more information.
40		-* Manage - Monitoring: It is now possible to search on messages using partial search words in Manage Monitoring. For example, a search for Uptime can be done by searching for "up" "time" "ptim".
41		-
42		-
43		-
44		-=====Infra and image changes=====
45		-
46		-* Infra: New logging feature enabling us to make better choices in deprecating old encryption standards.
	14	+* Design - Flow Designer: The delete and download buttons in Resources have been re-aligned such that their positions are consistent when switching from view to edit mode. (#1381)
	15	+* Design - Flow Testing: The error that is sometimes thrown while switching between traces in flowtester is fixed. (#1521)
	16	+* Deploy - Releases: The performance of selecting a runtime when editing properties in Deploy has been improved. (#1124)