simplify examples to reduce time series

Author: gitName

articles/api-management/azure-openai-emit-token-metric-policy.md

@@ -50,7 +50,6 @@ The `azure-openai-emit-token-metric` policy sends custom metrics to Application
 | Attribute | Description                | Required                | Default value  |
 | --------- | -------------------------- |  ------------------ | -------------- |
 | namespace | A string. Namespace of metric. Policy expressions aren't allowed. | No        | API Management |
-| value     |  Value of metric expressed as a double. Policy expressions are allowed.   | No           | 1              |
 
 
 ## Elements
@@ -92,15 +91,13 @@ The `azure-openai-emit-token-metric` policy sends custom metrics to Application
 
 ## Example
 
-The following example sends Azure OpenAI token count metrics to Application Insights along with User ID, Client IP, and API ID as dimensions.
+The following example sends Azure OpenAI token count metrics to Application Insights along with API ID as a custom dimension.
 
 ```xml
 <policies>
   <inbound>
       <azure-openai-emit-token-metric
             namespace="AzureOpenAI">   
-            <dimension name="User ID" />
-            <dimension name="Client IP" value="@(context.Request.IpAddress)" />
             <dimension name="API ID" />
         </azure-openai-emit-token-metric> 
   </inbound>

articles/api-management/emit-metric-policy.md

@@ -81,14 +81,12 @@ The `emit-metric` policy sends custom metrics in the specified format to Applica
 
 ## Example
 
-The following example sends a custom metric to count the number of API requests along with user ID, client IP, and API ID as custom dimensions.
+The following example sends a custom metric to count the number of API requests along with API ID as a custom dimension.
 
 ```xml
 <policies>
   <inbound>
     <emit-metric name="Request" value="1" namespace="my-metrics"> 
-        <dimension name="User ID" /> 
-        <dimension name="Client IP" value="@(context.Request.IpAddress)" /> 
         <dimension name="API ID" /> 
     </emit-metric> 
   </inbound>

articles/api-management/llm-emit-token-metric-policy.md

@@ -52,7 +52,6 @@ The `llm-emit-token-metric` policy sends custom metrics to Application Insights
 | Attribute | Description                | Required                | Default value  |
 | --------- | -------------------------- |  ------------------ | -------------- |
 | namespace | A string. Namespace of metric. Policy expressions aren't allowed. | No        | API Management |
-| value     |  Value of metric expressed as a double. Policy expressions are allowed.   | No           | 1              |
 
 
 ## Elements
@@ -93,15 +92,13 @@ The `llm-emit-token-metric` policy sends custom metrics to Application Insights
 
 ## Example
 
-The following example sends LLM token count metrics to Application Insights along with User ID, Client IP, and API ID as dimensions.
+The following example sends LLM token count metrics to Application Insights along with API ID as a custom dimension.
 
 ```xml
 <policies>
   <inbound>
       <llm-emit-token-metric
             namespace="MyLLM">   
-            <dimension name="User ID" />
-            <dimension name="Client IP" value="@(context.Request.IpAddress)" />
             <dimension name="API ID" />
         </llm-emit-token-metric> 
   </inbound>