feat: update docs to match trace ingestion (#3965)

kubeshop · Aug 14, 2024 · 7f55ed1 · 7f55ed1
1 parent 5de89bf
commit 7f55ed1
Show file tree

Hide file tree

Showing 47 changed files with 61 additions and 67 deletions.
diff --git a/docs/docs/concepts/agent.mdx b/docs/docs/concepts/agent.mdx
@@ -23,13 +23,13 @@ If you have a [publicly accessible application, then view this page](/concepts/c
 
 Go to your Environment Access Settings page.
 
-![Agent Settings](https://res.cloudinary.com/djwdcmwdz/image/upload/v1712586955/docs/app.tracetest.io_organizations_ttorg_2179a9cd8ba8dfa5_environments_ttenv_597cf82c754c2a01_settings_ykn53w.png)
+![Agent Settings](../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=agent.png)
 
-Select **"Application is in a private environment"**. Use the `--api-key` to run the Tracetest Agent in your environment.
+Select **"Application is in a private environment"**. Use the `--api-key` and `--environment` id to run the Tracetest Agent in your environment.
 
-![](https://res.cloudinary.com/djwdcmwdz/image/upload/v1712587335/docs/app.tracetest.io_organizations_ttorg_2179a9cd8ba8dfa5_environments_ttenv_597cf82c754c2a01_settings_1_iumdfz.png)
+![Trace Ingestion Settings](../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore.png)
 
-Configure the tracing backend you're using via the tracing backend tab or use the supplied OTLP endpoints to alter your OpenTelemetry Collector configuration to send trace information via either gRPC or HTTP directly to Tracetest.
+Enable and configure the tracing backend you're using via the trace ingestion tab or use the supplied OTLP endpoints to alter your OpenTelemetry Collector configuration to send trace information via either gRPC or HTTP directly to Tracetest.
 
 ## How It Works
 

diff --git a/docs/docs/concepts/cloud-agent.mdx b/docs/docs/concepts/cloud-agent.mdx
@@ -28,13 +28,13 @@ If you have a [publicly accessible application, then view this page](/concepts/c
 
 Go to your Environment Agent Settings page.
 
-![Agent Settings](https://res.cloudinary.com/djwdcmwdz/image/upload/v1712602150/docs/app.tracetest.io_organizations_ttorg_2179a9cd8ba8dfa5_environments_ttenv_597cf82c754c2a01_settings_2_bs2zc9.png)
+![Agent Settings](../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=agent_1.png)
 
 Select **"Application is publicly accessible"**. This will start an instance of Tracetest Agent in your Tracetest Account.
 
-![](https://res.cloudinary.com/djwdcmwdz/image/upload/v1712602455/docs/app.tracetest.io_organizations_ttorg_2179a9cd8ba8dfa5_environments_ttenv_597cf82c754c2a01_settings_3_xyexhw.png)
+![Trace Ingestion Settings](../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_1.png)
 
-Configure the publicly accessible tracing backend you're using via the tracing backend tab or use the supplied OTLP endpoints to alter your OpenTelemetry Collector configuration to send trace information via either gRPC or HTTP directly to Tracetest.
+Enable and configure the publicly accessible tracing backend you're using via the trace ingestion tab or use the supplied OTLP endpoints to alter your OpenTelemetry Collector configuration to send trace information via either gRPC or HTTP directly to Tracetest.
 
 ## How It Works
 

diff --git a/docs/docs/configuration/agent.mdx b/docs/docs/configuration/agent.mdx
@@ -21,7 +21,7 @@ Tracetest Agent connects to Tracetest via an API Key.
 
 Select `Application is in a private environment`.
 
-![](https://res.cloudinary.com/djwdcmwdz/image/upload/v1712586955/docs/app.tracetest.io_organizations_ttorg_2179a9cd8ba8dfa5_environments_ttenv_597cf82c754c2a01_settings_ykn53w.png)
+![Agent Settings](../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=agent.png)
 
 ## Configure Tracetest Agent
 

diff --git a/docs/docs/configuration/cloud-agent.mdx b/docs/docs/configuration/cloud-agent.mdx
@@ -23,7 +23,7 @@ Tracetest Cloud Agent runs in your Tracetest account.
 
 Select `Application is publicly accessible`.
 
-![](https://res.cloudinary.com/djwdcmwdz/image/upload/v1712602150/docs/app.tracetest.io_organizations_ttorg_2179a9cd8ba8dfa5_environments_ttenv_597cf82c754c2a01_settings_2_bs2zc9.png)
+![Agent Settings](../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=agent_1.png)
 
 ## Configure Tracetest Cloud Agent
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/awsxray.mdx b/docs/docs/configuration/connecting-to-data-stores/awsxray.mdx
@@ -29,9 +29,9 @@ Need help configuring the OpenTelemetry Collector so send trace data from your a
 
 ## Connect Tracetest to X-Ray with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) AWS X-Ray.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) AWS X-Ray.
 
-![AWS X-Ray Settings](../img/configure-awsxray-0.11.3.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_aws.png)
 
 From the configuration page, add your AWS credentials.
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/azure-app-insights.mdx b/docs/docs/configuration/connecting-to-data-stores/azure-app-insights.mdx
@@ -25,9 +25,9 @@ Tracetest uses the Golang [Azure SDK](https://learn.microsoft.com/en-us/azure/de
 
 ### Tracetest Direct Connection to Azure App Insights with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) Azure App Insights.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) Azure App Insights.
 
-![Azure App Insights Direct Connection Settings](../img/appinsights-direct.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_azure_1.png)
 
 From the configuration page, add your [App Insights API Access Token](https://learn.microsoft.com/en-us/azure/azure-monitor/app/app-insights-azure-ad-api). Or if you are running Tracetest from a authorized container, you can use the default Active Directory Authentication.
 
@@ -70,9 +70,9 @@ Need help configuring the [OpenTelemetry Collector](https://github.com/open-tele
 
 ### Tracetest OpenTelemetry Collector connection to Azure App Insights with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) Azure App Insights, (4) Select Open Telemetry Collector as Connection Type.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) Azure App Insights, (4) Select Open Telemetry Collector as Connection Type.
 
-![Azure App Insights Otel Connection Settings](../img/appinsights-otel.png)
+![Trace Ingestion Settings OpenTelemetry Collector](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_azure_2.png)
 
 From the configuration page, copy and customize the OpenTelemetry configuration YAML including the instrumentation key.
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/datadog.mdx b/docs/docs/configuration/connecting-to-data-stores/datadog.mdx
@@ -88,9 +88,9 @@ Configure your Tracetest instance to expose an `otlp` endpoint to make it aware
 
 ## Connect Tracetest to Datadog with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) Datadog.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) Datadog.
 
-![Datadog](../img/configure-datadog-0.11.3.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_datadog.png)
 
 ## Connect Tracetest to Datadog with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/dynatrace.mdx b/docs/docs/configuration/connecting-to-data-stores/dynatrace.mdx
@@ -79,9 +79,9 @@ Configure your Tracetest instance to expose an `otlp` endpoint to make it aware
 
 ## Connect Tracetest to Dynatrace with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) Dynatrace.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) Dynatrace.
 
-![Dynatrace](../img/Dynatrace-settings.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_dynatrace.png)
 
 ## Connect Tracetest to Dynatrace with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/elasticapm.mdx b/docs/docs/configuration/connecting-to-data-stores/elasticapm.mdx
@@ -44,13 +44,13 @@ Need help configuring the OpenTelemetry Collector so send trace data from your a
 
 ## Connect Tracetest to Elastic with the Web UI
 
-In the Web UI, (1) open Settings and, on the (2) Configure Data Store tab, select (3) Elastic APM. If you are using Docker, as in the screenshot below, use the service name as the hostname with port `9200`. Use `http`, or `https` if TLS is enabled.
+In the Web UI, (1) open Settings and, on the (2) Trace Ingestion tab, select (3) Elastic APM. If you are using Docker, as in the screenshot below, use the service name as the hostname with port `9200`. Use `http`, or `https` if TLS is enabled.
 
 ```
 https://es01:9200
 ```
 
-![ElasticAPM](../img/ElasticAPM-settings.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_elastic.png)
 
 ## Connect Tracetest to Elastic with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/honeycomb.mdx b/docs/docs/configuration/connecting-to-data-stores/honeycomb.mdx
@@ -81,9 +81,9 @@ Configure your Tracetest instance to expose an `otlp` endpoint to make it aware
 
 ## Connect Tracetest to Honeycomb with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) Honeycomb.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) Honeycomb.
 
-![Honeycomb](../img/honeycomb-settings.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_honeycomb.png)
 
 ## Connect Tracetest to Honeycomb with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/instana.mdx b/docs/docs/configuration/connecting-to-data-stores/instana.mdx
@@ -89,9 +89,9 @@ Configure your Tracetest instance to expose an `otlp` endpoint to make it aware
 
 ## Connect Tracetest to Instana with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Tracing Backend tab, select (3) Datadog.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) Instana.
 
-![Instana](../img/configure-instana.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_instana.png)
 
 ## Connect Tracetest to Instana with the CLI
 
@@ -110,7 +110,3 @@ Proceed to run this command in the terminal and specify the file above.
 ```bash
 tracetest apply datastore -f my/data-store/file/location.yaml
 ```
-
-{/*
-TODO: when the Instana tutorial is released, add link to learn more here
-*/}
diff --git a/docs/docs/configuration/connecting-to-data-stores/jaeger.mdx b/docs/docs/configuration/connecting-to-data-stores/jaeger.mdx
@@ -29,13 +29,13 @@ Need help configuring the OpenTelemetry Collector so send trace data from your a
 
 ## Connect Tracetest to Jaeger with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, (3) select Jaeger. If you are using Docker like in the screenshot below, use the service name as the hostname with port `16685` like this:
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, (3) select Jaeger. If you are using Docker like in the screenshot below, use the service name as the hostname with port `16685` like this:
 
 ```
 jaeger:16685
 ```
 
-![Jaeger](../img/Jaeger-settings.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_jaeger.png)
 
 ## Connect Tracetest to Jaeger with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/lightstep.mdx b/docs/docs/configuration/connecting-to-data-stores/lightstep.mdx
@@ -84,9 +84,9 @@ Configure your Tracetest instance to expose an `otlp` endpoint to make it aware
 
 ## Connect Tracetest to Lightstep with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) Lightstep.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) Lightstep.
 
-![Lightstep](../img/Lightstep-settings.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_lightstep.png)
 
 ## Connect Tracetest to Lightstep with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/new-relic.mdx b/docs/docs/configuration/connecting-to-data-stores/new-relic.mdx
@@ -86,9 +86,9 @@ Configure your Tracetest instance to expose an `otlp` endpoint to make it aware
 
 ## Connect Tracetest to New Relic with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) New Relic.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) New Relic.
 
-![NewRelic](../img/New-Relic-settings.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_newrelic.png)
 
 ## Connect Tracetest to New Relic with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/opensearch.mdx b/docs/docs/configuration/connecting-to-data-stores/opensearch.mdx
@@ -36,13 +36,13 @@ Need help configuring the OpenTelemetry Collector so send trace data from your a
 
 ## Connect Tracetest to OpenSearch with the Web UI
 
-In the Web UI, (1) open settings, and, on the (2) Configure Data Store tab, select (3) OpenSearch. If you are using Docker like in the screenshot below, use the service name as the hostname with port `9200`. Use `http`, or `https` if TLS is enabled.
+In the Web UI, (1) open settings, and, on the (2) Trace Ingestion tab, select (3) OpenSearch. If you are using Docker like in the screenshot below, use the service name as the hostname with port `9200`. Use `http`, or `https` if TLS is enabled.
 
 ```
 http://opensearch:9200
 ```
 
-![OpenSearch](../img/opensearch-settings.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_opensearch.png)
 
 ## Connect Tracetest to OpenSearch with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/opentelemetry-collector.mdx b/docs/docs/configuration/connecting-to-data-stores/opentelemetry-collector.mdx
@@ -73,10 +73,9 @@ Configure your Tracetest instance to expose an `otlp` endpoint to make it aware
 
 ## Connect Tracetest to OpenTelemetry Collector with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) OpenTelemetry.
-
-![OpenTelemetry](../img/open-telemetry-settings.png)
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) OpenTelemetry.
 
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_otel.png)
 
 ## Connect Tracetest to OpenTelemetry Collector with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/overview.mdx b/docs/docs/configuration/connecting-to-data-stores/overview.mdx
@@ -1,6 +1,6 @@
 ---
 id: overview
-title: Connecting to Tracing Backends
+title: Trace Ingestion
 description: Tracetest allows you to quickly build integration and end-to-end tests, powered by your OpenTelemetry traces. Learn how to connect tracing backends.
 keywords:
   - tracetest
@@ -11,7 +11,7 @@ keywords:
 image: https://res.cloudinary.com/djwdcmwdz/image/upload/v1698686403/docs/Blog_Thumbnail_14_rsvkmo.jpg
 ---
 
-Tracetest supports two types of tracing backend integrations.
+Tracetest allows you to connect your Tracing Backend to unlock the full potential of trace-based testing. Tracetest supports two types of tracing backend integrations.
 
 ## Native Connection (Polling)
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/signalfx.mdx b/docs/docs/configuration/connecting-to-data-stores/signalfx.mdx
@@ -27,7 +27,7 @@ Need help configuring the OpenTelemetry Collector so send trace data from your a
 
 ## Connect Tracetest to SignalFx with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, (3) select SignalFx.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, (3) select SignalFx.
 
 You need your SignalFx:
 
@@ -36,8 +36,7 @@ You need your SignalFx:
 
 Follow this [guide](https://docs.splunk.com/Observability/references/organizations.html).
 
-![SignalFX](../img/SignalFX-settings.png)
-
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_signal.png)
 
 ## Connect Tracetest to SignalFx with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/signoz.mdx b/docs/docs/configuration/connecting-to-data-stores/signoz.mdx
@@ -79,9 +79,9 @@ Configure your Tracetest instance to expose an `otlp` endpoint to make it aware
 
 ## Connect Tracetest to SigNoz with the Web UI
 
-In the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, select (3) SigNoz.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, select (3) SigNoz.
 
-![SigNoz](../img/Signoz-settings.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_signoz.png)
 
 ## Connect Tracetest to SigNoz with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/sumologic.mdx b/docs/docs/configuration/connecting-to-data-stores/sumologic.mdx
@@ -31,9 +31,9 @@ Need help configuring the OpenTelemetry Collector so send trace data from your a
 
 ## Connect Tracetest to Sumo Logic with the Web UI
 
-In the Web UI, (1) open Settings and, on the (2) Configure Data Store tab, select (3) Sumo Logic. Add the Sumo Logic **API**, your **Access ID**, and **Access Key**.
+In the Web UI, (1) open Settings and, on the (2) Trace Ingestion tab, select (3) Sumo Logic. Add the Sumo Logic **API**, your **Access ID**, and **Access Key**.
 
-![sumo logic](../img/sumologic-settings.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_sumologic.png)
 
 ## Connect Tracetest to Sumo Logic with the CLI
 

diff --git a/docs/docs/configuration/connecting-to-data-stores/tempo.mdx b/docs/docs/configuration/connecting-to-data-stores/tempo.mdx
@@ -79,23 +79,23 @@ Need help configuring the OpenTelemetry Collector so send trace data from your a
 
 ## Connect Tracetest to Tempo with the Web UI
 
-IIn the Web UI, (1) open Settings, and, on the (2) Configure Data Store tab, (3) select Tempo. Then, select either `gRPC` or `HTTP`.
+In the Web UI, (1) open Settings, and, on the (2) Trace Ingestion tab, (3) select Tempo. Then, select either `gRPC` or `HTTP`.
 
 If you are using Docker and the `gRPC` endpoint like in the screenshot below, use the service name as the hostname with port `9095` like this:
 
 ```
 tempo:9095
 ```
 
-![tempo grpc](https://res.cloudinary.com/djwdcmwdz/image/upload/v1710422510/docs/app.tracetest.io_organizations_ttorg_e66318ba6544b856_environments_ttenv_ad034a744607c050_settings_tab_agent_1_fc2ccz.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_tempo.png)
 
 If you are using Docker and the `HTTP` URL like in the screenshot below, use the service name as the hostname with port `80` or no specified port like this:
 
 ```
 http://tempo
 ```
 
-![Tempo http](https://res.cloudinary.com/djwdcmwdz/image/upload/v1710422502/docs/app.tracetest.io_organizations_ttorg_e66318ba6544b856_environments_ttenv_ad034a744607c050_settings_tab_agent_gqqnjy.png)
+![Trace Ingestion Settings](../../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_tempo_1.png)
 
 ## Connect Tracetest to Tempo with the CLI
 

diff --git a/...anizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=agent.png b/...anizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=agent.png
diff --git a/...izations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=agent_1.png b/...izations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=agent_1.png
diff --git a/...ations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore.png b/...ations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore.png
diff --git a/...ions_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_1.png b/...ions_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_1.png
diff --git a/...ns_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_aws.png b/...ns_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_aws.png
diff --git a/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_azure_1.png b/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_azure_1.png
diff --git a/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_azure_2.png b/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_azure_2.png
diff --git a/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_datadog.png b/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_datadog.png
diff --git a/...CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_dynatrace.png b/...CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_dynatrace.png
diff --git a/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_elastic.png b/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_elastic.png
diff --git a/...CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_honeycomb.png b/...CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_honeycomb.png
diff --git a/...at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_how_to.png b/...at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_how_to.png
diff --git a/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_instana.png b/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_instana.png
diff --git a/...at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_jaeger.png b/...at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_jaeger.png
diff --git a/...CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_lightstep.png b/...CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_lightstep.png
diff --git a/...4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_newrelic.png b/...4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_newrelic.png
diff --git a/...xvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_opensearch.png b/...xvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_opensearch.png
diff --git a/...s_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_otel.png b/...s_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_otel.png
diff --git a/...at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_signal.png b/...at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_signal.png
diff --git a/...at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_signoz.png b/...at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_signoz.png
diff --git a/...CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_sumologic.png b/...CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_sumologic.png
diff --git a/..._at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_tempo.png b/..._at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_tempo.png
diff --git a/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_tempo_1.png b/...t4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_tempo_1.png
diff --git a/..._environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_test_connection.png b/..._environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_test_connection.png
diff --git a/docs/docs/web-ui/creating-data-stores.mdx b/docs/docs/web-ui/creating-data-stores.mdx
@@ -1,6 +1,6 @@
 ---
 id: creating-data-stores
-title: Configuring Data Stores
+title: Configuring Trace Ingestion
 description: Tracetest enables configuring data stores visually in the Tracetest Web UI.
 hide_table_of_contents: false
 keywords:
@@ -12,16 +12,16 @@ keywords:
 image: https://res.cloudinary.com/djwdcmwdz/image/upload/v1698686403/docs/Blog_Thumbnail_14_rsvkmo.jpg
 ---
 
-This page shows how to configure data stores in the Tracetest Web UI.
+This page shows how to configure tracing backends in the Tracetest Web UI.
 
-Open the **settings** and select the **Configure Data Store** tab.
+Open the **Settings** page and select the **Trace Ingestion** tab.
 
-![](https://res.cloudinary.com/djwdcmwdz/image/upload/v1685971832/docs/Jaeger-settings-1477bdfe17b0675850681e0cfb85859a_ziy7un.png)
+![Trace Ingestion Settings](../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_how_to.png)
 
-To help you configure the connection, you can use the **Test Connection** button to validate if the connection is successful and Tracetest can fetch traces from the data store.
+To help you configure the connection, you can use the **Test Connection** button to validate if the connection is successful and Tracetest can fetch traces from the tracing backend.
 
-![](https://res.cloudinary.com/djwdcmwdz/image/upload/v1685972024/docs/demo.tracetest.io_transaction_QZ3ejgl4R_run_2_3_wrwikl.png)
+![Trace Ingestion Settings](../img/08132024/app.tracetest.io_organizations_at4CxvjIg_environments_ttenv_172de56e3dcbba9b_settings_tab=dataStore_test_connection.png)
 
-## Supported Trace Data Stores
+## Supported Tracing Backends
 
-Select from the [list of available data stores](/configuration/overview) and configure the connection.
+Select from the [list of available tracing backends](/configuration/overview) and configure the connection.