Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updates to the Reporting a Problem and Problem Analysis Sections #191

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 9 additions & 13 deletions trento/xml/article_sap_trento.xml
Original file line number Diff line number Diff line change
Expand Up @@ -2441,20 +2441,17 @@ In the Trento dashboard, go to the overview corresponding to the object for whic
<para>
Any &suse; customer, with a registered &sles4sap;&nbsp;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;&nbsp;15 and component trento.
or through the corresponding vendor, depending on their licensing model. Problems must be reported under &sles4sap;&nbsp;15 and component trento.
</para>
<para>
When opening a support case for Trento, provide the following information, which can be retrieved
as explained in section <xref linkend="sec-trento-problemanalysis" />:
When opening a support case for Trento, provide the chosen deployment option for &t.server;: &K8s;, systemd or containerized.</para>
<para>In case of a &K8s; deployment, provide the output of the Trento support plugin and the scenario dump, as explained in section <xref linkend="sec-trento-problemanalysis" />.
</para>
<para>In case of a systemd deployment, provide the status and the journal of the trento-web and trento-wanda services.
</para>
<para>In case of a containerized deployment, provide the logs of the trento-web and trento-wanda containers. Use <command>docker ps</command> to retrieve
the IDs of both containers, then <command>docker logs <replaceable>CONTAINER_ID</replaceable> to retrieve the corresponding logs.
</para>
<itemizedlist>
<listitem>
<para>The output of the Trento support plugin.</para>
</listitem>
<listitem>
<para>Your scenario dump.</para>
</listitem>
</itemizedlist>
<para>
For issues with a particular &t.agent;, or a component discovered by a particular &t.agent;, also provide the following:
</para>
Expand Down Expand Up @@ -2482,8 +2479,7 @@ In the Trento dashboard, go to the overview corresponding to the object for whic

<section>
<title>&t.server;</title>
<para>To analyze issues within the application, we have two tools at our
disposal. They both help us collect information/data that might be
<para>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.</para>

<section>
Expand Down
Loading