Older Release Notes

• Archived Release Notes (2022)
• v22.12.4 Release Notes
• v22.11.6 Release Notes
• v22.10.7 Release Notes
• v22.9.11 Release Notes
• v22.9.8 Release Notes
• v22.8.4 Release Notes
• v22.7.7 Release Notes
• v22.7.1 Release Notes

Archived Release Notes (2022)

v22.12.4 Release Notes

maiLink Agent Changes

File Pull from Device

The maiLink Agent software has been updated to incorporate the ability to transfer a file to the cloud upon a request from the cloud. That lets the user “pull” a file from the maiLink cloud portal. In order to use this feature, the user must specify the absolute path of the file that is to be pulled to the cloud.

maiLink Cloud Portal User Interface Changes

File Transfer

All file transfer functions have been reimagined under the Devices > {device} > File Transfers lefthand tab. You will now see two top tabs under the File Transfers heading: Send to Device, and Pull from Device.

The user interface now has an Uploaded Files table that shows a list of the files that have been either pulled from the device to the cloud, or pushed by the device to the cloud (via the Agent REST API).

Send to Device. This functionality has not change from prior releases, although the user interface has changed. The user selects a file on their local file system, which is then transferred to the cloud. Then it is transferred down to the device.

Pull from Device. The user “pulls” a file from the maiLink cloud portal. The user must specify the absolute path of the file that is to be pulled to the cloud.

Device Location and Maps

Location. Each device can now be associated with a street address. That address is used to derive a latitude and longitude for the location. Furthermore, you can embellish the address with building, floor, and suite reference information, but realize that the additional information may not influence the latitue and longitude. The following examples will all create the same latitude and longitude:

• 1111 Constitution Avenue Northwest, Washington, District of Columbia, DC
• 1111 Constitution Avenue Northwest, Washington, District of Columbia, DC, Building 13
• 1111 Constitution Avenue Northwest, Washington, District of Columbia, DC, Suite 103
• 1111 Constitution Avenue Northwest, Washington, District of Columbia, DC, Bldg 7, Suite 24

There are several ways to enter the address:

• For a new device, add the address in the device entry area.
• For an existing device, add the address by editing the device.
• When mass importing devices from a CSV file, you can incorporate the address into the CSV file (see below, and How to Import Devices).

Mass Import of Devices

maiLink now support mass import of devices through our technical support team. Our documentation pages contain information (see How to Import Devices) on how to create a CSV file that is compatible with our mass import capability. If you have any questions, please reach out to support@maidata.io.

v22.11.6 Release Notes

maiLink Agent Changes

Telemetry Events

The maiLink Agent software has been updated to transmit telemetry event data to the cloud. As in prior maiLink Agent releases, the telemetry event data can still be logged to a file on the device by setting the log.level in mailink-agent-plugin.yml to trace.

Telemetry Status

The maiLink Agent software has been updated to transmit telemetry status data to the cloud. As in prior maiLink Agent releases, the telemetry status data can still be logged to a file on the device by setting the log.level in mailink-agent-plugin.yml to trace.

Built-In System Telemetry

Prior releases of maiLink Agent included built-in system telemetry that transmitted CPU and memory utilization data to the cloud. This has now been greatly extended to include the following:

Control. By default, your device does not transmit all of the above information to the cloud. However, starting in this release you can enable any of the above items for automated transmission. To enable the items, edit mailink-agent-plugin.yml and add any or all of the following data items below. Note that you can easily disable any of them at any time by setting enabled:false.

Note: In a future release, controls over the enabling/disabling of built-in system telemetry will be moved to the Device Type controls in the cloud.

telemetry:
  metric:
    partition:
      free_bytes:
        enabled: true
      used_bytes:
        enabled: true
      used_percent:
        enabled: true
    memory:
      used_bytes:
        enabled: true
      used_percent:
        enabled: true
      free_bytes:
        enabled: true
    cpu:
      used_percent:
        enabled: true
  status:
    os:
      enabled: true
    system:
      boot_time:
        enabled: true
      up_time:
        enabled: true
    cpu:
      cpus:
        enabled: true
      cores:
        enabled: true
      vendor_id:
        enabled: true
      model_name:
        enabled: true
      frequency:
        enabled: true
    partition:
      device:
        enabled: true
      mountpoint:
        enabled: true
      fstype:
        enabled: true
      total_bytes:
        enabled: true
    memory:
      total_bytes:
        enabled: true
    interface:
      name:
        enabled: true
      mac_address:
        enabled: true
      ip_addresses:
        enabled: true

maiLink Metrics Explorer Changes

The maiLink web port has been updated to reflect the telemetry changes described above.

Display of Telemetry Status Data

Telemetry status information is now displayed in the user interface at Devices > [Device] > About [Device] > System Status. The data displayed here includes both any enabled built-in system telemetry status data as well as all the custom telemetry status data that your system is transmitting to the cloud.

Note: The data displayed is the most recent status value received for each of the status parameters.

Display of Telemetry Events Data

Telemetry events are now displayed as a graphical overlay in the metrics explorer as vertical dashed lines.

Note: Individual events cannot be enabled or disabled at this time.

Display of Built-In System Telemetry Metric Data

Built-in system telemetry data that is sent as metrics (dynamic numeric data) can be selected for graphical display by clicking on the Add Query button in the metrics explorer found at Devices > [Device] > About [Device] > Metrics Explorer.

v22.10.7 Release Notes

maiLink Agent Changes

File Push REST API

The maiLink Agent software REST API has been extended to include a new endpoint that allows the Agent to push a file to the Cloud. This can be performed programatically by the Device’s applications software, or can be performed from the command line with a simple Curl instruction.

Files transferred can be of any size. The Agent divides very large files in the sections to better ensure completion of file transfers in the event of connectivity interrupts; transfer will continue if connection is re-established after a connectivity interruption.

The REST API is documented at link.

The JSON message passed to the REST API at localhost:5465 contains the complete path for the file to be uploaded and the destination path in the cloud relative to the storage bucket:

{
    "path": "/Users/maidata/files/upload_this.txt",
    "destinationPath": "configs/config.txt"
}

Users can access the uploaded files through a table in the maiLink web portal at

Devices > [Device] > File Transfers > Uploaded Files

v22.9.11 Release Notes

maiLink Agent Changes

One-Click Agent Update

The maiLink Agent software architechture has changed so that it supports Agent self-update. To do this, the Agent has been divided into two parts: mailink-agent is a watchdog that runs continuously as a daemon or service; mailink-agent-plugin is a binary that runs at the behest of mailink-agent. When an update is performed, mailink-agent-plugin gets replaced.

Should an update fail, the Agent will revert to using the version of mailink-agent-plugin that was running just prior to initiation of the update.

Configuration File

The maiLink Agent plugin has a new configuration file, written in YAML. That is where you can configure the behavior of the Agent, most specifically for logging.

Windows. On Windows devices the configuration file is found at:

C:\Program Files\maiLink\agent\mailink-agent-plugin.yml

with the following default contents:

log.level: "info" # or debug / trace
log.file: C:\Program Files\maiLink\agent\mailink-agent-plugin.log

Linux. On Linux devices the configuration file is found at:

/etc/mailink/mailink-agent-plugin.yml

with the following default contents:

log.level: "info" # or debug / trace
log.file: /var/log/mailink/mailink-agent-plugin.log

Logging

The Agent plugin logs run-time information about the Agent plugin. For users, this is most useful for monitoring REST API activity for Telemetry stub-outs. The Agent plugin will only log telemetry messages received by the REST API if the log level is set to “trace” in the YAML configuration file.

This release fixes a bug that prevented mailink-agent from creating its log file.

v22.9.8 Release Notes

maiLink Agent Changes

One-Click Agent Update

This release is identical to v22.9.9 except for the version number. It is provided to allow testing of one-click Agent update so you have to working versions you can switch between. v22.9.8 and v22.9.9 are functionally equivalent.

For details on new functionality and changes introduced in v22.9.8/v22.9.9, see Release Notes

v22.8.4 Release Notes

Telemetry: Metrics

The REST API in the maiLink Agent now transmits “metric” type Telemetry messages to the Cloud. Those messages are recorded in the maiLink Telemetry Cloud database. Each metric is a named value where the name connotes the concept with unit (when applicable) and the value is a numeric value.

For example:

    {
        "type": "metric",
        "label": "pressure__mmHg",
        "value": 13.3
    },

Telemetry Time-Series Display

With this release you can display telemetry time-series plots. A new Dashboard block called “Metrics Explorer” is available on each Device page. To support this, several new pages of Metrics documentation have been added (see below).

Note that in a future release we plan to move this capability to the Device Type. It will be available in the Device page only for users with the correct permissions.

Built-in System Metrics

The maiLink Agent has been updated to automatically include host computer and operating system metrics as Telemetry “event” data sent to the Cloud. Two metrics have been created:

cpu_util        # CPU % used
mem_util        # Memory % used

Built-in System Metrics are available via queries in the Metrics Explorer.

File Transfer

maiLink now supports file transfer from the service specialist’s computer to an Agent in the field. The user selects a file on the local computer to transmit. The file is deposited into this directory:

C:\Program Files\maiLink\agent\file_transfers\

The source file is not removed.

Audit Logging

maiLink now has a comprehensive Audit Log trail that you can review. Find under Settings > Audit Logs.

Documentation

Documentation is available at Docs or by clicking on the Support tab in the top bar in the Cloud.

Release Notes

A section that contains release notes has been added. In this area you can find information about the most recent release of maiLink SRM software modules. In the future you will also be able to find historical release notes about prior software versions.

Telemetry API Specification

The Telemetry API interface specification has been updated to reflect the final syntax for Event and Status telemetry messages.

Metrics Documentation

Several new pages of documentation to help users learn about the PromQL query language used in the Metrics Explorer on the Device page. The pages are (in the order of most basic to most complex):

• Metrics Explorer
• Query Basics
• Query Examples
• Query Functions
• Query Operations

In addition, a new page has been added with coding samples that will generate telemetry Metrics data for you to play with:

• Experiment with Telemetry

v22.7.7 Release Notes

Telemetry Stub-out

Two new telemetry types are supported in the Agent REST API. Messages with type “events” and “status” will now be accepted. The results of calls to the REST API are documented in the Agent logfile:

C:\Program Files\maiLink\agent\mailink-agent.log

In order to log the telemetry calls, set MAILINK_LOG_LEVEL to “trace”:

C:\Program Files\maiLink\Agent\mailink-agent.cfg

  MAILINK_DEVICE_KEY_FILE=C:\Program Files\maiLink\agent\agent.jwt
  MAILINK_LOG_LEVEL=trace
  MAILINK_LOG_FILE=C:\Program Files\maiLink\agent\mailink-agent.log

After changing the log level, restart the maiLink Agent service.

v22.7.1 Release Notes

Client Connection Indicator

The user interface reflects whether the device is connected by showing a green dot in the menu bar at the top of the app.maidata.io user interface.