Repository: Axway/amplify-central
Pull request #645: APIGOV-30112 - update traceability sampling docs for new sampling process
Author: login: jcollins-axway
Created: 2025-04-01T15:03:32Z | Merged: 2025-04-25T00:19:23Z

## Describe the changes

Update documentation to reflect changes for sampling updates.

## Deploy preview link

* [Create Environment](http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/add_environments/) - Remove sampling from steps
* [Network traffic](http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/connected_agent_common_reference/network_traffic/) - Update reference to sampling doc
* [Trace sampling](http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/) - Update
* [Agent Variables](http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/connected_agent_common_reference/agent-variables/)
* [Edit environment](http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/edit_environment/) - Remove sampling percentage reference
* Removed sampling references from
 * http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/connect_api_manager/agent-variables/
 * http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/connect_api_manager/tips-troubleshooting-and-limitations/
 * http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/connect_aws_gateway/tips-and-troubleshooting/
 * http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/connect_azure_gateway/tips-and-troubleshooting/
 * http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/connect_ibm_api_connect/
 * http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/connected_agent_common_reference/traceability_usage/
 * http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/connect_manage_environ/mesh_management/deploy-your-agents-with-the-axway-cli/
 * http://pr-645.amplify-central.opendocs-builder.pcloud.axway.int/docs/integrate_with_central/cli_central/cli_embedded_agent_config/

## Checklist for contributors

Before submitting this PR:

* Verify that all status checks have passed
* For more information on the Markdown linter rules, see [DavidAnson/markdownlint](https://github.com/DavidAnson/markdownlint)
* For first-time contributors, ensure that you have signed the [Axway CLA](https://cla.axway.com/)



Diff:
diff --git a/content/en/docs/connect_manage_environ/add_environments.md b/content/en/docs/connect_manage_environ/add_environments.md
index 547ba9a03..eda79700b 100644
--- a/content/en/docs/connect_manage_environ/add_environments.md
+++ b/content/en/docs/connect_manage_environ/add_environments.md
@@ -53,7 +53,6 @@ Learn how to create an environment to represent your API services and other disc
 3. Embedded Traceability Agent Settings (these configuration steps are displayed only if there is Embedded agent support for the environment type and "Enable Traceability Agent" is selected in the Configure step):
 
     * **Frequency** - set how often the Embedded agent should run traffic collection. 30 minutes is the minimum value that can be set. For example, 30m = 30 minutes, 5h5m = 5 hours and 5 mins, 2d = 2 days.
-    * **Sampling** - enter the percentage of full transaction details sent to the platform for display in Business and Consumer insights. The default value is 10 and the acceptable values are between 0 and 50.
     * **Redaction and Sanitization** - redaction and sanitization settings to use when reporting transactions from the data plane.
         * **URL Path** - all URL paths, or path regular expressions, which may be reported to Amplify Engage. ".*" will send all the path values. For example, if the agent finds a path of `https://somehost.com/pathof/my/api/uses/thispath` then `https://somehost.com/pathof/my/api/uses/thispath` will be sent to the platform.
         * **Query Arguments** - regular expressions applied to the query argument name and query argument value in the transactional data.
@@ -135,7 +134,6 @@ Learn how to create an environment to represent your API services and other disc
 3. Embedded Traceability Agent Settings (these configuration steps are displayed only if there is Embedded agent support for the environment type and "Enable Traceability Agent" is selected in the Configure step):
 
     * **Frequency** - set how often the Embedded agent should run traffic collection. 30 minutes is the minimum value that can be set. For example, 30m = 30 minutes, 5h5m = 5 hours and 5 mins, 2d = 2 days.
-    * **Sampling** - enter the percentage of full transaction details sent to the platform for display in Business and Consumer insights. The default value is 10 and the acceptable values are between 0 and 50.
     * **Redaction and Sanitization** - the redaction and sanitization settings to use when reporting transactions from the data plane.
         * **URL Path** - all URL paths, or path regular expressions, which may be reported to Amplify Engage. ".*" will send all the path values. For example, if the agent finds a path of `https://somehost.com/pathof/my/api/uses/thispath` then `https://somehost.com/pathof/my/api/uses/thispath` will be sent to the platform.
         * **Query Arguments** - regular expressions applied to the query argument name and query argument value in the transactional data.
diff --git a/content/en/docs/connect_manage_environ/connect_api_manager/agent-variables.md b/content/en/docs/connect_manage_environ/connect_api_manager/agent-variables.md
index d136eb315..e9b231883 100644
--- a/content/en/docs/connect_manage_environ/connect_api_manager/agent-variables.md
+++ b/content/en/docs/connect_manage_environ/connect_api_manager/agent-variables.md
@@ -73,8 +73,6 @@ CENTRAL_ENVIRONMENT=AmplifyEngageEnvironmentName
 CENTRAL_GRPC_ENABLED=true 
 # enable (default=true) to store a cache locally when the agent is stopped. It enables the agent to resume from where it left off when restarting.
 AGENTFEATURES_PERSISTCACHE=true
-# enable to add sampling based on consumer and subscription information so each consumer can see a certain percentage of the traffic
-TRACEABILITY_PER_SUBSCRIPTION=true
 ```
 
 If you are either struggling with a variable value or want to benefit from the advanced agents features (API filtering / SSL security / proxy access / logging), the following section describes the variables the agents (Discovery / Traceability) rely on.
diff --git a/content/en/docs/connect_manage_environ/connect_api_manager/tips-troubleshooting-and-limitations.md b/content/en/docs/connect_manage_environ/connect_api_manager/tips-troubleshooting-and-limitations.md
index 9eebbe76b..ad4343c39 100644
--- a/content/en/docs/connect_manage_environ/connect_api_manager/tips-troubleshooting-and-limitations.md
+++ b/content/en/docs/connect_manage_environ/connect_api_manager/tips-troubleshooting-and-limitations.md
@@ -118,8 +118,6 @@ Below is the list of error codes and possible remediations.
 | 1506   | error while compiling regular expression                                                                                                             | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                      |
 | 1510   | global redaction config have not been initialized                                                                                                    | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                      |
 | 1511   | error while compiling regular expression                                                                                                             | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                      |
-| 1520   | global sampling has not been initialized                                                                                                             | See [Trace sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/).                                                                                                                                                                                        |
-| 1521   | invalid sampling configuration                                                                                                                       | See [Trace sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/).                                                                                                                                                                                        |
 | 1550   | error hit while applying redaction                                                                                                                   | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                      |
 | 1600   | error registering the job                                                                                                                            | The agent attempted to register a job, but could not do so successfully.                                                                                                                                                                                                                    |
 | 1601   | error executing a job                                                                                                                                | A job defined in the agent failed, see the logs for more information.                                                                                                                                                                                                                       |
diff --git a/content/en/docs/connect_manage_environ/connect_aws_gateway/tips-and-troubleshooting.md b/content/en/docs/connect_manage_environ/connect_aws_gateway/tips-and-troubleshooting.md
index e2ce54eed..117939714 100644
--- a/content/en/docs/connect_manage_environ/connect_aws_gateway/tips-and-troubleshooting.md
+++ b/content/en/docs/connect_manage_environ/connect_aws_gateway/tips-and-troubleshooting.md
@@ -86,8 +86,6 @@ Below is the list of error codes and possible remediations.
 | 1506   | error while compiling regular expression                                                                                                             | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                           |
 | 1510   | global redactions have not been initialized                                                                                                          | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                           |
 | 1511   | error while compiling regular expression                                                                                                             | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                           |
-| 1520   | global sampling has not been initialized                                                                                                             | See [Trace sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/).                                                                                                                                                                                             |
-| 1521   | invalid sampling configuration                                                                                                                       | See [Trace sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/).                                                                                                                                                                                             |
 | 1550   | error hit while applying redaction                                                                                                                   | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                           |
 | 1600   | error registering the job                                                                                                                            | The agent attempted to register a job, but could not do so successfully.                                                                                                                                                                                                                         |
 | 1601   | error executing a job                                                                                                                                | A job defined in the agent failed, see the logs for more information.                                                                                                                                                                                                                            |
diff --git a/content/en/docs/connect_manage_environ/connect_azure_gateway/tips-and-troubleshooting.md b/content/en/docs/connect_manage_environ/connect_azure_gateway/tips-and-troubleshooting.md
index cf7fd0227..e9d689e29 100644
--- a/content/en/docs/connect_manage_environ/connect_azure_gateway/tips-and-troubleshooting.md
+++ b/content/en/docs/connect_manage_environ/connect_azure_gateway/tips-and-troubleshooting.md
@@ -114,8 +114,6 @@ Below is the list of error codes and possible remediations.
 | 1506   | error while compiling regular expression                                                                                                                                                                                    | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                 |
 | 1510   | global redactions have not been initialized                                                                                                                                                                                 | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                 |
 | 1511   | error while compiling regular expression                                                                                                                                                                                    | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                 |
-| 1520   | global sampling has not been initialized                                                                                                                                                                                    | See [Trace sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/).                                                                                                                                                                                   |
-| 1521   | invalid sampling configuration                                                                                                                                                                                              | See [Trace sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/).                                                                                                                                                                                   |
 | 1550   | error hit while applying redaction                                                                                                                                                                                          | See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).                                                                                                                                                                                 |
 | 1600   | error registering the job                                                                                                                                                                                                   | The agent attempted to register a job, but could not do so successfully.                                                                                                                                                                                                               |
 | 1601   | error executing a job                                                                                                                                                                                                       | A job defined in the agent failed, see the logs for more information.                                                                                                                                                                                                                  |
diff --git a/content/en/docs/connect_manage_environ/connect_ibm_api_connect/_index.md b/content/en/docs/connect_manage_environ/connect_ibm_api_connect/_index.md
index 49e7b2b1c..e68587823 100644
--- a/content/en/docs/connect_manage_environ/connect_ibm_api_connect/_index.md
+++ b/content/en/docs/connect_manage_environ/connect_ibm_api_connect/_index.md
@@ -54,8 +54,6 @@ The Traceability Agent collects metric information and sampled transactions from
 
 The metric data collected includes call count, the number of transactions for a specific API or API/Application combination, and latency details.
 
-The transaction data collected will only be a sample of the overall number of transactions that were seen in IBM API Connect.
-
 ## Prerequisites
 
 * An Axway Amplify subscription in the Amplify platform
diff --git a/content/en/docs/connect_manage_environ/connected_agent_common_reference/agent-variables.md b/content/en/docs/connect_manage_environ/connected_agent_common_reference/agent-variables.md
index 80358d387..6fe1123e0 100644
--- a/content/en/docs/connect_manage_environ/connected_agent_common_reference/agent-variables.md
+++ b/content/en/docs/connect_manage_environ/connected_agent_common_reference/agent-variables.md
@@ -160,9 +160,6 @@ All of the variables in this list may be repeated for each IdP to be used. Each
 | TRACEABILITY_REDACTION_REQUESTHEADER_SHOW      | Determines what Request Header Keys to send to Amplify Engage. By default, all request headers are redacted. Example: `[{keyMatch:"Accept.*"}, {keyMatch:"Connection"}]` to send all Accept* and the Connection request header.                                                                                         |
 | TRACEABILITY_REDACTION_RESPONSEHEADER_SANITIZE | Determines what portions of a Response Header value to sanitize. Example: `[{keyMatch:"apiKey",valueMatch:".{0,10}$"}]` to sanitize the `apiKey` request header to mask the last ten characters or less.                                                                                                                        |
 | TRACEABILITY_REDACTION_RESPONSEHEADER_SHOW     | Determines which Response Header Keys to send to Amplify. By default, all response headers are redacted. Example: `[{keyMatch:".*"}]` to send all response headers.                                                                                                                                                             |
-| TRACEABILITY_SAMPLING_PERCENTAGE               | The percentage of all transactions that are sent to Amplify. A value of `0` reports no traffic (default value `0`), maximum value `10`. If the value is set higher than the maximum value, then the agent will use the default value.                                                                                           |
-| TRACEABILITY_SAMPLING_PER_API                  | When true, the percentage of API transactions sent will be based on each API ID in the transaction (default value: `true`).                                                                                                                                                                                                     |
-| TRACEABILITY_SAMPLING_ONLYERRORS               | When true, only API transactions that have an http error code will be sent to Amplify (default value: `false`).                                                                                                                                                                                                                 |
 | TRACEABILITY_WORKER                            | The number of workers collecting events and sending them to Amplify Engage (default value: `1`).                                                                                                                                                                                                                        |
 
 #### Audit log variables
diff --git a/content/en/docs/connect_manage_environ/connected_agent_common_reference/archive/_index.md b/content/en/docs/connect_manage_environ/connected_agent_common_reference/archive/_index.md
new file mode 100644
index 000000000..7bfeb8662
--- /dev/null
+++ b/content/en/docs/connect_manage_environ/connected_agent_common_reference/archive/_index.md
@@ -0,0 +1,7 @@
+---
+title: Archive
+linkTitle: Archive
+weight: 150
+date: 2025-04-18
+---
+An archive of features that are available in supported agents, but no longer available in the latest agents.
diff --git a/content/en/docs/connect_manage_environ/connected_agent_common_reference/archive/trace_sampling.md b/content/en/docs/connect_manage_environ/connected_agent_common_reference/archive/trace_sampling.md
new file mode 100644
index 000000000..889ec5bb6
--- /dev/null
+++ b/content/en/docs/connect_manage_environ/connected_agent_common_reference/archive/trace_sampling.md
@@ -0,0 +1,104 @@
+---
+title: Trace sampling
+linkTitle: Trace sampling
+draft: false
+weight: 150
+date: 2025-04-18
+---
+{{< alert title="Note" color="primary" >}}This is an archived functionality. For the latest sampling support, see [Trace sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling).{{< /alert >}}
+
+The Traceability Agent can sample the transaction information that is sent to Amplify Analytics. Learn how to set up sampling rules used to send only certain transactions to Amplify Analytics. With the agent default configuration, all transactions are sent to Amplify Analytics.
+
+## Sampling
+
+Sampling adds the ability to control the amount of transaction data that is sent to Amplify Analytics.
+
+### Settings
+
+The following settings can be used to control the sampling. A percentage can be set to control the number of transactions that are sent, and a switch can be set to determine how that percentage is applied.
+
+#### Percentage
+
+The `TRACEABILITY_SAMPLING_PERCENTAGE` variable, defaulted to **`0`**, may be set to any value between 0 and 10.  
+
+* A value of `0` results in no transactions sent to Amplify Analytics for the API traffic display within Business Insights. The API Health display will still show the API metrics even with sampling set to zero percent.
+* A value of `10` results in 10% of all transactions sent to Amplify Analytics for the API traffic display.
+
+The agent uses a counter to apply the sampling. When a value (other than 0 and 10) is set, the agent will send all transactions up to that value and then not send any until it reaches 100. Therefore, this percentage results in the first x of each 100 transactions being sampled.
+
+#### Per API
+
+The `TRACEABILITY_SAMPLING_PER_API` variable, defaulted to `true`, may be changed to determine how the percentage variable is applied.
+
+* A value of `true` means that the percentage is applied to each API ID within the transaction. In this case, regardless of usage, all APIs will have transaction representation in Business Insights.
+* A value of `false` means that the percentage is applied globally to all APIs. In this case, APIs with lower utilization may never be seen in Business Insights, as the sampling is always the first x of each 100 transactions.
+
+#### Report Only Errors
+
+The `TRACEABILITY_SAMPLING_ONLYERRORS` variable, defaulted to `false`, may be changed to send only error transaction events to ingestion service.
+
+* A value of `true` means that only the transaction events with a transaction status of *Failure* are sent to ingestion service based on the sampling percentage and may be seen in Business Insights.
+* A value of `false` means that transaction events with a transaction status of *Failure* will follow the sampling percentage and may or may not not be seen in Business Insights, as the sampling is always the first x of each 100 transactions.
+
+### Preparing Traceability Agent
+
+The Traceability Agent may be configured to sample fewer than all events. The maximum percentage is 10%.
+
+#### No events
+
+The following is a sample value that is added to `ta_env_vars.env`, which will send no gateway transactions to Amplify Analytics.
+
+```shell
+TRACEABILITY_SAMPLING_PERCENTAGE=0
+```
+
+#### 10% of all events, regardless of API
+
+The following is a sample value that is added to `ta_env_vars.env`, which will send 10% of the gateway transactions to Amplify Analytics.
+
+```shell
+TRACEABILITY_SAMPLING_PERCENTAGE=10
+TRACEABILITY_SAMPLING_PER_API=false
+```
+
+If the agent receives 100 transactions, evenly between two APIs, only the first 10 will be sent to Amplify Analytics.
+
+#### 10% of all events, regardless of API and error status
+
+The following is a sample value that is added to `ta_env_vars.env`, which will send 10% of the gateway transactions, including errors to Amplify Analytics.
+
+```shell
+TRACEABILITY_SAMPLING_PERCENTAGE=10
+TRACEABILITY_SAMPLING_PER_API=false
+TRACEABILITY_SAMPLING_ONLYERRORS=false
+```
+
+#### 10% of error events, regardless of API
+
+The following is a sample value that is added to `ta_env_vars.env`, which will send 10% of the gateway transactions to Amplify Analytics. Including all errors.
+
+```shell
+TRACEABILITY_SAMPLING_PERCENTAGE=10
+TRACEABILITY_SAMPLING_PER_API=false
+TRACEABILITY_SAMPLING_ONLYERRORS=true
+```
+
+If the agent receives 100 transactions, evenly between two APIs, the first 10 (five from each API) with error status will be sent to Amplify Analytics.
+
+#### 10% of events per API ID
+
+The following is a sample value that is added to `ta_env_vars.env`, which will send 10% of the gateway transactions to Amplify Analytics.
+
+```shell
+TRACEABILITY_SAMPLING_PERCENTAGE=10
+TRACEABILITY_SAMPLING_PER_API=true
+```
+
+If the agent receives 100 transactions, evenly between two APIs, only 10 (five from each API) will be sent to Amplify Analytics.
+
+{{< alert title="Note" color="primary" >}}It is recommended that you use the Business Insights API Health screen to identify the APIs that have status errors. Then view the API details with the tools provided by your API Gateway vendor.{{< /alert >}}
+
+For details on how to configure and view API Traffic Insights on the Axway API Management Gateway, see:
+
+* [Amplify Analytics Operational Insights](https://docs.axway.com/bundle/axway-open-docs/page/docs/operational_insights/index.html)
+* [Configure API Gateway Analytics](https://docs.axway.com/bundle/axway-open-docs/page/docs/apimanager_analytics/index.html).
diff --git a/content/en/docs/connect_manage_environ/connected_agent_common_reference/network_traffic.md b/content/en/docs/connect_manage_environ/connected_agent_common_reference/network_traffic.md
index 44b288b8b..a07aa31c1 100644
--- a/content/en/docs/connect_manage_environ/connected_agent_common_reference/network_traffic.md
+++ b/content/en/docs/connect_manage_environ/connected_agent_common_reference/network_traffic.md
@@ -86,7 +86,7 @@ Data Fields:
 
 #### Transactions data
 
-The transaction data represents the number and details of transactions processed by the Gateway during a period of time. You can limit the number of transactions sent to the platform, or completely turn this feature off, by applying a sampling configuration to the Traceability Agent. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
+The transaction data represents the number and details of transactions processed by the Gateway during a period of time. By default, the Traceability Agent does not send transactions but you can enable it for a short period on demand. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
 
 The transactions can be redacted (by default) and/or sanitized, according to your need, before sending the information to Amplify platform. See [Trace redaction](/docs/connect_manage_environ/connected_agent_common_reference/trace_redaction/).
 
diff --git a/content/en/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling.md b/content/en/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling.md
index dfa6290ae..77e367c89 100644
--- a/content/en/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling.md
+++ b/content/en/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling.md
@@ -4,96 +4,64 @@ linkTitle: Trace sampling
 draft: false
 weight: 10
 ---
-The Traceability Agent can sample the transaction information that is sent to Amplify Analytics . Learn how to set up sampling rules used to send only certain transactions to Amplify Analytics. With the agent default configuration, all transactions are sent to Amplify Analytics.
+{{< alert title="Note" color="primary" >}}If you are using a Traceability Agent version that supports percentage-based sampling, see [Archived trace sampling](/docs/connect_manage_environ/connected_agent_common_reference/archive/trace_sampling).{{< /alert >}}
 
-## Sampling
-
-Sampling adds the ability to control the amount of transaction data that is sent to Amplify Analytics.
-
-### Settings
-
-The following settings can be used to control the sampling.  A percentage can be set to control the number of transactions that are sent, and a switch can be set to determine how that percentage is applied.
-
-#### Percentage
-
-The `TRACEABILITY_SAMPLING_PERCENTAGE` variable, defaulted to **`0`**, may be set to any value between 0 and 10.  
+The Traceability Agent can sample the transaction information that is sent to Amplify Analytics. Learn how to request a sampling period, the restrictions of the sampling period, and the rules used by the agent when sending those transactions.
 
-* A value of `0` results in no transactions sent to Amplify Analytics for the API traffic display within Business Insights.  The API Health display will still show the API metrics even with sampling set to zero percent.
-* A value of `10` results in 10% of all transactions sent to Amplify Analytics for the API traffic display.
+{{< alert title="Note" color="primary" >}}It is recommended that you use the Business Insights API Health screen to identify the APIs that have status errors. Then view the API details with the tools provided by your API Gateway vendor.{{< /alert >}}
 
-The agent uses a counter to apply the sampling. When a value (other than 0 and 10) is set, the agent will send all transactions up to that value and then not send any until it reaches 100.  Therefore, this percentage results in the first x of each 100 transactions being sampled.
+## Sampling
 
-#### Per API
+Sampling grants the agent the ability to send transaction information of API Traffic to Amplify Analytics.
 
-The `TRACEABILITY_SAMPLING_PER_API` variable, defaulted to `true`, may be changed to determine how the percentage variable is applied.
+When requesting a sampling period the user will also request a time frame, 0-300 seconds (five minutes). Given that the agent has surpassed its cool down period (30 minutes) since the last sampling ended, the agent sampling will be enabled. The agent will begin to send transactions as they come through, but still be limited to a maximum of 100 transactions a minute.
 
-* A value of `true` means that the percentage is applied to each API ID within the transaction. In this case, regardless of usage, all APIs will have transaction representation in Business Insights.
-* A value of `false` means that the percentage is applied globally to all APIs. In this case, APIs with lower utilization may never be seen in Business Insights, as the sampling is always the first x of each 100 transactions.
+{{< alert title="Note" color="primary" >}}The max sampling time and transactions per minute limit may be changed in future updates to Amplify Engage.{{< /alert >}}
 
-#### Report Only Errors
+### Requesting the Traceability Agent to sample
 
-The `TRACEABILITY_SAMPLING_ONLYERRORS` variable, defaulted to `false`, may be changed to send only error transaction events to ingestion service.
+The Traceability Agent, if listed as [supporting sampling](/docs/connect_manage_environ#on-premise-Agent-Features), is already configured. The only other step is to request the sampling to begin using the Amplify Engage UI or CLI.
 
-* A value of `true` means that only the transaction events with a transaction status of *Failure* are sent to ingestion service based on the sampling percentage and may be seen in Business Insights.
-* A value of `false` means that transaction events with a transaction status of *Failure* will follow the sampling percentage and may or may not not be seen in Business Insights, as the sampling is always the first x of each 100 transactions.
+{{< alert title="Note" color="primary" >}}The duration field below does not apply to SaaS agents. When enabled, the SaaS agent will immediately run and send transactional data for that execution only.{{< /alert >}}
 
-### Preparing Traceability Agent
+#### Request via the UI
 
-The Traceability Agent may be configured to sample fewer than all events. The maximum percentage is 10%
+1. Navigate to the *Agents List* page in Amplify Engage.
+2. Find a Traceability Agent you would like transactional data from.
+3. Click the **Traceability Sampling** icon.
+4. Click in the menu to enable sampling. Select a duration, and click **Save**.
 
-#### No events
+Your selected agent should now sample transactions for the duration selected.
+  
+#### Request via the CLI
 
-The following is a sample value that is added to `ta_env_vars.env`, which will send no gateway transactions to Amplify Analytics.
+* Log in using the Amplify CLI:
 
 ```shell
-TRACEABILITY_SAMPLING_PERCENTAGE=0
+axway auth login
 ```
 
-#### 10% of all events, regardless of API
-
-The following is a sample value that is added to `ta_env_vars.env`, which will send 10% of the gateway transactions to Amplify Analytics.
-
+* Retrieve the Traceability Agent you would like transactional data from:
+  
 ```shell
-TRACEABILITY_SAMPLING_PERCENTAGE=10
-TRACEABILITY_SAMPLING_PER_API=false
+axway central get -o yaml -s [Environment Name] traceabilityagent [Traceability Agent Name] > resource.yaml
 ```
 
-If the agent receives 100 transactions, evenly between 2 APIs, only the first 10 will be sent to Amplify Analytics.
-
-#### 10% of all events, regardless of API and error status
-
-The following is a sample value that is added to `ta_env_vars.env`, which will send 10% of the gateway transactions including errors to Amplify Analytics.
-
-```shell
-TRACEABILITY_SAMPLING_PERCENTAGE=10
-TRACEABILITY_SAMPLING_PER_API=false
-TRACEABILITY_SAMPLING_ONLYERRORS=false
+* Within the `resource.yaml` file, add:
+  
+```yaml
+sampletrigger:
+  requested: true
+  duration: 60
 ```
 
-#### 10% of error events, regardless of API
-
-The following is a sample value that is added to `ta_env_vars.env`, which will send 10% of the gateway transactions to Amplify Analytics. Including all errors.
+* Update the Traceability Agent using the `resource.yaml` file:
 
 ```shell
-TRACEABILITY_SAMPLING_PERCENTAGE=10
-TRACEABILITY_SAMPLING_PER_API=false
-TRACEABILITY_SAMPLING_ONLYERRORS=true
+axway central apply -f resource.yaml
 ```
 
-If the agent receives 100 transactions, evenly between 2 APIs, the first 10 (five from each API) with error status will be sent to Amplify Analytics.
-
-#### 10% of events per API ID
-
-The following is a sample value that is added to `ta_env_vars.env`, which will send 10% of the gateway transactions to Amplify Analytics.
-
-```shell
-TRACEABILITY_SAMPLING_PERCENTAGE=10
-TRACEABILITY_SAMPLING_PER_API=true
-```
-
-If the agent receives 100 transactions, evenly between 2 APIs, only 10 (5 from each API) will be sent to Amplify Analytics.
-
-{{< alert title="Note" color="primary" >}}It is recommended that you use the Business Insights API Health screen to identify the APIs that have status errors. Then view the API details with the tools provided by your API Gateway vendor.{{< /alert >}}
+Your selected agent should now sample transactions for 60 seconds.
 
 For details on how to configure and view API Traffic Insights on the Axway API Management Gateway, see:
 
diff --git a/content/en/docs/connect_manage_environ/connected_agent_common_reference/traceability_usage.md b/content/en/docs/connect_manage_environ/connected_agent_common_reference/traceability_usage.md
index 5da4aa027..adb074ee0 100644
--- a/content/en/docs/connect_manage_environ/connected_agent_common_reference/traceability_usage.md
+++ b/content/en/docs/connect_manage_environ/connected_agent_common_reference/traceability_usage.md
@@ -105,8 +105,6 @@ Step 5. Install the agent.
 
 After all questions are answered, the Axway Central CLI will create an Amplify platform environment that will host the usage report, as well as local files (`traceability_agent` binary file / `ta_env_vars.env` file containing the agent configuration / the public-private key to manage the communication from the agent to the Platform), based on the provided answers.
 
-{{< alert title="Note" color="primary" >}}If you plan to use the Traceability Agent for logging usage only, set `TRACEABILITY_SAMPLING_PERCENTAGE=0` and `TRACEABILITY_SAMPLING_ONLYERRORS=false` in the `ta_env_vars.env` file produced by the CLI to disable the transaction report.{{< /alert >}}
-
 The local files must be copied to the gateway machine, as mentioned in the CLI output.
 
 After all files are copied, start Traceability Agent: `./traceability_agent ./ta_env_vars.env`
@@ -243,10 +241,6 @@ The usage report is based on the transactions the Traceability Agent monitors. I
 
 In the case of high demand, Axway recommends turning off the trace event logging of the gateway. In this situation, the Traceability Agent will not be able to monitor the transactions or report the corresponding traffic.
 
-### AWS API Gateway
-
-The current solution relies on AWS Simple Queue Service to collect traffic from CloudWatch. However, there is a limit of 10 SQS messages per client connection that can be consumed at one time. As a workaround, you can increase the number of workers (i.e., consumer clients) using the `AWS_WORKERS` variable. Be aware that the number of workers is directly related to the network consumption -- the more you add, the more network connections are used.
-
 ### Azure API Gateway
 
 Within Azure API Gateway, it is possible to activate the transaction sampling for Azure Monitoring (either at API level or for all APIs). Activating sampling will make the usage report inaccurate.
diff --git a/content/en/docs/connect_manage_environ/edit_environment.md b/content/en/docs/connect_manage_environ/edit_environment.md
index b5b5325c4..a3d115bd9 100644
--- a/content/en/docs/connect_manage_environ/edit_environment.md
+++ b/content/en/docs/connect_manage_environ/edit_environment.md
@@ -38,7 +38,7 @@ These configuration steps are displayed only if an Embedded AWS environment is s
 
 3. Embedded Traceability Agent Settings:
 
-    * If enabled, edit: Frequency, Sampling Percentage, URL Path Allowed Patterns, Query Arguments Allowed Patterns, Query Arguments Sanitization Patterns, Request Headers Allowed Patterns, Request Headers Sanitization Patterns, Response Headers Allowed Patterns, Response Headers Sanitization Patterns, and Masking Characters. Sample All Errors can also be set.
+    * If enabled, edit: Frequency, URL Path Allowed Patterns, Query Arguments Allowed Patterns, Query Arguments Sanitization Patterns, Request Headers Allowed Patterns, Request Headers Sanitization Patterns, Response Headers Allowed Patterns, Response Headers Sanitization Patterns, and Masking Characters. Sample All Errors can also be set.
 
 ### Embedded Apigee X API Gateway environment
 
@@ -75,7 +75,7 @@ These configuration steps are displayed only if an Embedded Azure environment is
 
 3. Embedded Traceability Agent Settings:
 
-    * If enabled, edit: Frequency, Sampling Percentage, URL Path Allowed Patterns, Query Arguments Allowed Patterns, Query Arguments Sanitization Patterns, Request Headers Allowed Patterns, Request Headers Sanitization Patterns, Response Headers Allowed Patterns, Response Headers Sanitization Patterns, and Masking Characters. Sample All Errors can also be set.
+    * If enabled, edit: Frequency, URL Path Allowed Patterns, Query Arguments Allowed Patterns, Query Arguments Sanitization Patterns, Request Headers Allowed Patterns, Request Headers Sanitization Patterns, Response Headers Allowed Patterns, Response Headers Sanitization Patterns, and Masking Characters.
 
 ### Embedded GitHub environment
 
diff --git a/content/en/docs/connect_manage_environ/mesh_management/deploy-your-agents-with-the-axway-cli.md b/content/en/docs/connect_manage_environ/mesh_management/deploy-your-agents-with-the-axway-cli.md
index 3a2c5778d..a5087e21d 100644
--- a/content/en/docs/connect_manage_environ/mesh_management/deploy-your-agents-with-the-axway-cli.md
+++ b/content/en/docs/connect_manage_environ/mesh_management/deploy-your-agents-with-the-axway-cli.md
@@ -284,21 +284,7 @@ Created secret/gateway-cert in the istio-system namespace.
       No
     ```
 
-2. Select a sampling rate. A sampling rate of 1 will log 1% of transactions, a sampling rate of 10 will log 10% of all transactions.
-
-    ```bash
-    What sampling rate would you like to use? (1-10):  (1)
-    ```
-
-3. Select if the agent should report all errors recorded by the Traceability Agent.
-
-    ```bash
-    Would you like to report all errors?:
-    ❯ Yes
-      No
-    ```
-
-4. Select the Traceability Agent protocol.
+2. Select the Traceability Agent protocol.
 
     ```bash
     ? Select Traceability protocol:  (Use arrow keys)
diff --git a/content/en/docs/integrate_with_central/cli_central/cli_embedded_agent_config.md b/content/en/docs/integrate_with_central/cli_central/cli_embedded_agent_config.md
index ff93f31c2..bcbc598a5 100644
--- a/content/en/docs/integrate_with_central/cli_central/cli_embedded_agent_config.md
+++ b/content/en/docs/integrate_with_central/cli_central/cli_embedded_agent_config.md
@@ -134,7 +134,7 @@ Add additional tags to resources on Amplify Engage, ignore tags on dataplane res
 
 ## Embedded Traceability Agent
 
-Configured to set if headers should be processed, redact certain information, sample an amount of the transactional data, and set the owner for the transactional data.
+Configured to set if headers should be processed, redact certain information, and set the owner for the transactional data.
 
 * Pull the existing Traceability Agent from your environment and direct it to a file:
 
@@ -160,9 +160,6 @@ Configured to set if headers should be processed, redact certain information, sa
                 * **keyMatch** - response headers keys that match any of these expressions will have the valueMatch sanitized
                 * **valueMatch** - when the header name matches the keyMatch expression, the valueMatch expression is applied and replaces the matches in the header value with the masking character value.
         * **maskingCharacter** - the set of character(s) that will replace any value matched while sanitizing
-    * **sampling** - the sampling settings that will be applied when reporting transactional data
-        * **percentage** - the percentage of all transactions that will be reported to Amplify Engage for display in Business and Consumer insights
-        * **allErrors** - when set to `true`, regardless of the percentage, all errored transactions will be reported to Amplify Engage
     * **owner** - the team owner that will be set when creating resources in Amplify Engage
         * type - set to `team`
         * id - the id value found when viewing the team in Amplify Engage
@@ -192,9 +189,6 @@ Configured to set if headers should be processed, redact certain information, sa
               - keyMath: <header-key-regex>
                 valueMatch: <header-val-regex>
           maskingCharacter: {*}
-        sampling: 
-          percentage: 1
-          allErrors: true
         owner:
           type: team
           id: <team-id>


Reviews:
user: login: robertengaxway
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-01T23:06:57Z
user: login: robertengaxway
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-01T23:10:34Z
user: login: robertengaxway
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-01T23:13:11Z
user: login: robertengaxway
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-01T23:17:13Z
user: login: lbadenhop
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-02T15:06:18Z
user: login: lbadenhop
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-02T15:06:51Z
user: login: jcollins-axway
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-02T20:38:57Z
user: login: jcollins-axway
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-02T20:39:36Z
user: login: robertengaxway
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-04T16:27:31Z
user: login: robertengaxway
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-04-04T16:28:17Z
user: login: georgiana-caras
state: CHANGES_REQUESTED
author_association: COLLABORATOR
submitted_at: 2025-04-17T20:38:15Z
user: login: robertengaxway
body: I approve
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-04-18T21:46:03Z
user: login: georgiana-caras
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-04-21T17:46:58Z

Review comments:
diff_hunk: @@ -86,7 +86,7 @@ Data Fields:
 
 #### Transactions data
 
-The transaction data represents the number and details of transactions processed by the Gateway during a period of time. You can limit the number of transactions sent to the platform, or completely turn this feature off, by applying a sampling configuration to the Traceability Agent. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
+The transaction data represents the number and details of transactions processed by the Gateway during a period of time. By default the Traceability Agent does not send Transactions but you can enable it for a short period on demand. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/network_traffic.md
user: login: robertengaxway
body: I would suggest adding because there is no single version number to use:
"The On-demand Traceability Sampling is included in all Traceability Agents released after April 4th 2025."
created_at: 2025-04-01T23:06:57Z
author_association: COLLABORATOR
diff_hunk: @@ -4,96 +4,61 @@ linkTitle: Trace sampling
 draft: false
 weight: 10
 ---
-The Traceability Agent can sample the transaction information that is sent to Amplify Analytics . Learn how to set up sampling rules used to send only certain transactions to Amplify Analytics. With the agent default configuration, all transactions are sent to Amplify Analytics.
+The Traceability Agent can sample the transaction information that is sent to Amplify Analytics. Learn how to request a sampling period, the restrictions of the sampling period, and the rules used by the agent when sending those transactions.
 
-## Sampling
-
-Sampling adds the ability to control the amount of transaction data that is sent to Amplify Analytics.
-
-### Settings
-
-The following settings can be used to control the sampling.  A percentage can be set to control the number of transactions that are sent, and a switch can be set to determine how that percentage is applied.
-
-#### Percentage
-
-The `TRACEABILITY_SAMPLING_PERCENTAGE` variable, defaulted to **`0`**, may be set to any value between 0 and 10.  
-
-* A value of `0` results in no transactions sent to Amplify Analytics for the API traffic display within Business Insights.  The API Health display will still show the API metrics even with sampling set to zero percent.
-* A value of `10` results in 10% of all transactions sent to Amplify Analytics for the API traffic display.
-
-The agent uses a counter to apply the sampling. When a value (other than 0 and 10) is set, the agent will send all transactions up to that value and then not send any until it reaches 100.  Therefore, this percentage results in the first x of each 100 transactions being sampled.
+{{< alert title="Note" color="primary" >}}It is recommended that you use the Business Insights API Health screen to identify the APIs that have status errors. Then view the API details with the tools provided by your API Gateway vendor.{{< /alert >}}
 
-#### Per API
+## Sampling
 
-The `TRACEABILITY_SAMPLING_PER_API` variable, defaulted to `true`, may be changed to determine how the percentage variable is applied.
+Sampling grants the agent the ability to send transaction information of API Traffic to Amplify Analytics.
 
-* A value of `true` means that the percentage is applied to each API ID within the transaction. In this case, regardless of usage, all APIs will have transaction representation in Business Insights.
-* A value of `false` means that the percentage is applied globally to all APIs. In this case, APIs with lower utilization may never be seen in Business Insights, as the sampling is always the first x of each 100 transactions.
+When requesting a sampling period the user will also request a time frame, 0-300 seconds (5 minutes). Given that the agent has surpassed its cool down period (30 minutes), time since last sampling has ended, the agent sampling will be enabled. At that point the agent will begin to send transactions as they come through, but still be limited to a maximum of 100 transactions a minute.
 
-#### Report Only Errors
+{{< alert title="Note" color="primary" >}}The max sampling time and transactions per minute limit may be changed future updates to Amplify Engage.{{< /alert >}}
 
-The `TRACEABILITY_SAMPLING_ONLYERRORS` variable, defaulted to `false`, may be changed to send only error transaction events to ingestion service.
+### Requesting the Traceability Agent to sample
 
-* A value of `true` means that only the transaction events with a transaction status of *Failure* are sent to ingestion service based on the sampling percentage and may be seen in Business Insights.
-* A value of `false` means that transaction events with a transaction status of *Failure* will follow the sampling percentage and may or may not not be seen in Business Insights, as the sampling is always the first x of each 100 transactions.
+The Traceability Agent, if listed as [supporting sampling](/docs/connect_manage_environ#on-premise-Agent-Features), is already configured. The only other step is to request the sampling to begin using the Amplify Engage UI or CLI.
 
-### Preparing Traceability Agent
+{{< alert title="Note" color="primary" >}}The duration field below doe snot apply to SaaS agents, when enabled the SaaS agent will immediately run and send transactional data for that execution only.{{< /alert >}}
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling.md
user: login: robertengaxway
body: typo on "does not"
If the duration field does not apply, should we state how long the duration is for SaaS agents.
created_at: 2025-04-01T23:10:34Z
author_association: COLLABORATOR
diff_hunk: @@ -4,96 +4,61 @@ linkTitle: Trace sampling
 draft: false
 weight: 10
 ---
-The Traceability Agent can sample the transaction information that is sent to Amplify Analytics . Learn how to set up sampling rules used to send only certain transactions to Amplify Analytics. With the agent default configuration, all transactions are sent to Amplify Analytics.
+The Traceability Agent can sample the transaction information that is sent to Amplify Analytics. Learn how to request a sampling period, the restrictions of the sampling period, and the rules used by the agent when sending those transactions.
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling.md
user: login: robertengaxway
body: I would suggest adding because there is no single version number to use:
"The On-demand Traceability Sampling request is included in all Traceability Agents released after April 4th 2025."
created_at: 2025-04-01T23:13:10Z
author_association: COLLABORATOR
diff_hunk: @@ -75,7 +75,7 @@ These configuration steps are displayed only if an Embedded Azure environment is
 
 3. Embedded Traceability Agent Settings:
 
-    * If enabled, edit: Frequency, Sampling Percentage, URL Path Allowed Patterns, Query Arguments Allowed Patterns, Query Arguments Sanitization Patterns, Request Headers Allowed Patterns, Request Headers Sanitization Patterns, Response Headers Allowed Patterns, Response Headers Sanitization Patterns, and Masking Characters. Sample All Errors can also be set.
+    * If enabled, edit: Frequency, URL Path Allowed Patterns, Query Arguments Allowed Patterns, Query Arguments Sanitization Patterns, Request Headers Allowed Patterns, Request Headers Sanitization Patterns, Response Headers Allowed Patterns, Response Headers Sanitization Patterns, and Masking Characters. Sample All Errors can also be set.
path: content/en/docs/connect_manage_environ/edit_environment.md
user: login: robertengaxway
body: I believe we should indicate that "If Sample All Errors is set, the Traceability Agent will perform On-demand sampling up to a maximum of 300 second upon request"  
created_at: 2025-04-01T23:17:13Z
author_association: COLLABORATOR
diff_hunk: @@ -4,96 +4,61 @@ linkTitle: Trace sampling
 draft: false
 weight: 10
 ---
-The Traceability Agent can sample the transaction information that is sent to Amplify Analytics . Learn how to set up sampling rules used to send only certain transactions to Amplify Analytics. With the agent default configuration, all transactions are sent to Amplify Analytics.
+The Traceability Agent can sample the transaction information that is sent to Amplify Analytics. Learn how to request a sampling period, the restrictions of the sampling period, and the rules used by the agent when sending those transactions.
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling.md
user: login: lbadenhop
body: Why would we state in the doc topic when a feature is added? Our documentation always reflects the latest and the Release Notes reference when a feature is added.
created_at: 2025-04-02T15:06:17Z
author_association: COLLABORATOR
diff_hunk: @@ -86,7 +86,7 @@ Data Fields:
 
 #### Transactions data
 
-The transaction data represents the number and details of transactions processed by the Gateway during a period of time. You can limit the number of transactions sent to the platform, or completely turn this feature off, by applying a sampling configuration to the Traceability Agent. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
+The transaction data represents the number and details of transactions processed by the Gateway during a period of time. By default the Traceability Agent does not send Transactions but you can enable it for a short period on demand. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/network_traffic.md
user: login: lbadenhop
body: Why would we state in the doc topic when a feature is added? Our documentation always reflects the latest and the Release Notes reference when a feature is added.
created_at: 2025-04-02T15:06:51Z
author_association: COLLABORATOR
diff_hunk: @@ -4,96 +4,61 @@ linkTitle: Trace sampling
 draft: false
 weight: 10
 ---
-The Traceability Agent can sample the transaction information that is sent to Amplify Analytics . Learn how to set up sampling rules used to send only certain transactions to Amplify Analytics. With the agent default configuration, all transactions are sent to Amplify Analytics.
+The Traceability Agent can sample the transaction information that is sent to Amplify Analytics. Learn how to request a sampling period, the restrictions of the sampling period, and the rules used by the agent when sending those transactions.
 
-## Sampling
-
-Sampling adds the ability to control the amount of transaction data that is sent to Amplify Analytics.
-
-### Settings
-
-The following settings can be used to control the sampling.  A percentage can be set to control the number of transactions that are sent, and a switch can be set to determine how that percentage is applied.
-
-#### Percentage
-
-The `TRACEABILITY_SAMPLING_PERCENTAGE` variable, defaulted to **`0`**, may be set to any value between 0 and 10.  
-
-* A value of `0` results in no transactions sent to Amplify Analytics for the API traffic display within Business Insights.  The API Health display will still show the API metrics even with sampling set to zero percent.
-* A value of `10` results in 10% of all transactions sent to Amplify Analytics for the API traffic display.
-
-The agent uses a counter to apply the sampling. When a value (other than 0 and 10) is set, the agent will send all transactions up to that value and then not send any until it reaches 100.  Therefore, this percentage results in the first x of each 100 transactions being sampled.
+{{< alert title="Note" color="primary" >}}It is recommended that you use the Business Insights API Health screen to identify the APIs that have status errors. Then view the API details with the tools provided by your API Gateway vendor.{{< /alert >}}
 
-#### Per API
+## Sampling
 
-The `TRACEABILITY_SAMPLING_PER_API` variable, defaulted to `true`, may be changed to determine how the percentage variable is applied.
+Sampling grants the agent the ability to send transaction information of API Traffic to Amplify Analytics.
 
-* A value of `true` means that the percentage is applied to each API ID within the transaction. In this case, regardless of usage, all APIs will have transaction representation in Business Insights.
-* A value of `false` means that the percentage is applied globally to all APIs. In this case, APIs with lower utilization may never be seen in Business Insights, as the sampling is always the first x of each 100 transactions.
+When requesting a sampling period the user will also request a time frame, 0-300 seconds (5 minutes). Given that the agent has surpassed its cool down period (30 minutes), time since last sampling has ended, the agent sampling will be enabled. At that point the agent will begin to send transactions as they come through, but still be limited to a maximum of 100 transactions a minute.
 
-#### Report Only Errors
+{{< alert title="Note" color="primary" >}}The max sampling time and transactions per minute limit may be changed future updates to Amplify Engage.{{< /alert >}}
 
-The `TRACEABILITY_SAMPLING_ONLYERRORS` variable, defaulted to `false`, may be changed to send only error transaction events to ingestion service.
+### Requesting the Traceability Agent to sample
 
-* A value of `true` means that only the transaction events with a transaction status of *Failure* are sent to ingestion service based on the sampling percentage and may be seen in Business Insights.
-* A value of `false` means that transaction events with a transaction status of *Failure* will follow the sampling percentage and may or may not not be seen in Business Insights, as the sampling is always the first x of each 100 transactions.
+The Traceability Agent, if listed as [supporting sampling](/docs/connect_manage_environ#on-premise-Agent-Features), is already configured. The only other step is to request the sampling to begin using the Amplify Engage UI or CLI.
 
-### Preparing Traceability Agent
+{{< alert title="Note" color="primary" >}}The duration field below doe snot apply to SaaS agents, when enabled the SaaS agent will immediately run and send transactional data for that execution only.{{< /alert >}}
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling.md
user: login: jcollins-axway
body: it does not apply, so why would we state anything?
created_at: 2025-04-02T20:38:55Z
author_association: COLLABORATOR
diff_hunk: @@ -75,7 +75,7 @@ These configuration steps are displayed only if an Embedded Azure environment is
 
 3. Embedded Traceability Agent Settings:
 
-    * If enabled, edit: Frequency, Sampling Percentage, URL Path Allowed Patterns, Query Arguments Allowed Patterns, Query Arguments Sanitization Patterns, Request Headers Allowed Patterns, Request Headers Sanitization Patterns, Response Headers Allowed Patterns, Response Headers Sanitization Patterns, and Masking Characters. Sample All Errors can also be set.
+    * If enabled, edit: Frequency, URL Path Allowed Patterns, Query Arguments Allowed Patterns, Query Arguments Sanitization Patterns, Request Headers Allowed Patterns, Request Headers Sanitization Patterns, Response Headers Allowed Patterns, Response Headers Sanitization Patterns, and Masking Characters. Sample All Errors can also be set.
path: content/en/docs/connect_manage_environ/edit_environment.md
user: login: jcollins-axway
body: All errors is not an option anymore
created_at: 2025-04-02T20:39:34Z
author_association: COLLABORATOR
diff_hunk: @@ -86,7 +86,7 @@ Data Fields:
 
 #### Transactions data
 
-The transaction data represents the number and details of transactions processed by the Gateway during a period of time. You can limit the number of transactions sent to the platform, or completely turn this feature off, by applying a sampling configuration to the Traceability Agent. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
+The transaction data represents the number and details of transactions processed by the Gateway during a period of time. By default the Traceability Agent does not send Transactions but you can enable it for a short period on demand. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/network_traffic.md
user: login: robertengaxway
body: We will still use the release notes to indicate feature additions.
However, the deprecation of the way Transaction Sampling was done with older agents is something we need to discuss more with Bosch because of the contractual details that Bas raised.
Thus why I am suggesting we make an exception for now to document the prior feature behavior , until we have closed the loop with Bosch.
Georgi, your feedback?
created_at: 2025-04-04T16:27:31Z
author_association: COLLABORATOR
diff_hunk: @@ -4,96 +4,61 @@ linkTitle: Trace sampling
 draft: false
 weight: 10
 ---
-The Traceability Agent can sample the transaction information that is sent to Amplify Analytics . Learn how to set up sampling rules used to send only certain transactions to Amplify Analytics. With the agent default configuration, all transactions are sent to Amplify Analytics.
+The Traceability Agent can sample the transaction information that is sent to Amplify Analytics. Learn how to request a sampling period, the restrictions of the sampling period, and the rules used by the agent when sending those transactions.
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling.md
user: login: robertengaxway
body: see my prior comment on why we need to keep the prior way the feature behaved and what date it changed.

created_at: 2025-04-04T16:28:17Z
author_association: COLLABORATOR
diff_hunk: @@ -86,7 +86,7 @@ Data Fields:
 
 #### Transactions data
 
-The transaction data represents the number and details of transactions processed by the Gateway during a period of time. You can limit the number of transactions sent to the platform, or completely turn this feature off, by applying a sampling configuration to the Traceability Agent. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
+The transaction data represents the number and details of transactions processed by the Gateway during a period of time. By default the Traceability Agent does not send Transactions but you can enable it for a short period on demand. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/network_traffic.md
user: login: georgiana-caras
body: The goal is not to state in the doc when a feature is added, but as customers can run on older agents with a different transaction sampling methods, we need to continue to document both. 

created_at: 2025-04-08T19:46:10Z
author_association: COLLABORATOR
diff_hunk: @@ -86,7 +86,7 @@ Data Fields:
 
 #### Transactions data
 
-The transaction data represents the number and details of transactions processed by the Gateway during a period of time. You can limit the number of transactions sent to the platform, or completely turn this feature off, by applying a sampling configuration to the Traceability Agent. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
+The transaction data represents the number and details of transactions processed by the Gateway during a period of time. By default the Traceability Agent does not send Transactions but you can enable it for a short period on demand. See [Trace Sampling](/docs/connect_manage_environ/connected_agent_common_reference/trace_sampling/#sampling).
path: content/en/docs/connect_manage_environ/connected_agent_common_reference/network_traffic.md
user: login: georgiana-caras
body: @lbadenhop , @robertengaxway  it's not immediate obvious to me where the Date is listed in the documentation. As customers can continue to run on agent versions that still support the Percentage based sampling, we need to continue to document it. My suggestion is to Archive the existing Transaction Sampling doc file, and in the current document we should add a note that states: "If you are using a Traceability agent version that support Percentage based sampling, refer to [add link to archived file]". 
created_at: 2025-04-15T23:24:12Z
author_association: COLLABORATOR

PR comments:
user: login: docsbuilder
created_at: 2025-04-01T15:05:27Z
body: ### <span aria-hidden="true">✅</span> Deploy preview is ready!

 |  Name | Link |
 |---------------------------------|------------------------|
 |<span aria-hidden="true">🔨</span> Latest commit | 5e8e62a |
 |<span aria-hidden="true">😎</span> Deploy preview | http://PR-645.amplify-central.opendocs-builder.pcloud.axway.int |
author_association: COLLABORATOR
user: login: jcollins-axway
created_at: 2025-04-01T17:38:53Z
body: @vivekschauhan @sbolosan @alrosca @dgghinea - please review the doc changes here
author_association: COLLABORATOR
user: login: jcollins-axway
created_at: 2025-04-18T14:59:51Z
body: Added an archive directory for features in supported agents, < 1 year old, but no longer in the latest agents. I will create a calendar event to remind me that this document can be removed in April of next year.
author_association: COLLABORATOR