From bf315b1090e11b543cfea9c7d32c379e877059b8 Mon Sep 17 00:00:00 2001 From: Eliska Romanova Date: Wed, 16 Sep 2026 11:52:41 +0200 Subject: [PATCH 1/6] Liz: user documentation --- .../modules/user-guide/nav_user_guide.adoc | 3 +- trento/adoc/product-attributes.adoc | 1 + trento/adoc/trento-guide.adoc | 1 + trento/adoc/trento-liz-ai-assistant.adoc | 99 +++++++++++++++++++ 4 files changed, 103 insertions(+), 1 deletion(-) create mode 100644 trento/adoc/trento-liz-ai-assistant.adoc diff --git a/trento-docs-site/modules/user-guide/nav_user_guide.adoc b/trento-docs-site/modules/user-guide/nav_user_guide.adoc index 0fedb283..a86ebeb9 100644 --- a/trento-docs-site/modules/user-guide/nav_user_guide.adoc +++ b/trento-docs-site/modules/user-guide/nav_user_guide.adoc @@ -18,6 +18,7 @@ *** xref:trento-mcp-install.adoc[Installing Trento MCP Server] *** xref:trento-mcp-config.adoc[Configuring Trento MCP Server] *** xref:trento-mcp-how-to-use.adoc[Using the Trento MCP Server] + ** xref:trento-liz-ai-assistant.adoc[Liz AI assistant in Trento Web] ** xref:trento-core-features.adoc[Core Features] *** xref:trento-user-manage.adoc[User management] *** xref:trento-sso-integration.adoc[Single Sign-On integration] @@ -29,7 +30,7 @@ ** xref::trento-compliance-features.adoc[Compliance Features] *** xref:trento-checks.adoc[Performing configuration checks] *** xref:trento-checks-customization.adoc[Checks Customization] - ** xref:trento-web-console.adoc[Using Trento Web] + ** xref:trento-web-console.adoc[Monitoring SAP health in the Trento Web console] ** xref:trento-smlm-integration.adoc[Integration with SUSE Multi-Linux Manager] ** xref:trento-operations.adoc[Operations] ** xref:trento-report-issue.adoc[Reporting an issue] diff --git a/trento/adoc/product-attributes.adoc b/trento/adoc/product-attributes.adoc index a8bd71e2..d329f19e 100644 --- a/trento/adoc/product-attributes.adoc +++ b/trento/adoc/product-attributes.adoc @@ -24,6 +24,7 @@ :tr_mcp_health_port: 8080 :tr_mcp_health_api_path: /api/healthz :mcp_host: MCPHost +:liz: Liz // PROJECT REPOSITORY URL :repo-url: https://github.com/SUSE/doc-[PRODUCT] diff --git a/trento/adoc/trento-guide.adoc b/trento/adoc/trento-guide.adoc index d812906c..f8daae45 100644 --- a/trento/adoc/trento-guide.adoc +++ b/trento/adoc/trento-guide.adoc @@ -12,6 +12,7 @@ include::trento-update.adoc[] include::trento-uninstall.adoc[] include::trento-integration-prometheus.adoc[] include::trento-mcp-integration.adoc[] +include::trento-liz-ai-assistant.adoc[] include::trento-core-features.adoc[] include::trento-compliance-features.adoc[] include::trento-web-console.adoc[] diff --git a/trento/adoc/trento-liz-ai-assistant.adoc b/trento/adoc/trento-liz-ai-assistant.adoc new file mode 100644 index 00000000..4406cb61 --- /dev/null +++ b/trento/adoc/trento-liz-ai-assistant.adoc @@ -0,0 +1,99 @@ +include::product-attributes.adoc[] + +[[sec-trento-liz-ai-assistant]] +== {liz} AI assistant in {tr_web} +:revdate: 2026-09-16 + +{liz} is a chat-based AI assistant built directly into {tr_web}. It lets you ask questions about your SAP landscape in natural language. By analyzing the live state of your systems and best-practice validations, {liz} helps you actively monitor health and troubleshoot issues, all without requiring any additional deployment. + +[[sec-about-liz]] +=== About the {liz} AI assistant + +Unlike the {tr_mcp}, which is an optional component you install separately to connect external AI tools to {trento}, {liz} is part of {tr_web} itself. You only need to supply an API key for a supported large language model (LLM) provider. + +[[sec-liz-providers]] +==== Which providers and models are supported + +{liz} AI assistant currently supports the following LLM providers: + +* Anthropic Claude +* Google Gemini +* OpenAI GPT + +Each provider offers several models. To ensure compatibility, {liz} only displays models capable of powering the assistant. + +[[sec-liz-data-access]] +==== How does {liz} access data + +{liz} answers using the same tools the {tr_mcp} exposes: live SAP landscape state from {tr_web}, and check results from {tr_wanda}. + +Access is bound to your {trento} user account. When you open a chat session, {liz} can only access data you are authorized to see. Your existing {trento} roles and permissions remain unchanged. + +[[sec-liz-limitations]] +==== What are {liz}'s current limitations + +In the current release, {liz} does not offer the following capabilities: + +* Keeping conversation history or resuming previous threads. Conversation state is held in memory only. Closing the session discards it, and you cannot resume an earlier conversation. +* Using the page you are viewing as context. You must state what you are asking about. +* Searching documentation or knowledge bases. +* Logging conversations to the Activity Log. Only AI settings changes are logged. + +[[sec-configuring-liz]] +=== Configuring {liz} + +You can configure {liz} from your user profile in {tr_web}. + +Requirements: + +* A user account in {tr_web}. AI configuration is per user and each user configures their own provider and model. +* An API key for one of the supported providers. + +To configure {liz}: + +[.procedure] +. In the {tr_web} console, click your user icon and select *Profile* to open your profile page. + +. Go to the *AI Configuration* section and click *Edit Settings*. + +. Select a provider and model from the supported list. + +. Enter your API key for the chosen provider. + +. Click *Save* to save your configuration. + +{liz} becomes available as soon as the configuration is saved. + +[NOTE] +==== +You can change your model or provider at any time from the *Profile* page. Changes +apply to an active conversation immediately without the need to reload the web console. +==== + +To stop using {liz}, clear your AI configuration from the *Profile* page. The chat launcher is disabled after the configuration is removed. + +[[sec-using-liz]] +=== Using {liz} + +Open the chat launcher in {tr_web} and type your question. Your chat session remains active as long as you are logged into the {tr_web} console. + +*Example queries:* + +* _What is the status of the HANA database clusters?_ +* _Which hosts are failing and why?_ +* _Why is the Pacemaker cluster in a critical state, and how can I troubleshoot it?_ + +If you did not configure a provider and model, the launcher is disabled. See <> for more information. + +[WARNING] +==== +Clicking *New chat* in {liz} immediately ends the active conversation and clears its history. Previous chats cannot be recovered once a new session starts. +==== + + + + + + + + From 8b0eb8dd44a78f8e99ff8744ed29f27225279188 Mon Sep 17 00:00:00 2001 From: Eliska Romanova Date: Thu, 17 Sep 2026 09:19:33 +0200 Subject: [PATCH 2/6] Review comments --- trento/adoc/trento-liz-ai-assistant.adoc | 44 ++++++++++++++++-------- 1 file changed, 29 insertions(+), 15 deletions(-) diff --git a/trento/adoc/trento-liz-ai-assistant.adoc b/trento/adoc/trento-liz-ai-assistant.adoc index 4406cb61..c170ee53 100644 --- a/trento/adoc/trento-liz-ai-assistant.adoc +++ b/trento/adoc/trento-liz-ai-assistant.adoc @@ -2,15 +2,23 @@ include::product-attributes.adoc[] [[sec-trento-liz-ai-assistant]] == {liz} AI assistant in {tr_web} -:revdate: 2026-09-16 +:revdate: 2026-09-17 -{liz} is a chat-based AI assistant built directly into {tr_web}. It lets you ask questions about your SAP landscape in natural language. By analyzing the live state of your systems and best-practice validations, {liz} helps you actively monitor health and troubleshoot issues, all without requiring any additional deployment. +{liz} is a chat-based AI assistant built directly into {tr_web}. It lets you ask questions about your SAP landscape in natural language. By analyzing the live state of your systems and best-practice validations, {liz} helps you actively monitor health and identify issues, all without requiring any additional deployment. [[sec-about-liz]] === About the {liz} AI assistant Unlike the {tr_mcp}, which is an optional component you install separately to connect external AI tools to {trento}, {liz} is part of {tr_web} itself. You only need to supply an API key for a supported large language model (LLM) provider. +{liz} is guided by built-in system instructions tailored for {trento}, ensuring it understands your SAP landscape right out of the box. + +[IMPORTANT] +.Data privacy +==== +{liz} sends your prompts and the system data needed to answer them to the third-party LLM provider you configure. Review your organization's data handling policy before enabling this feature.. +==== + [[sec-liz-providers]] ==== Which providers and models are supported @@ -29,16 +37,6 @@ Each provider offers several models. To ensure compatibility, {liz} only display Access is bound to your {trento} user account. When you open a chat session, {liz} can only access data you are authorized to see. Your existing {trento} roles and permissions remain unchanged. -[[sec-liz-limitations]] -==== What are {liz}'s current limitations - -In the current release, {liz} does not offer the following capabilities: - -* Keeping conversation history or resuming previous threads. Conversation state is held in memory only. Closing the session discards it, and you cannot resume an earlier conversation. -* Using the page you are viewing as context. You must state what you are asking about. -* Searching documentation or knowledge bases. -* Logging conversations to the Activity Log. Only AI settings changes are logged. - [[sec-configuring-liz]] === Configuring {liz} @@ -79,12 +77,28 @@ Open the chat launcher in {tr_web} and type your question. Your chat session rem *Example queries:* -* _What is the status of the HANA database clusters?_ -* _Which hosts are failing and why?_ -* _Why is the Pacemaker cluster in a critical state, and how can I troubleshoot it?_ +* _What is the tuning status of the registered hosts?_ +* _Which hosts are affected by patch XYZ?_ +* _Provide a summary of checks not passing for cluster XYZ and step-by-step remediation instructions._ If you did not configure a provider and model, the launcher is disabled. See <> for more information. +While a conversation is open you can perform the following actions: + +[cols="1,7", options="header"] +|=== +| Action | Description +| *Stop* +| Stop {liz} processing the current question. The assistant stays available for your next question. +| *Retry* +| Re-send your last prompt. +| *Copy* +| Copy a reply to the clipboard. {liz} formats its responses in Markdown, so pasting into compatible tools (like wikis or issue trackers) preserves the text formatting. +|=== + +Selecting **Learn more** in the assistant opens the {trento} documentation in a new +browser tab. + [WARNING] ==== Clicking *New chat* in {liz} immediately ends the active conversation and clears its history. Previous chats cannot be recovered once a new session starts. From 78c6ae787e7ce843b7629659ac9db4806ca2d3c3 Mon Sep 17 00:00:00 2001 From: Eliska Romanova Date: Fri, 18 Sep 2026 10:17:38 +0200 Subject: [PATCH 3/6] Review comments and restructuring --- .../modules/user-guide/nav_user_guide.adoc | 8 ++-- .../adoc/partials/mcp-host-prerequisites.adoc | 5 +- trento/adoc/trento-ai-integrations.adoc | 11 +++++ trento/adoc/trento-guide.adoc | 3 +- trento/adoc/trento-liz-ai-assistant.adoc | 47 ++++++++++-------- trento/adoc/trento-mcp-config.adoc | 48 +++++++++---------- trento/adoc/trento-mcp-host-others.adoc | 40 ++++++++-------- trento/adoc/trento-mcp-host-sles.adoc | 18 +++---- trento/adoc/trento-mcp-how-to-use.adoc | 4 +- .../adoc/trento-mcp-install-kubernetes.adoc | 47 ++++++++---------- trento/adoc/trento-mcp-install-systemd.adoc | 10 ++-- trento/adoc/trento-mcp-install.adoc | 6 +-- trento/adoc/trento-mcp-integration.adoc | 14 ++++-- 13 files changed, 137 insertions(+), 124 deletions(-) create mode 100644 trento/adoc/trento-ai-integrations.adoc diff --git a/trento-docs-site/modules/user-guide/nav_user_guide.adoc b/trento-docs-site/modules/user-guide/nav_user_guide.adoc index a86ebeb9..5c2011fe 100644 --- a/trento-docs-site/modules/user-guide/nav_user_guide.adoc +++ b/trento-docs-site/modules/user-guide/nav_user_guide.adoc @@ -14,11 +14,9 @@ *** xref:trento-uninstall-trento-server.adoc[Uninstalling Trento Server] *** xref:trento-uninstall-trento-agent.adoc[Uninstalling a Trento Agent] ** xref:trento-integration-prometheus.adoc[Prometheus integration] - ** xref:trento-mcp-integration.adoc[MCP Integration] - *** xref:trento-mcp-install.adoc[Installing Trento MCP Server] - *** xref:trento-mcp-config.adoc[Configuring Trento MCP Server] - *** xref:trento-mcp-how-to-use.adoc[Using the Trento MCP Server] - ** xref:trento-liz-ai-assistant.adoc[Liz AI assistant in Trento Web] + ** xref:trento-ai-integrations.adoc[Trento AI integrations] + *** xref:trento-liz-ai-assistant.adoc[Liz AI assistant in Trento Web] + *** xref:trento-mcp-integration.adoc[MCP Integration] ** xref:trento-core-features.adoc[Core Features] *** xref:trento-user-manage.adoc[User management] *** xref:trento-sso-integration.adoc[Single Sign-On integration] diff --git a/trento/adoc/partials/mcp-host-prerequisites.adoc b/trento/adoc/partials/mcp-host-prerequisites.adoc index ec900ce3..604adfed 100644 --- a/trento/adoc/partials/mcp-host-prerequisites.adoc +++ b/trento/adoc/partials/mcp-host-prerequisites.adoc @@ -1,7 +1,4 @@ -include::../product-attributes.adoc[] - -:revdate: 2026-01-08 -===== Prerequisites +:revdate: 2026-09-18 * An LLM provider and credentials. ** Public hosted options, such as Google Gemini, OpenAI, etc. diff --git a/trento/adoc/trento-ai-integrations.adoc b/trento/adoc/trento-ai-integrations.adoc new file mode 100644 index 00000000..8afd9377 --- /dev/null +++ b/trento/adoc/trento-ai-integrations.adoc @@ -0,0 +1,11 @@ +// Show third-level headings in the "Contents" box on the documentation site +include::product-attributes.adoc[] + +[[trento-ai-integrations]] +== {trento} AI integrations +:revdate: 2026-09-18 + +{trento} provides AI-driven capabilities to help you monitor and troubleshoot your SAP landscape using natural language. You can use these features directly within the web console, or connect {trento} data to your own external AI tools. + +include::trento-liz-ai-assistant.adoc[] +include::trento-mcp-integration.adoc[] diff --git a/trento/adoc/trento-guide.adoc b/trento/adoc/trento-guide.adoc index f8daae45..05317027 100644 --- a/trento/adoc/trento-guide.adoc +++ b/trento/adoc/trento-guide.adoc @@ -11,8 +11,7 @@ include::trento-installation.adoc[] include::trento-update.adoc[] include::trento-uninstall.adoc[] include::trento-integration-prometheus.adoc[] -include::trento-mcp-integration.adoc[] -include::trento-liz-ai-assistant.adoc[] +include::trento-ai-integrations.adoc[] include::trento-core-features.adoc[] include::trento-compliance-features.adoc[] include::trento-web-console.adoc[] diff --git a/trento/adoc/trento-liz-ai-assistant.adoc b/trento/adoc/trento-liz-ai-assistant.adoc index c170ee53..a10512eb 100644 --- a/trento/adoc/trento-liz-ai-assistant.adoc +++ b/trento/adoc/trento-liz-ai-assistant.adoc @@ -1,51 +1,59 @@ include::product-attributes.adoc[] [[sec-trento-liz-ai-assistant]] -== {liz} AI assistant in {tr_web} -:revdate: 2026-09-17 +=== {liz} AI assistant in {tr_web} +:revdate: 2026-09-18 {liz} is a chat-based AI assistant built directly into {tr_web}. It lets you ask questions about your SAP landscape in natural language. By analyzing the live state of your systems and best-practice validations, {liz} helps you actively monitor health and identify issues, all without requiring any additional deployment. +This section covers the following topics: + +* <> +* <> +* <> + [[sec-about-liz]] -=== About the {liz} AI assistant +==== About the {liz} AI assistant -Unlike the {tr_mcp}, which is an optional component you install separately to connect external AI tools to {trento}, {liz} is part of {tr_web} itself. You only need to supply an API key for a supported large language model (LLM) provider. +{liz} is part of {tr_web} itself and requires no additional deployment. You only need to supply an API key for a <>. {liz} is guided by built-in system instructions tailored for {trento}, ensuring it understands your SAP landscape right out of the box. [IMPORTANT] .Data privacy ==== -{liz} sends your prompts and the system data needed to answer them to the third-party LLM provider you configure. Review your organization's data handling policy before enabling this feature.. +{liz} sends your prompts and the system data needed to answer them to the third-party LLM provider you configure. Review your organization's data handling policy before enabling this feature. ==== [[sec-liz-providers]] -==== Which providers and models are supported - +Which providers and models are supported?:: ++ {liz} AI assistant currently supports the following LLM providers: - ++ +-- * Anthropic Claude * Google Gemini * OpenAI GPT - +-- ++ Each provider offers several models. To ensure compatibility, {liz} only displays models capable of powering the assistant. [[sec-liz-data-access]] -==== How does {liz} access data - -{liz} answers using the same tools the {tr_mcp} exposes: live SAP landscape state from {tr_web}, and check results from {tr_wanda}. - +How does {liz} access data?:: ++ +{liz} answers queries using live SAP landscape state from {tr_web}, and check results from {tr_wanda}. ++ Access is bound to your {trento} user account. When you open a chat session, {liz} can only access data you are authorized to see. Your existing {trento} roles and permissions remain unchanged. [[sec-configuring-liz]] -=== Configuring {liz} +==== Configuring {liz} You can configure {liz} from your user profile in {tr_web}. -Requirements: +*Requirements:* * A user account in {tr_web}. AI configuration is per user and each user configures their own provider and model. -* An API key for one of the supported providers. +* An API key for one of the <>. To configure {liz}: @@ -64,14 +72,13 @@ To configure {liz}: [NOTE] ==== -You can change your model or provider at any time from the *Profile* page. Changes -apply to an active conversation immediately without the need to reload the web console. +You can change your model or provider at any time from the *Profile* page without the need to reload the web console. Changes apply starting with your next prompt; any prompt currently processing finishes using the previous configuration. ==== -To stop using {liz}, clear your AI configuration from the *Profile* page. The chat launcher is disabled after the configuration is removed. +To stop using {liz}, clear your AI configuration from the *Profile* page. If the chat window is open, {liz} goes offline and the conversation becomes read-only. Once the window is closed, the chat launcher is disabled. [[sec-using-liz]] -=== Using {liz} +==== Using {liz} Open the chat launcher in {tr_web} and type your question. Your chat session remains active as long as you are logged into the {tr_web} console. diff --git a/trento/adoc/trento-mcp-config.adoc b/trento/adoc/trento-mcp-config.adoc index 03d257de..3c8195bc 100644 --- a/trento/adoc/trento-mcp-config.adoc +++ b/trento/adoc/trento-mcp-config.adoc @@ -1,8 +1,8 @@ include::product-attributes.adoc[] [[sec-trento-mcp-config]] -=== Configuring {tr_mcp} -:revdate: 2026-01-08 +==== Configuring {tr_mcp} +:revdate: 2026-09-18 This section provides an overview of how to configure the {tr_mcp} depending on the deployment method. @@ -10,9 +10,9 @@ This section provides an overview of how to configure the {tr_mcp} depending on * <> [[sec-trento-mcp-kubernetes-config]] -==== Configuration in a {k8s} deployment +===== Configuration in a {k8s} deployment -===== Configuration Sources +====== Configuration Sources The {tr_mcp} supports multiple configuration sources with the following priority order (highest to lowest): @@ -20,7 +20,7 @@ The {tr_mcp} supports multiple configuration sources with the following priority 2. **Built-in defaults** - Fallback values. [[sec-trento-mcp-kubernetes-config-sources]] -===== Configuration Overview +====== Configuration Overview [width="100%",options="header"] |=== @@ -79,7 +79,7 @@ The {tr_mcp} supports multiple configuration sources with the following priority |Log level: `debug`, `info`, `warning`, or `error`. |=== -===== {k8s} Deployment Example +====== {k8s} Deployment Example [source,yaml,subs="attributes"] ---- @@ -113,17 +113,17 @@ spec: [[sec-trento-mcp-systemd-config]] -==== Configuration in an systemd deployment +===== Configuration in an systemd deployment [[sec-trento-mcp-systemd-config-sources]] -===== Configuration Sources +====== Configuration Sources The {tr_mcp} supports multiple configuration sources with the following priority order (highest to lowest): 1. **Command-line flags** - Override config for the current process. 2. **Configuration file** - Persistent settings configuration. -===== Configuration Overview +====== Configuration Overview The `{tr_mcp_binary}` binary accepts several command-line flags to configure its behavior. The following table lists all available configuration options, their corresponding flags, configuration variables, and default values. @@ -197,7 +197,7 @@ The `{tr_mcp_binary}` binary accepts several command-line flags to configure its |Log level: `debug`, `info`, `warning`, or `error`. |=== -===== Configure {tr_mcp} with Command-Line Flags +====== Configure {tr_mcp} with Command-Line Flags {tr_mcp} allows you to override configuration settings using command-line flags for temporary changes. These overrides are not persistent and are lost when the process stops or the system is rebooted. To make configuration changes permanent for the systemd service, update `{tr_mcp_config_file}` and restart the service. @@ -230,7 +230,7 @@ Enable health checks on a custom port: ---- [[sec-trento-mcp-help-validation]] -===== Help and Validation +====== Help and Validation You can see all available flags by running: @@ -242,7 +242,7 @@ You can see all available flags by running: The server will validate the configuration on startup and log any issues with debug verbosity enabled. [[sec-trento-mcp-health-checks]] -==== Health Check Configuration +===== Health Check Configuration The {tr_mcp} includes built-in health check endpoints for systemd and {k8s} integration. @@ -251,7 +251,7 @@ The {tr_mcp} includes built-in health check endpoints for systemd and {k8s} inte Health check functionality is disabled by default and must be explicitly enabled using the `--enable-health-check` flag or the `TRENTO_MCP_ENABLE_HEALTH_CHECK` environment variable. ==== -===== Health Check Endpoints +====== Health Check Endpoints The health check server provides the following endpoints: @@ -264,7 +264,7 @@ The readiness endpoint performs comprehensive health checks, including: * `api-server` - Verifies connectivity to the configured {trento} API server. [[sec-trento-mcp-k3s-health-helm]] -===== Enable Health Checks with {helm} on a {k8s} deployment +====== Enable Health Checks with {helm} on a {k8s} deployment Enable health checks when deploying on {k8s} with {helm}: @@ -289,7 +289,7 @@ kubectl port-forward --namespace NAMESPACE \ ---- With the port forward active, test the endpoints in <>. -===== Enable Health Checks with the command-line for systemd deployment +====== Enable Health Checks with the command-line for systemd deployment [source,console,subs="attributes"] ---- @@ -302,7 +302,7 @@ With the port forward active, test the endpoints in <> or <> for details. diff --git a/trento/adoc/trento-mcp-install-kubernetes.adoc b/trento/adoc/trento-mcp-install-kubernetes.adoc index 6664099f..ef77e155 100644 --- a/trento/adoc/trento-mcp-install-kubernetes.adoc +++ b/trento/adoc/trento-mcp-install-kubernetes.adoc @@ -1,13 +1,12 @@ include::product-attributes.adoc[] - [[sec-trento-mcp-server-k8s]] -==== {k8s} deployment of {tr_mcp} -:revdate: 2026-01-08 +===== {k8s} deployment of {tr_mcp} +:revdate: 2026-09-18 include::partials/kubernetes-placeholders.adoc[] -===== Enable the {tr_mcp} +====== Enable the {tr_mcp} When installing {trserver} following the instructions in <>, the {tr_mcp} is disabled by default. Enable it by passing `--set trento-mcp-server.enabled=true`: @@ -23,7 +22,7 @@ helm upgrade --install trento-server oci://registry.suse.com/trento/trento-serve The {tr_mcp} will automatically connect to the {tr_web} and {tr_wanda} internal services within the {k8s} cluster. -===== Verify the {tr_mcp} installation +====== Verify the {tr_mcp} installation . Check that the {tr_mcp} Pod is running: + @@ -82,21 +81,16 @@ Example output: {"status":"up","details":{"mcp-server":{"status":"up","timestamp":"2025-10-09T12:11:09.528898849Z"},"wanda-api":{"status":"up","timestamp":"2025-10-09T12:11:09.544855047Z"},"web-api":{"status":"up","timestamp":"2025-10-09T12:11:09.544855047Z"}}} ---- -===== {tr_mcp} {helm} configuration options +====== {tr_mcp} {helm} configuration options The {tr_mcp} {helm} chart supports various configuration options: -* <> -* <> -* <> -* <> - [[mcp-customize-ingress-path]] -====== Customize Ingress Path - +Customize Ingress Path:: ++ By default, ingress is enabled. To customize the ingress configuration in a basic K3s installation, run the command below: - ++ ==== [source,bash,subs="attributes"] ---- @@ -109,14 +103,14 @@ helm upgrade --install trento-server oci://registry.suse.com/trento/trento-serve --set trento-mcp-server.ingress.hosts[0].paths[0].pathType=ImplementationSpecific ---- ==== - ++ The {tr_mcp} endpoint will be: `\https://TRENTO_SERVER_HOSTNAME{tr_mcp_ingress_path}/mcp` [[mcp-adjust-log-verbosity]] -====== Adjust Log Verbosity - +Adjust Log Verbosity:: ++ The default log level is `info`. Adjust it for debugging: - ++ ==== [source,bash] ---- @@ -129,10 +123,10 @@ helm upgrade --install trento-server oci://registry.suse.com/trento/trento-serve ==== [[mcp-adjust-resource-limits]] -====== Adjust Resource Limits - +Adjust Resource Limits:: ++ For production deployments with different resource requirements: - ++ ==== [source,bash] ---- @@ -147,11 +141,11 @@ helm upgrade --install trento-server oci://registry.suse.com/trento/trento-serve ---- ==== -[[mcp-disabling-health-check-probes]] -====== Disabling Health Check Probes - +[[mcp-disable-health-check-probes]] +Disable Health Check Probes:: ++ Health check probes are enabled by default. To disable them if needed, run the following command: - ++ ==== [source,bash] ---- @@ -164,8 +158,7 @@ helm upgrade --install trento-server oci://registry.suse.com/trento/trento-serve ---- ==== - -===== Complete configuration example +====== Complete configuration example Below is a complete example that configures external access via a custom ingress path: diff --git a/trento/adoc/trento-mcp-install-systemd.adoc b/trento/adoc/trento-mcp-install-systemd.adoc index 0a9ec30a..bb2dd49e 100644 --- a/trento/adoc/trento-mcp-install-systemd.adoc +++ b/trento/adoc/trento-mcp-install-systemd.adoc @@ -1,15 +1,15 @@ include::product-attributes.adoc[] [[sec-trento-mcp-server-systemd]] -:revdate: 2026-01-08 -==== systemd deployment +===== systemd deployment +:revdate: 2026-09-18 A systemd-based installation of the {tr_mcp} using RPM packages can be performed manually on the latest supported versions of {sles4sap}. include::partials/supported-versions.adoc[] [[mcp-systemd-install-rpm]] -===== Installing {tr_mcp} using RPM packages +====== Installing {tr_mcp} using RPM packages * Install the {tr_mcp} package: + @@ -19,7 +19,7 @@ zypper install {tr_mcp_binary} ---- [[mcp-systemd-configure]] -===== Configure {tr_mcp} +====== Configure {tr_mcp} . Create the {tr_mcp} configuration file `{tr_mcp_config_file}` by copying the example: + @@ -84,7 +84,7 @@ systemctl enable --now {tr_mcp_binary} ---- [[mcp-systemd-verify]] -===== Verify the {tr_mcp} service +====== Verify the {tr_mcp} service . Verify the service is running: + diff --git a/trento/adoc/trento-mcp-install.adoc b/trento/adoc/trento-mcp-install.adoc index b460f309..8dff144a 100644 --- a/trento/adoc/trento-mcp-install.adoc +++ b/trento/adoc/trento-mcp-install.adoc @@ -1,8 +1,8 @@ include::product-attributes.adoc[] [[sec-trento-mcp-install]] -:revdate: 2026-01-08 -=== Installing {tr_mcp} +==== Installing {tr_mcp} +:revdate: 2026-09-18 The {tr_mcp} can be deployed in different ways depending on your infrastructure and requirements. @@ -11,7 +11,7 @@ Supported installation methods: * <> * <> -==== Prerequisites {tr_mcp} +===== Prerequisites {tr_mcp} The {tr_mcp} is lightweight and stateless. No persistent storage is required; allocate space for logs as per your logging policy. Before installing the {tr_mcp}, both {tr_web} and {tr_wanda} components must be running and be accessible for the {tr_mcp} to function properly. diff --git a/trento/adoc/trento-mcp-integration.adoc b/trento/adoc/trento-mcp-integration.adoc index 809b147e..3ba6877a 100644 --- a/trento/adoc/trento-mcp-integration.adoc +++ b/trento/adoc/trento-mcp-integration.adoc @@ -1,10 +1,18 @@ include::product-attributes.adoc[] [[sec-trento-mcp-integration]] -:revdate: 2026-01-08 -== MCP Integration +=== MCP Integration +:revdate: 2026-09-18 -The {tr_mcp} is an optional component that enables AI-assisted infrastructure management for your SAP landscape. It exposes {trento} functionality through the Model Context Protocol (MCP), an open standard that facilitates secure communication between data sources and AI agents. While the core {trserver} operates independently, the {tr_mcp} component allows you to integrate {trento} into an agentic AI workflow. This enables the use of Large Language Models (LLMs) to perform common monitoring and troubleshooting tasks using natural language, providing a standardized way for AI tools to access real-time system state and best-practice validations. +While {trento} provides the built-in {liz} assistant for AI conversations directly inside the {tr_web} console, you can also integrate {trento}'s data into your own external AI tools and workflows. The {tr_mcp} is an optional component that enables this external AI-assisted infrastructure management for your SAP landscape. + +{tr_mcp} exposes {trento} functionality through the Model Context Protocol (MCP), an open standard that facilitates secure communication between data sources and AI agents. While the core {trserver} operates independently, the {tr_mcp} component allows you to integrate {trento} into an agentic AI workflow. This enables the use of Large Language Models (LLMs) to perform common monitoring and troubleshooting tasks using natural language, providing a standardized way for AI tools to access real-time system state and best-practice validations. + +This section covers the following topics: + +* <> +* <> +* <> include::trento-mcp-install.adoc[] include::trento-mcp-config.adoc[] From 70d3a1dfa8e588afefa02e0fe1851c0d8c737fb2 Mon Sep 17 00:00:00 2001 From: Eliska Romanova Date: Fri, 18 Sep 2026 11:19:59 +0200 Subject: [PATCH 4/6] Second round of reviews --- trento/adoc/trento-liz-ai-assistant.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/trento/adoc/trento-liz-ai-assistant.adoc b/trento/adoc/trento-liz-ai-assistant.adoc index a10512eb..98270aae 100644 --- a/trento/adoc/trento-liz-ai-assistant.adoc +++ b/trento/adoc/trento-liz-ai-assistant.adoc @@ -36,7 +36,7 @@ Which providers and models are supported?:: * OpenAI GPT -- + -Each provider offers several models. To ensure compatibility, {liz} only displays models capable of powering the assistant. +Each provider offers several models. To ensure compatibility, {trento} only displays models capable of powering the assistant. [[sec-liz-data-access]] How does {liz} access data?:: From 5d07c5ab8b0fda23c554faba97f750ef244b8034 Mon Sep 17 00:00:00 2001 From: Eliska Romanova Date: Mon, 21 Sep 2026 15:44:47 +0200 Subject: [PATCH 5/6] Small fix --- trento/adoc/partials/mcp-host-prerequisites.adoc | 2 +- trento/adoc/trento-ai-integrations.adoc | 2 +- trento/adoc/trento-liz-ai-assistant.adoc | 2 +- trento/adoc/trento-mcp-config.adoc | 5 ++--- trento/adoc/trento-mcp-host-others.adoc | 2 +- trento/adoc/trento-mcp-host-sles.adoc | 2 +- trento/adoc/trento-mcp-how-to-use.adoc | 2 +- trento/adoc/trento-mcp-install-kubernetes.adoc | 2 +- trento/adoc/trento-mcp-install-systemd.adoc | 2 +- trento/adoc/trento-mcp-install.adoc | 2 +- trento/adoc/trento-mcp-integration.adoc | 2 +- 11 files changed, 12 insertions(+), 13 deletions(-) diff --git a/trento/adoc/partials/mcp-host-prerequisites.adoc b/trento/adoc/partials/mcp-host-prerequisites.adoc index 604adfed..b6c0ed6d 100644 --- a/trento/adoc/partials/mcp-host-prerequisites.adoc +++ b/trento/adoc/partials/mcp-host-prerequisites.adoc @@ -1,4 +1,4 @@ -:revdate: 2026-09-18 +:revdate: 2026-09-21 * An LLM provider and credentials. ** Public hosted options, such as Google Gemini, OpenAI, etc. diff --git a/trento/adoc/trento-ai-integrations.adoc b/trento/adoc/trento-ai-integrations.adoc index 8afd9377..596c0a80 100644 --- a/trento/adoc/trento-ai-integrations.adoc +++ b/trento/adoc/trento-ai-integrations.adoc @@ -3,7 +3,7 @@ include::product-attributes.adoc[] [[trento-ai-integrations]] == {trento} AI integrations -:revdate: 2026-09-18 +:revdate: 2026-09-21 {trento} provides AI-driven capabilities to help you monitor and troubleshoot your SAP landscape using natural language. You can use these features directly within the web console, or connect {trento} data to your own external AI tools. diff --git a/trento/adoc/trento-liz-ai-assistant.adoc b/trento/adoc/trento-liz-ai-assistant.adoc index 98270aae..47c7fc61 100644 --- a/trento/adoc/trento-liz-ai-assistant.adoc +++ b/trento/adoc/trento-liz-ai-assistant.adoc @@ -2,7 +2,7 @@ include::product-attributes.adoc[] [[sec-trento-liz-ai-assistant]] === {liz} AI assistant in {tr_web} -:revdate: 2026-09-18 +:revdate: 2026-09-21 {liz} is a chat-based AI assistant built directly into {tr_web}. It lets you ask questions about your SAP landscape in natural language. By analyzing the live state of your systems and best-practice validations, {liz} helps you actively monitor health and identify issues, all without requiring any additional deployment. diff --git a/trento/adoc/trento-mcp-config.adoc b/trento/adoc/trento-mcp-config.adoc index 3c8195bc..f68acb66 100644 --- a/trento/adoc/trento-mcp-config.adoc +++ b/trento/adoc/trento-mcp-config.adoc @@ -2,7 +2,7 @@ include::product-attributes.adoc[] [[sec-trento-mcp-config]] ==== Configuring {tr_mcp} -:revdate: 2026-09-18 +:revdate: 2026-09-21 This section provides an overview of how to configure the {tr_mcp} depending on the deployment method. @@ -111,9 +111,8 @@ spec: name: health ---- - [[sec-trento-mcp-systemd-config]] -===== Configuration in an systemd deployment +===== Configuration in a systemd deployment [[sec-trento-mcp-systemd-config-sources]] ====== Configuration Sources diff --git a/trento/adoc/trento-mcp-host-others.adoc b/trento/adoc/trento-mcp-host-others.adoc index 758a1b91..ab33e81d 100644 --- a/trento/adoc/trento-mcp-host-others.adoc +++ b/trento/adoc/trento-mcp-host-others.adoc @@ -2,7 +2,7 @@ include::product-attributes.adoc[] [[sec-trento-mcp-others]] ===== Integrating the {tr_mcp} with other clients -:revdate: 2026-09-18 +:revdate: 2026-09-21 The {tr_mcp} can be integrated with any client application that supports the Model Context Protocol. This makes it possible to interact with the {trento} API and execute tools defined in the OpenAPI specification through your preferred AI assistant or development tool. diff --git a/trento/adoc/trento-mcp-host-sles.adoc b/trento/adoc/trento-mcp-host-sles.adoc index 4a968053..4276fc04 100644 --- a/trento/adoc/trento-mcp-host-sles.adoc +++ b/trento/adoc/trento-mcp-host-sles.adoc @@ -2,7 +2,7 @@ include::product-attributes.adoc[] [[sec-trento-mcp-sles]] ===== Integrating the {tr_mcp} with {mcp_host} -:revdate: 2026-09-18 +:revdate: 2026-09-21 This guide explains how to connect the {tr_mcp} to {sles} 16 using {mcp_host}, a lightweight CLI tool for the Model Context Protocol (MCP). diff --git a/trento/adoc/trento-mcp-how-to-use.adoc b/trento/adoc/trento-mcp-how-to-use.adoc index 0c233b61..abf42948 100644 --- a/trento/adoc/trento-mcp-how-to-use.adoc +++ b/trento/adoc/trento-mcp-how-to-use.adoc @@ -2,7 +2,7 @@ include::product-attributes.adoc[] [[sec-trento-mcp-how-to-use]] ==== Using the {tr_mcp} -:revdate: 2026-09-18 +:revdate: 2026-09-21 The {tr_mcp} provides the interface for AI-assisted infrastructure operations, enabling agentic assistants to integrate with {trento}. By utilizing the Model Context Protocol, these assistants can perform monitoring and troubleshooting tasks through natural language. See <> or <> for details. diff --git a/trento/adoc/trento-mcp-install-kubernetes.adoc b/trento/adoc/trento-mcp-install-kubernetes.adoc index ef77e155..3a1120da 100644 --- a/trento/adoc/trento-mcp-install-kubernetes.adoc +++ b/trento/adoc/trento-mcp-install-kubernetes.adoc @@ -2,7 +2,7 @@ include::product-attributes.adoc[] [[sec-trento-mcp-server-k8s]] ===== {k8s} deployment of {tr_mcp} -:revdate: 2026-09-18 +:revdate: 2026-09-21 include::partials/kubernetes-placeholders.adoc[] diff --git a/trento/adoc/trento-mcp-install-systemd.adoc b/trento/adoc/trento-mcp-install-systemd.adoc index bb2dd49e..b3b2cf5f 100644 --- a/trento/adoc/trento-mcp-install-systemd.adoc +++ b/trento/adoc/trento-mcp-install-systemd.adoc @@ -2,7 +2,7 @@ include::product-attributes.adoc[] [[sec-trento-mcp-server-systemd]] ===== systemd deployment -:revdate: 2026-09-18 +:revdate: 2026-09-21 A systemd-based installation of the {tr_mcp} using RPM packages can be performed manually on the latest supported versions of {sles4sap}. diff --git a/trento/adoc/trento-mcp-install.adoc b/trento/adoc/trento-mcp-install.adoc index 8dff144a..022f7c9c 100644 --- a/trento/adoc/trento-mcp-install.adoc +++ b/trento/adoc/trento-mcp-install.adoc @@ -2,7 +2,7 @@ include::product-attributes.adoc[] [[sec-trento-mcp-install]] ==== Installing {tr_mcp} -:revdate: 2026-09-18 +:revdate: 2026-09-21 The {tr_mcp} can be deployed in different ways depending on your infrastructure and requirements. diff --git a/trento/adoc/trento-mcp-integration.adoc b/trento/adoc/trento-mcp-integration.adoc index 3ba6877a..c4e9fc3f 100644 --- a/trento/adoc/trento-mcp-integration.adoc +++ b/trento/adoc/trento-mcp-integration.adoc @@ -2,7 +2,7 @@ include::product-attributes.adoc[] [[sec-trento-mcp-integration]] === MCP Integration -:revdate: 2026-09-18 +:revdate: 2026-09-21 While {trento} provides the built-in {liz} assistant for AI conversations directly inside the {tr_web} console, you can also integrate {trento}'s data into your own external AI tools and workflows. The {tr_mcp} is an optional component that enables this external AI-assisted infrastructure management for your SAP landscape. From bcc1ca9acaef27c6ca465a0233395c51bd99d8b0 Mon Sep 17 00:00:00 2001 From: Eliska Romanova Date: Mon, 21 Sep 2026 15:52:57 +0200 Subject: [PATCH 6/6] Last small fix for pdf rendering --- trento/adoc/trento-liz-ai-assistant.adoc | 8 ++++---- trento/adoc/trento-mcp-install-kubernetes.adoc | 8 ++++---- trento/adoc/trento-mcp-integration.adoc | 8 ++++---- 3 files changed, 12 insertions(+), 12 deletions(-) diff --git a/trento/adoc/trento-liz-ai-assistant.adoc b/trento/adoc/trento-liz-ai-assistant.adoc index 47c7fc61..b0fa36de 100644 --- a/trento/adoc/trento-liz-ai-assistant.adoc +++ b/trento/adoc/trento-liz-ai-assistant.adoc @@ -6,11 +6,11 @@ include::product-attributes.adoc[] {liz} is a chat-based AI assistant built directly into {tr_web}. It lets you ask questions about your SAP landscape in natural language. By analyzing the live state of your systems and best-practice validations, {liz} helps you actively monitor health and identify issues, all without requiring any additional deployment. -This section covers the following topics: +This chapter covers the following topics: -* <> -* <> -* <> +* <> +* <> +* <> [[sec-about-liz]] ==== About the {liz} AI assistant diff --git a/trento/adoc/trento-mcp-install-kubernetes.adoc b/trento/adoc/trento-mcp-install-kubernetes.adoc index 3a1120da..b5289e29 100644 --- a/trento/adoc/trento-mcp-install-kubernetes.adoc +++ b/trento/adoc/trento-mcp-install-kubernetes.adoc @@ -85,7 +85,7 @@ Example output: The {tr_mcp} {helm} chart supports various configuration options: -[[mcp-customize-ingress-path]] +[[mcp-customize-ingress-path, Customize Ingress Path]] Customize Ingress Path:: + By default, ingress is enabled. @@ -106,7 +106,7 @@ helm upgrade --install trento-server oci://registry.suse.com/trento/trento-serve + The {tr_mcp} endpoint will be: `\https://TRENTO_SERVER_HOSTNAME{tr_mcp_ingress_path}/mcp` -[[mcp-adjust-log-verbosity]] +[[mcp-adjust-log-verbosity, Adjust Log Verbosity]] Adjust Log Verbosity:: + The default log level is `info`. Adjust it for debugging: @@ -122,7 +122,7 @@ helm upgrade --install trento-server oci://registry.suse.com/trento/trento-serve ---- ==== -[[mcp-adjust-resource-limits]] +[[mcp-adjust-resource-limits, Adjust Resource Limits]] Adjust Resource Limits:: + For production deployments with different resource requirements: @@ -141,7 +141,7 @@ helm upgrade --install trento-server oci://registry.suse.com/trento/trento-serve ---- ==== -[[mcp-disable-health-check-probes]] +[[mcp-disable-health-check-probes, Disable Health Check Probes]] Disable Health Check Probes:: + Health check probes are enabled by default. To disable them if needed, run the following command: diff --git a/trento/adoc/trento-mcp-integration.adoc b/trento/adoc/trento-mcp-integration.adoc index c4e9fc3f..6110b366 100644 --- a/trento/adoc/trento-mcp-integration.adoc +++ b/trento/adoc/trento-mcp-integration.adoc @@ -8,11 +8,11 @@ While {trento} provides the built-in {liz} assistant for AI conversations direct {tr_mcp} exposes {trento} functionality through the Model Context Protocol (MCP), an open standard that facilitates secure communication between data sources and AI agents. While the core {trserver} operates independently, the {tr_mcp} component allows you to integrate {trento} into an agentic AI workflow. This enables the use of Large Language Models (LLMs) to perform common monitoring and troubleshooting tasks using natural language, providing a standardized way for AI tools to access real-time system state and best-practice validations. -This section covers the following topics: +This chapter covers the following topics: -* <> -* <> -* <> +* <> +* <> +* <> include::trento-mcp-install.adoc[] include::trento-mcp-config.adoc[]