Added 1.0 observability topics

docs-site/assets/kagent-docs/versions/kube-prometheus-stack.md

@@ -0,0 +1 @@
+75.6.1

docs-site/assets/kagent-docs/versions/prometheus.md

@@ -0,0 +1 @@
+29.33.0

docs-site/content/kagent/1.x/agents/agent-harness.md

@@ -116,7 +116,7 @@ Some supported combinations still carry restrictions.
 | `claude` with `AnthropicVertexAI` | Accepts only `projectID` and `location`. The Secret must hold a `service_account` key whose `project_id` matches and whose `token_uri` is `https://oauth2.googleapis.com`. |
 
 > [!IMPORTANT]
-> Neither `codex` nor `claude` accepts a ModelConfig that sets `defaultHeaders`, `tls`, or `apiKeyPassthrough`. Separately, the `kagent` and `byo` runtimes cannot use a ModelConfig whose credential is a file rather than a string. This restriction rules out both Vertex AI providers there. For more information about that limitation, see [About model providers]({{< link path="setup/model-providers/about-model-providers" >}}).
+> Neither `codex` nor `claude` accepts a ModelConfig that sets `defaultHeaders`, `tls`, or `apiKeyPassthrough`. Separately, the `kagent` and `byo` runtimes cannot use a ModelConfig whose credential is a file rather than a string. The file credential restriction rules out both Vertex AI providers on the `kagent` and `byo` runtimes. For more information about that limitation, see [About model providers]({{< link path="setup/model-providers/about-model-providers" >}}).
 
 ## Tool and skill support
 
@@ -132,7 +132,7 @@ The `kagent` and `byo` runtimes take the full set. For more information about wh
 
 ## Telemetry content settings
 
-Tracing and audit logging both carry the prompts and replies that an agent exchanges with a model. Two settings in the kagent Helm chart decide whether that content leaves the runtime, and each one reaches a different set of runtimes. Both default to `false`, and both take effect only where tracing or audit logging is already enabled.
+Tracing carries the prompts and replies that an agent exchanges with a model, and so does log export on the `claude` runtime. Two settings in the kagent Helm chart decide whether that content leaves the runtime, and each one reaches a different set of runtimes. Both default to `false`, and both take effect only where tracing or log export is already enabled.
 
 ```yaml
 otel:
@@ -143,10 +143,10 @@ otel:
 
 | Setting | What it includes | Applies to |
 | ------- | ---------------- | ---------- |
-| `otel.captureSensitiveContent` | Prompts, tool details, and assistant replies in the runtime's telemetry. On the `claude` runtime, tool results require tracing, and assistant replies require audit logging. | `codex`, `claude` |
+| `otel.captureSensitiveContent` | Prompts, tool details, and assistant replies in the runtime's telemetry. On the `kagent` runtime, the content appears in the spans for each model call. On the `claude` runtime, tool results require tracing, and assistant replies require log export through `otel.logging`. | `kagent`, `codex`, `claude` |
 | `otel.logging.captureRawApiBodies` | The complete provider API request and response bodies. This setting returns more than `otel.captureSensitiveContent` does, and it takes effect only when `otel.logging.enabled` is `true`. | `claude` |
 
-The `kagent` runtime honors neither setting. To include message content for an agent on that runtime, set `OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT` in the Harness `spec.env` field. That variable defaults differently for each signal, so check the [audit prompt onfiguration]({{< link path="observability/audit-prompts#configuration" >}}) before you set it.
+The controller sets `OTEL_INSTRUMENTATION_GENAI_CAPTURE_MESSAGE_CONTENT` in every compiled runtime from `otel.captureSensitiveContent`, so setting that variable in the Harness `spec.env` field has no effect.
 
 The controller sends the `byo` runtime no telemetry configuration, so neither setting reaches it. A `byo` image that implements OpenTelemetry itself reads whatever the Harness `spec.env` field holds. For more information, see [Tracing]({{< link path="observability/tracing#about-trace-coverage" >}}).
 

docs-site/content/kagent/1.x/examples/agentgateway.md

@@ -386,6 +386,6 @@ An `AgentgatewayPolicy` holds the same `promptGuard` configuration, and one poli
 
 {{< cards >}}
   {{< card link=`{{< link path="setup/model-providers/byo-agentgateway" >}}` title="agentgateway model routing" subtitle="Review the Gateway, AgentgatewayModel, and ModelConfig that carry an agent's model traffic." >}}
-  {{< card link=`{{< link path="observability/audit-prompts" >}}` title="Audit prompts" subtitle="Export the prompts and replies that your agents exchange with a model, and query them in a logging backend." >}}
+  {{< card link=`{{< link path="observability/audit-prompts" >}}` title="Audit prompts" subtitle="Review where each runtime records the prompts and replies that your agents exchange with a model, and how to capture them for an audit." >}}
   {{< card link="https://agentgateway.dev/docs/kubernetes/latest/documentation/llm/guardrails/regex/#block-requests-with-pii" title="agentgateway regex guardrails" subtitle="Read the full set of regex guards, masking rules, and built-in patterns in the agentgateway documentation." >}}
 {{< /cards >}}

docs-site/content/kagent/1.x/observability/_index.md

@@ -1,6 +1,6 @@
 ---
 title: Observability
-description: Open the kagent UI, trace agent requests across the controller and the Actors that run your agents, and audit the prompts your agents send.
+description: Open the kagent UI, set up an OpenTelemetry stack, and review the traces, metrics, and logs that kagent and Agent Substrate report.
 weight: 70
 author: kagent.dev
 ---