diff --git a/trento/xml/article_sap_trento.xml b/trento/xml/article_sap_trento.xml index f49b9e39..e48edd22 100644 --- a/trento/xml/article_sap_trento.xml +++ b/trento/xml/article_sap_trento.xml @@ -2441,20 +2441,17 @@ In the Trento dashboard, go to the overview corresponding to the object for whic Any &suse; customer, with a registered &sles4sap; 15 (SP1 or higher) distribution, experiencing an issue with &trentopremium;, can report the problem either directly in the &scc; - or through the corresponding vendor, depending on their licensing model. Please report the problem under &sles4sap; 15 and component trento. + or through the corresponding vendor, depending on their licensing model. Problems must be reported under &sles4sap; 15 and component trento. - When opening a support case for Trento, provide the following information, which can be retrieved - as explained in section : + When opening a support case for Trento, provide the chosen deployment option for &t.server;: &K8s;, systemd or containerized. + In case of a &K8s; deployment, provide the output of the Trento support plugin and the scenario dump, as explained in section . + + In case of a systemd deployment, provide the status and the journal of the trento-web and trento-wanda services. + + In case of a containerized deployment, provide the logs of the trento-web and trento-wanda containers. Use docker ps to retrieve + the IDs of both containers, then docker logs CONTAINER_ID to retrieve the corresponding logs. - - - The output of the Trento support plugin. - - - Your scenario dump. - - For issues with a particular &t.agent;, or a component discovered by a particular &t.agent;, also provide the following: @@ -2482,8 +2479,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic
&t.server; - To analyze issues within the application, we have two tools at our - disposal. They both help us collect information/data that might be + There are two tools you can use to analyze issues with &t.server; in a &K8s; scenario. They both help us collect information/data that might be useful when troubleshooting/analyzing the issue.