What's Changed
AI Empowered
With a 6.0.0 release we made a big step into fully AI empower the dynamic mapper. With this pre-release we introduce a capability to auto-generate substitutions either for graphical mappings or JavaScript mappings with just a single click.
To use it, you need to have:
the AI Agent Manager deployed to your tenant (currently in private preview - reach out to your c8y contact),
an AI model subscription & API key and
optional the latest C8Y MCP Server deployed to your tenant.
Check the updated Installation Guide for more details.
Afterwards you just need to (re-)deploy the 6.0.0 Dynamic Mapper microservice and it will configure / create all AI Agents automatically and enable the feature to be useable within the UI.
We tested a lot of templates with a very good output, but there might be always templates where the AI agents won't generate what you are probably expecting. Therefore this feature should be considered as preview and might be changed and improved in final & upcoming releases.
Feedback: Please share your feedback so we can improve the AI agents.
See related issue #350 #360 #361
Microservice Pre-builds
Before the 6.0.0 release we only provided one microservices with 0.5 CPUs + 2 GB RAM hard-coded in the manifest. This is working for most starting use cases to play around with dynamic mapper and up to 625 messages per seconds. For more performance we are now providing 4 builds with different CPU + Memory configuration. Here are all 4 pre-builds:
- Starter - Uses 0.5 CPUs and 2 GB RAM, suitable for up to 625 messages per second to be processed.
- Standard - Uses 2 CPU and 4 GB RAM, suitable for up to 2500 messages per second to be processed.
- Performance - Uses 8 CPU and 8 GB RAM, suitable for up to 10.000 messages per second to be processed.
- Max - Uses 16 CPU and 16 GB RAM, suitable for up to 20.000 messages per second to be processed.
To avoid costs we would ask you to start with Starter trying out the Dynamic Mapper. You can easily switch by just replacing the archive with one of the other 4 options later.
See related issue #349
Responsive UI
The UI has been improved to act more responsive on small screens. In previous versions we had cases that buttons / tool bars disappeared out of screen due to the fixed size of elements. This should be resolved now. #358
Other Changes
- We renamed Filter Mapping to Filter execution mapping making more clear that this filter defines if a mapping is executed or not. #354
- The limitation to only use one wildcard in topic for outbound mappings has been removed. Before change it was only possible to use something like this device/+/temp. Now it is also supported to use this device/+/+ which allows more dynamic mappings but more comprehensive mapping logic of course #357
- Make source payload editable in test UI to dynamically test different payloads #359
- We removed "c8y_IsDevice" fragment from Dynamic Mapper Managed Object to avoid unintended deletion. #362
- Shrinked the UI archive from 20Mb+ to ~11 MB now.
Full Changelog: v5.5.0...v6.0.0-pre