Merge pull request #525 from logzio/revert-524-accountregioncode

Revert "Account region code"

docs/_include/general-shipping/k8s.md

@@ -133,7 +133,7 @@ helm install -n monitoring \
 --set metricsOrTraces.enabled=true \
 --set logzio-k8s-telemetry.traces.enabled=true \
 --set logzio-k8s-telemetry.secrets.TracesToken="<<TRACING-SHIPPING-TOKEN>>" \
---set logzio-k8s-telemetry.secrets.LogzioRegion="<<logzio_account_region_code>>" \
+--set logzio-k8s-telemetry.secrets.LogzioRegion="<<LOGZIO_ACCOUNT_REGION_CODE>>" \
 --set logzio-k8s-telemetry.secrets.env_id="<<CLUSTER-NAME>>" \
 logzio-monitoring logzio-helm/logzio-monitoring
 ```
@@ -142,7 +142,7 @@ logzio-monitoring logzio-helm/logzio-monitoring
 | --- | --- |
 | `<<TRACING-SHIPPING-TOKEN>>` | Your [traces shipping token](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping?product=tracing). |
 | `<<CLUSTER-NAME>>` | The cluster's name, to easily identify the telemetry data for each environment. |
-| `<<logzio_account_region_code>>` | Name of your Logz.io traces region e.g `us`, `eu`... |
+| `<<LOGZIO_ACCOUNT_REGION_CODE>>` | Name of your Logz.io traces region e.g `us`, `eu`... |
 
 
 For traces shipping troubleshooting, see our [Distributed Tracing troubleshooting](https://docs.logz.io/docs/user-guide/distributed-tracing/troubleshooting/tracing-troubleshooting/).
@@ -155,7 +155,7 @@ helm install -n monitoring \
 --set metricsOrTraces.enabled=true \
 --set logzio-k8s-telemetry.traces.enabled=true \
 --set logzio-k8s-telemetry.secrets.TracesToken="<<TRACING-SHIPPING-TOKEN>>" \
---set logzio-k8s-telemetry.secrets.LogzioRegion="<<logzio_account_region_code>>" \
+--set logzio-k8s-telemetry.secrets.LogzioRegion="<<LOGZIO_ACCOUNT_REGION_CODE>>" \
 --set logzio-k8s-telemetry.secrets.env_id="<<CLUSTER-NAME>>" \
 --set logzio-k8s-telemetry.spm.enabled=true \
 --set logzio-k8s-telemetry.secrets.SpmToken=<<SPM-METRICS-SHIPPING-TOKEN>> \
@@ -167,7 +167,7 @@ logzio-monitoring logzio-helm/logzio-monitoring
 | `<<TRACING-SHIPPING-TOKEN>>` | Your [traces shipping token](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping). |
 | `<<CLUSTER-NAME>>` | The cluster's name, to easily identify the telemetry data for each environment. |
 | `<<LISTENER-HOST>>` | Your account's [listener host](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping?product=logs). |
-| `<<logzio_account_region_code>>` | Name of your Logz.io traces region e.g `us`, `eu`... |
+| `<<LOGZIO_ACCOUNT_REGION_CODE>>` | Name of your Logz.io traces region e.g `us`, `eu`... |
 | `<<SPM-METRICS-SHIPPING-TOKEN>>` | Your [span metrics shipping token](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping). |
 
 ## Deploy both charts with span metrics and service graph
@@ -177,7 +177,7 @@ helm install -n monitoring \
 --set metricsOrTraces.enabled=true \
 --set logzio-k8s-telemetry.traces.enabled=true \
 --set logzio-k8s-telemetry.secrets.TracesToken="<<TRACING-SHIPPING-TOKEN>>" \
---set logzio-k8s-telemetry.secrets.LogzioRegion="<<logzio_account_region_code>>" \
+--set logzio-k8s-telemetry.secrets.LogzioRegion="<<LOGZIO_ACCOUNT_REGION_CODE>>" \
 --set logzio-k8s-telemetry.secrets.env_id="<<CLUSTER-NAME>>" \
 --set logzio-k8s-telemetry.spm.enabled=true \
 --set logzio-k8s-telemetry.secrets.SpmToken=<<SPM-METRICS-SHIPPING-TOKEN>> \
@@ -263,7 +263,7 @@ helm install -n monitoring \
 --set logzio-k8s-telemetry.secrets.p8s_logzio_name="<<CLUSTER-NAME>>" \
 --set logzio-k8s-telemetry.traces.enabled=true \
 --set logzio-k8s-telemetry.secrets.TracesToken="<<TRACING-SHIPPING-TOKEN>>" \
---set logzio-k8s-telemetry.secrets.LogzioRegion="<<logzio_account_region_code>>" \
+--set logzio-k8s-telemetry.secrets.LogzioRegion="<<LOGZIO_ACCOUNT_REGION_CODE>>" \
 logzio-monitoring logzio-helm/logzio-monitoring
 ```
 
@@ -276,7 +276,7 @@ logzio-monitoring logzio-helm/logzio-monitoring
 | `<<CLUSTER-NAME>>` | The name for your environment's identifier, to easily identify the telemetry data for each environment. |
 | `<<ENV-TAG>>` | Your custom name for the environment's metrics, to easily identify the metrics for each environment. |
 | `<<TRACING-SHIPPING-TOKEN>>` | Replace `<<TRACING-SHIPPING-TOKEN>>` with the [token](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping?product=tracing) of the account you want to ship to. |
-| `<<logzio_account_region_code>>` | Name of your Logz.io traces region e.g `us` or `eu`. You can find your region code in the [Regions and URLs](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/#regions-and-urls/) table. |
+| `<<LOGZIO_ACCOUNT_REGION_CODE>>` | Name of your Logz.io traces region e.g `us` or `eu`. You can find your region code in the [Regions and URLs](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/#regions-and-urls/) table. |
 
 ## Handling image pull rate limit
 

docs/_include/tracing-shipping/collector-config.md

@@ -10,11 +10,10 @@ receivers:
 exporters:
   logzio/traces:
     account_token: "<<TRACING-SHIPPING-TOKEN>>"
-    region: "<<logzio_account_region_code>>"
+    region: "<<LOGZIO_ACCOUNT_REGION_CODE>>"
     headers:
       user-agent: logzio-opentelemetry-traces
 
-
   logging:
 
 processors:

docs/_include/tracing-shipping/docker.md

@@ -21,11 +21,10 @@ receivers:
 exporters:
   logzio/traces:
     account_token: "<<TRACING-SHIPPING-TOKEN>>"
-    region: "<<logzio_account_region_code>>"
+    region: "<<LOGZIO_ACCOUNT_REGION_CODE>>"
     headers:
       user-agent: logzio-opentelemetry-traces
 
-
   logging:
 
 processors:
@@ -82,7 +81,7 @@ If you already have an OpenTelemetry installation, add the following parameters
 ```yaml
   logzio/traces:
     account_token: <<TRACING-SHIPPING-TOKEN>>
-    region: <<logzio_account_region_code>>
+    region: <<LOGZIO_ACCOUNT_REGION_CODE>>
     headers:
       user-agent: logzio-opentelemetry-traces
 ```
@@ -113,7 +112,7 @@ receivers:
 exporters:
   logzio/traces:
     account_token: "<<TRACING-SHIPPING-TOKEN>>"
-    region: "<<logzio_account_region_code>>"
+    region: "<<LOGZIO_ACCOUNT_REGION_CODE>>"
     headers:
       user-agent: logzio-opentelemetry-traces
 

docs/_include/tracing-shipping/replace-tracing-token-prefix.html

@@ -1,4 +1,4 @@
 Replace `<<TRACING-SHIPPING-TOKEN>>` with the [token](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping?product=tracing) of the account you want to ship to.
 
-Replace `<logzio_account_region_code_PREFIX>` with the prefix of the applicable [region code](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/#available-regions). For example, `us` for `us-east-1`.
+Replace `<LOGZIO_ACCOUNT_REGION_CODE_PREFIX>` with the prefix of the applicable [region code](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/#available-regions). For example, `us` for `us-east-1`.
 

docs/_include/tracing-shipping/replace-tracing-token.html

@@ -1,4 +1,4 @@
 Replace `<<TRACING-SHIPPING-TOKEN>>` with the [token](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping?product=tracing) of the account you want to ship to.
 
-Replace `<logzio_account_region_code>` with the applicable [region code](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/#available-regions).
+Replace `<LOGZIO_ACCOUNT_REGION_CODE>` with the applicable [region code](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/#available-regions).
 

docs/_include/tracing-shipping/replace-tracing-token.md

@@ -1,3 +1,3 @@
 Replace `<<TRACING-SHIPPING-TOKEN>>` with the [token](https://app.logz.io/#/dashboard/settings/manage-tokens/data-shipping?product=tracing) of the account you want to ship to.
 
-Replace `<<logzio_account_region_code>>` with the applicable [region code](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/#available-regions).
+Replace `<<LOGZIO_ACCOUNT_REGION_CODE>>` with the applicable [region code](https://docs.logz.io/docs/user-guide/admin/hosting-regions/account-region/#available-regions).