211 - Log Luminary
Hi there, eMagiz developers! In this release, we have done much work to improve our logging and overviews. This should improve the user experience for our platform. Next to this, we have done several minor changes and bug fixes, mainly relating to the Deploy and Manage phase.
Logging
Missing log entries
We improved crash handling so that log messages clearly show when and why a container failed to start.
Runtime logging
We fixed a bug where no new log messages were showing up, even though they were produced by a container.
Deployment execution error message
In some cases when a machine type step in the deployment plan execution errors, the portal may give an error when trying to display the error message. This has been fixed by now showing a generic error in the deployment plan and logging the full error in the Deploy history. The Deploy history will show a summary of the error and show the full error message in a new pop-up.
Overviews
Runtime overview
We added a new overview in the Deploy phase, called 'Runtime Overview', which shows the information of all runtimes on running machines.
Missing properties overview
The missing properties overview has been updated to show the runtimes and flow versions of missing property values.
Runtime restart or redeploy overview
Before executing the deployment plan to deploy machines, a pop-up will be shown with a list of the affected runtimes.
Feedback Items
Breaking changes pop-up
The risk level of pending changes is now shown in the pop up that appears after clicking 'Apply to environment'. The risk level is either medium or high.
External recipients emailaddress
The overview of external recipients has been updated. External recipients are now created on a model level, instead of comma separated list. This means that you can add them to your environment directly, like internal users.
Broker queue metrics dashboards
It is now possible to select the MQTT broker in the queue metrics dashboards.
Runtime image version
The version of runtime images used to prepare your containers for deployments will be the same across all environments. This holds for releases that are deployed and promoted to a next environment.
Bug Fixes
Message throughput
The message throughput graph in the Manage phase will now show the correct data, independent from the selected time internal. Before, this graph would not show any data in some cases.
Cloud template upgrade incorrect rollback
An issue has been fixed where a cloud template upgrade would be rolled back incorrectly due to failed runtime checks.
Next generation block
Apply to environment will now be blocked when trying to deploy Gen3 runtimes on a Gen2 model.
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:
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
- If you have feedback or ideas for us, talk to the Platypus
- Please inform us of new additions to the store (productmanagement@emagiz.com) so we can all benefit from these.
- Clear your browser cache (Ctrl + Shift + Del)
- Check out the release notes here
- Start thinking about how the license tracker can aid your development
- Start thinking about major, minor, and patch
- Keep making great integrations
Let's stay in touch and till next time!