From bb6bdd4ca2c5bc32d3a23b7aeb880b89f39dd7a8 Mon Sep 17 00:00:00 2001
From: Mike Birnstiehl <114418652+mdbirnstiehl@users.noreply.github.com>
Date: Thu, 16 Oct 2025 09:17:47 -0500
Subject: [PATCH] [AI Assistant] Add Non-string fields anonymization limitation

This PR closes [Issue 3381](https://github.com/elastic/docs-content/issues/3381)
---
 docs/en/observability/observability-ai-assistant.asciidoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/observability/observability-ai-assistant.asciidoc b/docs/en/observability/observability-ai-assistant.asciidoc
index ae19602fbd..fa07f8bead 100644
--- a/docs/en/observability/observability-ai-assistant.asciidoc
+++ b/docs/en/observability/observability-ai-assistant.asciidoc
@@ -517,11 +517,11 @@ Anonymization requires the following:
 
 Anonymization has the following limitations:
 
+* *Non-string fields*: Anonymization only applies to string values. Booleans, numbers, image types, and other non-string values are ignored.
 * *Performance (NER)*: Running an NER model can add latency depending on the request. To improve performance of the model, consider scaling up your ML nodes by adjusting deployment parameters: increase `number_of_allocations` for better throughput and `threads_per_allocation` for faster individual requests. For details, refer to https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ml-start-trained-model-deployment[start trained model deployment API].
 * *Structured JSON*: The NER model we validated (`elastic/distilbert-base-uncased-finetuned-conll03-english`) is trained on natural English text and often misses entities inside JSON or other structured data. If thorough masking is required, prefer regex rules and craft them to account for JSON syntax.
 * *False negatives / positives*: No model or pattern is perfect. Model accuracy may vary depending on model and input.
 
-
 [discrete]
 [[obs-ai-known-issues]]
 == Known issues