MAMAS version 0.7.0 "early2"

• Status: obsoleted by MAMAS v.0.7.1
• Released at: 2023-01-15
• Supported modes of operation:
  • production: Yes
  • free usage: Yes (included, 15 seats, 2 webtunnel, expires 2023-03-10)
• Supported deployment modes:
  • DT SAAS / DT Cloud / DT Server Managed: Yes / No / Yes
  • Partner SAAS / Partner Cloud / Partner Server Managed: Yes / No / Yes
  • Customer self-managed: Yes
  • Private network: Yes
• Support planned: until 0.7.1 release
  • See release table
• Upgrade supported from:
  • manual - Feature version 0.6.0 (See release table)
  • manual - Patch version 0.6.1 (See release table)
• Target audience: early adopters
• Showcase video:
  • for news in MAMAS 0.7, see What's new in MAMAS 0.7
  • for general MAMAS functionality see Showcase for MAMAS 0.6.x

Release notes - known issues, changes since last release

Version 0.7.0 is a second feature version of MAMAS available to a wider public - all early adopters. This version brings mainly the Changes Tracker (Data Audit Log) and SW packages list for Advantech routers features. See more on below.

Known issues (updates with bugs being reported)

• Agent may not start after router HW crash or fast reboot / Advantech routers only
  • When reboot occurs unexpectedly (e.g. reboot by Watchdog), some of the agent date are not cleaned up from the FS. Also, if the reboot happens fast (normal reboot but it happens to go through faster than agent tidies up during stop operation), this could happen as well.
  • When new agent (after OS boot) receives the same PID as the agent that was running before reboot, the detection in the sense is there an agent running already ? misfires (it detects existing process with correct name because of the identical PID) and agent does not start after reboot
  • suprisingly, ICR OS assigns very similar and often identical PIDs to the same process, probably due to repetition of the (almost) same situation - probably due to low entropy. Result is that the chance of agent getting identical PID to the pre-boot agent is quite high.
  • status: fixed and released in MAMAS v.0.7.1

Changes since version 0.6.1 "early1 patch1"

• The Changes Tracker is a visual tool for inspecting changes on selected metrics of your devices. You can select device and/or a metric combined with a calendar time span to see changes over time. By sorting, you are also able to e.g. show the device with peak reported temperature among all devices or a peak value of one device. The number of supported metrics will grow further in future MAMAS versions.
• The data changes can be also exported in the form of text file as the Changes Tracker is just a parametrized view over the DCL (Data Change Log) functionality.
• Advantech routers now report the list of installed SW packages - called either User Modules or Router Apps based on which Firmware version are you running on the devices. In MAMAS 0.7.0, the list of all reported SW packages is accessible under SW Manager -> SW Packages and each devices shows a list of installed SW packages in Device Details. This functionality will grow into real SW package management (Uninstallation and Installation of SW packages on devices) in future MAMAS versions.
• The Firmware menu has been moved under SW Manager.
• The Global Status light is now updated automatically.
• When Firmware cannot be downloaded, the download attempts are issued less frequently. Also, a FW version that is not used by devices and impossible to download is removed on service restart.
• Alert configuration change handling has been improved. User configuration change for an alert is picked earlier, the evaluation is done faster after the update (and it is also more frequent in regular) and user is now able to completely delete any alert.