STaaS Troubleshooting #4105
STaaS Troubleshooting #4105
Conversation
There was a problem hiding this comment.
@robin-devos-skyline, as per your request via email, we’ve created a new "Troubleshooting - STaaS" page based on the Word document you provided. Could you please carefully review this pull request and go over my comments?
| > [!TIP] | ||
| > For more information, refer to [Skyline DataMiner Core InterAppCalls Range 1.0.1.1](xref:Skyline_DataMiner_Core_InterAppCalls_Range_1.0#1011). | ||
|
|
||
| DataMiner Systems may experience performance issues because of the high number of interactions when using SLNet Subscriptions for specific actions. In DataMiner 10.3.12, improvements were made to increase the efficiency of these interactions, with further enhancements added in DataMiner 10.4.6. |
There was a problem hiding this comment.
I'm not entirely sure if I interpreted the section above correctly. It was structured and worded differently in the original document, but I made some adjustments for the sake of clarity. Could you double-check if the content is still accurate, @robin-devos-skyline?
There was a problem hiding this comment.
@FalconeDanielle could you assist with the above?
There was a problem hiding this comment.
I would adjust lines 244-249 as follows:
"- If the DataMiner System uses many inter-element or inter-automation communication, then the usage of the InterApp framework is a good architectural choice.
If the DataMiner System experiences SLNet performance issues because of the large interactions when using SLNet Subscriptions. Make sure you have DataMiner v10.3.12/v10.4.6 or higher, as the efficiency of InterApp communication has improved greatly. This also directly impacts the interactions towards STaaS.
Tip
For more information, refer to Skyline DataMiner Core InterAppCalls Range 1.0.1.1."
Context: the InterApp class was introduced in v10.1, which used SLNet as a communication layer. As of v10.3.12/10.4.6, this communication layer has moved to a message broker. This also reduces the interactions towards STaaS (=extra load + extra costs)
(Note - I found the backbone of InterApp difficult to understand, as I could only find bits and pieces in the documentation, then link it to a specific use case)
No description provided.