Platform Update - Updatable Event Fields, Cloud Storage To/From Edge Device Files

Dylan Schuster
Dylan Schuster | 2 minute read

 

Today’s platform update covers improvements released this week and others rolled out in mid-December. These new features come almost entirely from user requests.

Changeable Event Properties

Losant’s Events feature has evolved considerably over time based on user feedback, and December’s release was our biggest change to the feature since adding direct device association and event tags back in 2019.

Now, users can edit several additional fields after creating an event, such as its subject; level (e.g. “critical” vs. “warning”); and associated device.

Also, changes to these properties over time are tracked in the event’s updates along with the previously tracked state changes (“new” vs. “acknowledged” vs. “resolved”). And while event tags were always editable after event creation, changes to tags are now also tracked in the updates as well.

Event Update Tracking

Finally, another user request we’ve fulfilled is the ability to create an event in an “acknowledged” or “resolved” state. This is helpful for tracking device anomalies that have already been accounted for but that you would like to record for posterity.

Edge Device Cloud Storage Syncing

In Gateway Edge Agent version 2.1.0, we’ve rolled out a number of changes that allow for syncing files stored on an edge compute device to/from our various cloud storage integrations …

S3 Write Config to Disk

These features allow for exchanging large configuration files, container logs, and captured images between the edge and third-party services – transactions that would have been impossible to achieve through a workflow execution previously due to payload size limits.

Other Updates

As always, this release comes with other features and improvements, including:

  • We’ve published a new base image of our Jupyter Notebook execution environment. The new image includes several Python packages requested by our users as well as upgrades to several other packages.
  • Event exports can now be formatted as either JSON or CSV, following similar changes in device exports. Similarly, event data can now be exposed to notebooks as either JSON or CSV format.
  • Endpoint Reply Nodes can now accept a payload path of topics to subscribe to in SSE stream reply types. This allows for building a dynamic list of topics to include in the stream per user request.

What’s Next?

With every new release, we listen to your feedback. By combining your suggestions with our roadmap, we can continue to improve the platform while maintaining its ease of use. Let us know what you think in the Losant Forums.