2012-11-04 - Bosch IoT Thing - service update
Our latest service release comes with various changes:
New filter for lifecycle events
In case your business application needs to receive lifecycle events (e.g. thing created, thing deleted) you can activate a filter in your managed connections (and WebSockets) to get only those events forwarded automatically by Bosch IoT Things.
Of course, you can still be notified about ALL thing updates, if you don’t apply any restrictions.
New support of RQL-based filter for live messages
This new features helps to filter live messages based on information in the digital twin, and thus also helps to reduce traffic. Using the RQL filter, it is now also possible to subscribe only for specific message subjects, which allows a more fine-grained control of which subscriber handles which messages.
The RQL filter is applied to the “enriched” information pulled from the persistent digital twin.
The easiest way to configure such a RQL filter for live message targets is the Connections UI. Of course, the HTTP API has been enhanced accordingly.
Search index changes
The Namespace UI offers the possibility to re-configure the set of fields, which need to be indexed for search. With this service update we will activate the pricing model for search-updates and re-indexing. The same is valid if you request the respective HTTP API resources.
You can now decide to index a smaller set of thing attributes or feature properties, if your business application will not search for some fields, and thus save traffic and costs on both sides of the service.
Note: While updating the search index, your search results may be incorrect. Please wait some time before your next search. The costs will be charged in conformance with our pricing model.
Hub-to-Things connection changes
We are happy to announce that with this latest update we can soon offer Apache Kafka based connections between the device connectivity layer (Bosch IoT Hub) and the digital twin layer (Bosch IoT Things) of the Device Management service.
All new connections which will be created automatically after November 8th, 2021 (all new subscriptions) will use Kafka.
For the migration of the standard plans of all customers, we will proceed as announced via Email.
“We are going to perform these changes without any downtime and no activities to be done on the customer side.”
Migration activities on the production system are scheduled to start November, 15th, 2021.
For using the Bosch IoT Thing HTTP API documentation, the authorization options “Bosch-ID” as well as “API-Key” have been removed.
The API Token was deprecated since June 2020, now it’s time to delete it.
The Bosch-ID authorization itself will be available for other resources.
We recommend to use the Suite OAuth approach.
Throttling in connection metrics
The Connections UI, in particular the Metrics tab, now visualizes occurrences when an AMQP or Kafka-based connection cannot keep up with the actual message rate.
The number represents the amount of minute-intervals where the consumption was close to the limit, or was exceeding the expected number of messages per client.
This helps identifying situations, where messages queue up and in the worst case may be dropped.
Such warnings indicate that it might be necessary to scale out the connection by increasing the number of used clients.
At this occasion, various minor bugs have also been fixed.