The Platform Stream egress sink allows you to route messages from one stream to another stream within the same workspace, which is particularly useful for:
Multi-storage: Route messages to different streams with different storage configurations based on device characteristics (e.g., site ID, device ID) using a filter.
Different egress sinks for production and for testing devices.
To learn more read Platform Stream Egress Sink.
With this update, you can now configure Microsoft Entra ID authentication for a stream storage, Event Hub and Service Bus egress sinks. This way you don't have to specify connection strings but instead just assign required roles to the platform service principal, which is much more secure and convenient. This way of authentication is currently available only for dedicated instances.
When you enable this feature for the stream, the platform will not store any messages in stream storage, but will still deliver them to the configured egress sinks.
This can be useful in scenarios such as:
When you only need to process data in real time, without requiring long-term storage
When your egress sink already stores the messages, making additional storage redundant
When you want to reduce storage costs
To learn more read Storage Skipping.
We added the API endpoint for creating a secure WebSocket tunnel to a TCP port on a device.
This feature is disabled by default for security reasons, contact us to enable a specific set of ports in your workspace. You'll also need to allow remote access to the device in the interface of the Device SDK.
To better support non-interactive authentication to platform APIs, we have introduced service accounts and API keys.
For each workspace, one or more service accounts can be created and each service account can have one or more API keys with configurable expiration.
Service accounts can be assigned the same granular permissions & roles as users.
Currently, the service accounts and API keys can be managed via API:
We introduced comprehensive granular authorization capabilities for most platform assets. The well-known RBAC model is used that allows to define:
Details and overview of predefined roles can be found at Roles & Permissions page.
Currently, the role assignments can be managed via API:
It has always been possible to provide a custom storage account for a stream group to use instead of the default one provided by the platform. Now, you can assign a custom storage account to a specific stream as well.
This gives you more granular control over storage encryption, data residency, cost optimization, and other configurations.
To learn more go to Custom Storage Account.
When concatenation for the stream is enabled, the platform concatenates messages continuously at regular intervals, allowing you to read a batch blob even before it is fully completed.
Now you can adjust the regularity of this interval by setting max staleness on the stream.
To learn more go to Concatenation.
Spotflow IoT Platform now allows you to validate the payload of the messages sent by your devices before they are persisted in the storage. Based on the selected mode, the invalid message will either be discarded or marked with the validation outcome metadata. The message validation is configured at the stream level and supports JSON Schema of versions 2020-12, 2019-09, Draft 7, and Draft 6. To learn more go to Message Validation.
Support for this feature is also available in the API and CLI:
spotf stream create-or-update \
--name 'example-stream' \
--stream-group-name 'example-group' \
--with-validation Discard \
--validation-json-schema '{ "type": "number", "maximum": 30 }'
Apart from Text Lines and Open Telemetry schemas, we have added support for a plain Binary schema for Delta Egress.
This new schema is suitable for any kind of data. In addition to storing binary formats, it can also be used for JSON, XML, or any other format that can be serialized to bytes.
The schema can be configured at the egress route level and requires users to specify Content Type:
Support for this feature is also available in the API and CLI:
spotf stream egress-route create-or-update delta \
--name 'delta-route' \
--stream-group-name 'example-group' \
--stream-name 'example-stream' \
--egress-sink-name 'delta-sink' \
--schema 'Binary' \
--binary-schema-content-type 'application/json'
We created a custom package for Teltonika RUTX routers that contains a sample background service for sending telemetry to the Spotflow IoT Platform. The package greatly simplified the corresponding tutorial, because you no longer need to create and compile a custom Rust application just to test the basic telemetry sending functionality.
It is possible now to filter messages and batches that are routed to the egress sink by specifying a filter condition. The filter condition is a SQL-like expression, e.g. metadata.messageId = 'report' AND starts_with(metadata.deviceId, 'prod'). If the condition evaluates to true, the event is routed to the egress sink. Otherwise, the event is discarded.
Correspondingly, the CLI commands for creating and updating routes has been extended to support filtering:
spotf stream egress-route create-or-update sql \
--name "sql-route" \
--stream-group-name "example-group" \
--stream-name "example-stream" \
--egress-sink-name "postgresql-sink" \
--with-filter "metadata.messageId = 'report'"
Users of Delta Egress feature can now configure non-default table schema not only via HTTP API but also through the Portal and CLI.
Support in the Portal is integrated into the existing Egress Route creation and modification dialog:
Correspondingly, the CLI command for managing Delta Egress routes has been extended to support the table schema configuration:
spotf stream egress-route create-or-update delta \
--name 'delta-route' \
--stream-group-name 'example-group' \
--stream-name 'example-stream' \
--egress-sink-name 'delta-sink' \
--schema 'Otel' \
--otel-schema-logs 'true' \
--otel-schema-metrics 'true' \
--otel-schema-traces 'true'
Until now, user data routed through Delta Egress was constrained to textual row-based format and single, generic output Table Delta schema. Although this approach covered many original use cases of our customers, with the growing popularity of Databricks, new use cases appeared over time that were tedious or impossible to achieve.
To address these emerging use cases, we redesigned the Delta Egress to support new data formats and table schemas. At the same time, we added first-class support for processing Open Telemetry data in binary Protobuf format together with a new table schema tailor-made for Open Telemetry.
import pyspark
from delta.tables import *
spark = pyspark.sql.SparkSession.builder.appName("MyApp").getOrCreate()
table_uri = f"abfss://{container_name}@{storage_account_name}.dfs.core.windows.net/otel/traces"
df = spark.read.format("delta").load(table_uri)
rows = df.collect()
trace_id = rows[0]['otel_trace_id']
span_id = rows[0]['otel_span_id']
The new Open Telemetry table schema can be configured via API when creating a new Egress Route. Support in Portal and CLI is on the way.
If you use Teltonika RUTX routers, take a look at our new tutorial:
The tutorial shows how to create a custom Rust application that uses the Spotflow Device SDK and compile it for the router. You'll also see how to install the application on the router as a background service and visualize the telemetry data in the instance of Grafana integrated into the Spotflow IoT Platform.
The source code of the Device SDK is available on GitHub under the MIT license. The repository also contains the description of the architecture and the instructions for compilation and test execution.
We've simplified the configuration of data flows in the Spotflow IoT Platform. Now, the page shows a graphical representation of the data flow, making it easier to understand the data processing pipeline. That is, where the data flows for each stream. And conversely, where the data comes from for each egress sink.
Customers using SQL Egress can now write data to PostgreSQL columns of json and jsonb data types.
This update enables number of scenarios that were not possible before, such as storing any data types not supported natively by SQL Egress or storing data with eveloving schema.
No configuration changes are needed to start using this feature.
Spotflow customers can now manage OTEL Egress (OpenTelemetry) sinks and routes via spotf CLI,
along side the already existing support in Portal.
The newly available CLI commands are:
spotf egress-sink create-or-update otelspotf stream egress-route create-or-update otelspotf egress-sink create-or-update otel \
--name 'otel-sink' \
--endpoint 'https://otlp-gateway-prod-eu-west-3.grafana.net/otlp' \
--basic-auth-username 'user' \
--basic-auth-password 'password'
spotf stream egress-route create-or-update otel \
--name 'otel-route' \
--stream-group-name 'example-group' \
--stream-name 'example-stream' \
--egress-sink-name 'otel-sink' \
--log-labels 'deviceId:true'
We've added a new tutorial showing how to easily send data to delta tables (Databricks) using Spotflow IoT Platform. The tutorial also instruct you how to simply access the data in Databricks.
Sounds interesting? Give it a try right away!
You can now use the Rust interface of the Device SDK. Because the interface hasn't reached the version 1.0 yet, there might be minor breaking changes in the future. However, we don't plan to remove any existing functionality.
We'll be happy to hear your feedback on the new interface!
Spotflow customers can now manage Delta Egress sinks and routes via Portal and spotf CLI.
The newly available CLI commands are:
spotf egress-sink create-or-update delta azure-blobspotf stream egress-route create-or-update deltaspotf egress-sink create-or-update delta azure-blob \
--name 'delta-sink' \
--connection-string 'AccountName=...;AccountKey=...' \
--container-name 'tables'
spotf stream egress-route create-or-update delta \
--name 'delta-route' \
--stream-group-name 'example-group' \
--stream-name 'example-stream' \
--egress-sink-name 'delta-sink' \
--directory-path 'table/path'
We've added new tutorials showing how easy it is to send data to Azure EventHubs or observability backends using Spotflow IoT Platform. The tutorials also instruct you how to read the incoming data or visualize them, respectively.
Sounds interesting? Give it a try right away!
We've simplified the interface of Device SDK for Python and C:
Changes in version 2.0.0 of the Python interface:
DeviceClient.start now accepts all the options directly as arguments instead of using DeviceClientOptions.ProvisioningToken was replaced by a simple string.DeviceClient.send_message waits until the Device SDK sends the Message to the Platform.
We recommend using DeviceClient.enqueue_message for production scenarios because it doesn't block code execution during connection outages.Changes in version 2.0.0 of the C interface:
spotflow_client_options_create has changed to match the Python interface.spotflow_client_send_message waits until the Device SDK sends the Message to the Platform.
We recommend using spotflow_client_enqueue_message for production scenarios because it doesn't block code execution during connection outages.We've introduced a new interactive quickstart tutorial to improve the first interactions with the platform.
When each user signs up, we setup an initial workspace for them, so there are no obstacles to start using the platform. When the user lands in our Portal, they'll see a tutorial which guides the user through the initial steps within the platform:
Spotflow customers using Device Fleet Configurations to configure devices at scale can now modify the configuration's content or path.
This feature allows to edit configuration used by many devices without needing to delete and create a new configuration. Our goal with this update is to make it easy for customers to make iterative changes to large scale of devices even when running in production.
Please see Tutorial: Configure Multiple Devices if you want to start using Device Fleet Configurations.
We've completely redesigned our documentation to be more intuitive and focused on real-world use cases. Dive in to find clearer guides and more helpful examples tailored just for you!
Spotflow users can now delete devices directly through the command line interface (CLI).
This feature provides a quick and efficient way to delete devices without the need to access the portal.
To delete a device, you can use the spotf device delete command followed by the device's ID. Here's an example:
spotf device delete --device-id "<device_id>"
Please refer to the CLI command reference documentation for detailed instructions.
Data streams from devices can now be directly inserted into Delta Tables backed by Azure Blob Storage. This feature is provided as a new Egress Sink kind to which both new and existing streams can be routed.
The target Azure Blob Storage container is specified via connection string and container name. The Delta Table is created in the specified container, and the data is inserted into it. Optionally, a static prefix of the target path can be added.
The created Delta Table contains several predefined columns, such as stream_name, message_id or ingress_enqueued_date_time as well column payload_line with content of the stream message.
See detailed documentation in Delta Egress Sink page.
The new egress sink can be configured via API. Support in CLI and Portal is not yet available.
#!/usr/bin/env pwsh
$body = @{
properties = @{
config = @{
delta = @{
azureBlobStorage = @{
connectionString = "AccountName=...;AccountKey=..."
containerName = "delta"
}
}
}
}
}
$uri = "https://api.eu1.spotflow.io"
$uri += "/workspaces/$workspaceId"
$uri += "/egress-sinks/delta-example"
Invoke-WebRequest `
-Method Patch `
-Uri $uri `
-Headers @{ "Authorization" = "Bearer $token" } `
-ContentType "application/json" `
-Body ($body | ConvertTo-Json -Depth 10)
#!/usr/bin/env pwsh
$body = @{
properties = @{
egressSinkName = "delta-sink-sample"
config = @{
delta = @{
directoryPath = "sample-path"
}
}
}
}
$uri = "https://api.eu1.spotflow.io"
$uri += "/workspaces/$workspaceId"
$uri += "/stream-groups/$streamGroupName"
$uri += "/streams/$streamName"
$uri += "/egress-routes/delta-route-sample"
Invoke-WebRequest `
-Method Patch `
-Uri $uri `
-Headers @{ "Authorization" = "Bearer $token" } `
-ContentType "application/json" `
-Body ($body | ConvertTo-Json -Depth 10)
Product changelog has been started. Spotflow engineers and product managers will keep you informed about the latest updates and improvements via this page. Stay tuned!