Dear Dojo Community,
In a DMA with a regular Cassandra and ElasticSearch DB, a user can define a protocol to an element where data is offloaded via a logger table of type DirectConnection.
An example of such a table is added below.
Then with an SLNet-call an alias can be assigned to a certain combination of tablename and columndatabasename. This is the SLNet-call that can be used in an automation script.
In the specific use case of the example before the variable "customDatabaseNameInProtocol" should be "CentralErrorDB", while the "offloadedTableNameInProtocol" should equal "ErrorLogsTable". Alias name can be chosen freely, but in this example we chose "MAMErrorMessages" which will be used later on.
And via Dashboards, a GQI Query of type "get parameter by alias" is then a powerful way of fetching this data to appear in a dashboard or even aggregate it to CSV files via the DataMiner Data Aggregator.
Will this "get parameter by alias"-mechanism also work when the DMS is working with STaaS instead of a combination of a Cassandra and ElasticSearch Database?
The SetAliassesRequest is part of the SLSearch API which is currently not supported when using STaaS.
If you would be interested in this functionality, please let us know so we can adjust our priorities accordingly.