Hello,
One of the current limitations of STaaS is the lack of support for exporting trend data STaaS features | DataMiner Docs. Is this feature on the roadmap, or are there any recommended alternatives in the meantime? Swarming is not an alternative because it is only supported within the same cluster.
Could you advise on possible alternatives for the following scenarios, where I require a .dmimport file that includes trend data?
-
A DELT export from a STaaS-connected agent to be imported into a self-hosted DataMiner system.
-
A DELT export from a STaaS-connected agent to be imported into another cluster also connected to STaaS, how does this actually work? I assume alarms and trend data don't need to be included in the export, since that information is already stored in the shared STaaS database?
Hi Christine,
You're right, exporting trend data is not supported in STaaS.
Due to how the data is partitioned and stored in TableStorage, there’s currently no straightforward way to extract all trend data for a specific element. At this time, there are no plans to add support for this functionality.
As for the second scenario, the data does exist in the STaaS database but is tied to a cloud identity. This ensures that a cluster can only access its own data based on its identity. Currently, moving data between clusters with different cloud identities is not supported.
Kind regards,
I know it's not an alternative for your use case, but just wanted to add that exporting trend data from Cube in csv format is supported on STaaS.