Introducing: Device Logs & Anedya ValueStore

This month has been very exciting at Anedya. We're thrilled to announce the launch of two exciting new features on the Anedya IoT cloud platform: Device Logs and ValueStore! 

Device Logs

Ever felt like your IoT devices operate in a black box? Debugging and diagnosing issues can be a frustrating endeavour, especially in the case of IoT devices. It is still easy during the development phase to see what's happening inside the device, but as IoT devices are deployed on the field the complexity increases. Today, the majority of IoT devices support Firmware updates, and debugging or diagnosing an issue happening at some remote device is a very big challenge.

We at Anedya, always strive to make the developer journey as smooth and easy as possible. Hence, introducing device logs in the Anedya Platform.

This service allows IoT devices to send logs to the platform, and you can view those logs in the Anedya Dashboard as well as through the API.

Device Logs support millisecond-level resolution and can be submitted by the devices one log at a time or in a batch of 100s. Each log entry can contain a maximum of 1000 characters. All logs are stored and are immediately available for the access through dashboard or API. The logs remain stored for 60 days.

Device Logs are available to all Anedya users without any additional cost! 

You can learn more about sending logs from your devices here

Anedya ValueStore

Anedya ValueStore is a managed key-value store service that allows users to tackle several problems with the management of fleets of devices. ValueStore is designed especially for IoT applications.

In ValueStore, keys are organized into namespaces, which act as containers for related data. Each namespace is configured with a scope, which can be either global or node. Global namespaces are designed for read-only access and are accessible to all devices within a project, as long as the namespace ID is known to the devices. This setup ensures that important data like variant-specific device configurations can be shared across the entire device fleet seamlessly.

On the other hand, node namespaces are more targeted, allowing data to be specific to individual devices identified by their unique Node ID. This level of granularity enables devices to access and manage their own set of key-value pairs independently, enhancing data privacy and device-specific functionalities. This can be used to manage device-specific data like calibration parameters as well as to get the attributes from the devices also like battery health.

Furthermore, ValueStore allows users total control over namespaces and their associated key-value data through Platform APIs.

To know more about Anedya ValueStore, refer to the documentation here.