diff --git a/docs/docs/examples-tutorials/recipes/running-tracetest-with-sumologic.mdx b/docs/docs/examples-tutorials/recipes/running-tracetest-with-sumologic.mdx
index a5aa26b8df..d1b9f845a8 100644
--- a/docs/docs/examples-tutorials/recipes/running-tracetest-with-sumologic.mdx
+++ b/docs/docs/examples-tutorials/recipes/running-tracetest-with-sumologic.mdx
@@ -17,10 +17,6 @@ keywords:
 image: https://res.cloudinary.com/djwdcmwdz/image/upload/v1698686403/docs/Blog_Thumbnail_14_rsvkmo.jpg
 ---
 
-import Tabs from '@theme/Tabs';
-import TabItem from '@theme/TabItem';
-import CodeBlock from '@theme/CodeBlock';
-
 :::note
 [Check out the source code on GitHub here.](https://github.com/kubeshop/tracetest/tree/main/examples/quick-start-sumologic-nodejs)
 :::
@@ -33,19 +29,13 @@ import CodeBlock from '@theme/CodeBlock';
 
 This is a simple quick start on how to configure a Node.js app to use OpenTelemetry instrumentation with traces and Tracetest for enhancing your E2E and integration tests with trace-based testing. The infrastructure will use Sumo Logic as the trace data store, and the Sumo Logic distribution of OpenTelemetry Collector to receive traces from the Node.js app and send them to Sumo Logic.
 
-```mdx-code-block
-<Tabs groupId="running-tracetest-without-a-trace-data-store">
-  <TabItem value="Tracetest" label="Cloud-based Managed Tracetest" default>
-```
 
 ## Prerequisites
 
 **Tracetest Account**:
 
 - Sign up to [`app.tracetest.io`](https://app.tracetest.io) or follow the [get started](/getting-started/installation) docs.
-- Create an [environment](/concepts/environments).
-- Create an [environment token](/concepts/environment-tokens).
-- Have access to the environment's [agent API key](/configuration/agent).
+- Have access to the environment's [agent API key](https://app.tracetest.io/retrieve-token).
 
 **Sumo Logic Account**:
 
@@ -69,17 +59,17 @@ cd tracetest/examples/quick-start-sumologic-nodejs
 Follow these instructions to run the quick start:
 
 1. Copy the `.env.template` file to `.env`.
-2. Log into the [Tracetest app](https://app.tracetest.io/).
-3. Fill out the [token](https://docs.tracetest.io/concepts/environment-tokens) and [API key](https://docs.tracetest.io/concepts/agent) details by editing your `.env` file. You can find these values in the Settings area for your environment.
-4. Run `docker compose up -d`.
-5. This example is configured to use the Sumo Logic Tracing Backend. Ensure the environment you're using to run this example is configured to use the Sumo Logic Tracing Backend by clicking on Settings, Tracing Backend, Sumo Logic, Save. Or, use the CLI as explained below.
-6. Run tests from the Tracetest Web UI by accessing the app with the URL `http://app:8080/`.
+2. Fill out the [TRACETEST_TOKEN and ENVIRONMENT_ID](https://app.tracetest.io/retrieve-token) details by editing your `.env` file.
+4. Fill out the [SUMOLOGIC_INSTALLATION_TOKEN](# https://help.sumologic.com/docs/manage/security/installation-tokens/), [SUMO_LOGIC_ACCESS_ID and SUMO_LOGIC_ACCESS_KEY](https://help.sumologic.com/docs/manage/security/access-keys/#create-an-access-key) details by editing your `.env` file.
+3. Run `docker compose run tracetest-run`.
+4. Follow the links in the output to view the test results.
+
 
 Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works.
 
 ## Project Structure
 
-The project contains [Tracetest Agent](/getting-started/installation#install-the-tracetest-agent), [Sumo Logic OpenTelemetry Collector](https://github.com/SumoLogic/sumologic-otel-collector/tree/main), and a Node.js app.
+The project contains [Tracetest Agent](/getting-started/installation#install-the-tracetest-agent), [OpenTelemetry Collector](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main), and a Node.js app.
 
 The `docker-compose.yaml` file in the root directory of the quick start runs the Node.js app and the [Tracetest Agent](/concepts/agent) setup.
 
@@ -90,7 +80,18 @@ The Node.js app is a simple Express app, contained in the `app.js` file.
 Configure the `.env` like shown below.
 
 ```bash
-TRACETEST_API_KEY="<YOUR_TRACETEST_API_KEY>"
+# Get the required information here: https://app.tracetest.io/retrieve-token
+
+TRACETEST_TOKEN="<YOUR_TRACETEST_TOKEN>"
+TRACETEST_ENVIRONMENT_ID="<YOUR_ENV_ID>"
+
+# https://help.sumologic.com/docs/manage/security/installation-tokens/
+SUMOLOGIC_INSTALLATION_TOKEN="<YOUR_SUMOLOGIC_INSTALLATION_TOKEN>"
+
+# https://help.sumologic.com/docs/manage/security/access-keys/#create-an-access-key
+SUMO_LOGIC_ACCESS_ID="<YOUR_SUMO_LOGIC_ACCESS_ID>"
+SUMO_LOGIC_ACCESS_KEY="<YOUR_SUMO_LOGIC_ACCESS_KEY>"
+
 ```
 
 The OpenTelemetry tracing is contained in the `tracing.otel.grpc.js` or `tracing.otel.http.js` files.
@@ -105,48 +106,6 @@ Enabling the tracer is done by preloading the trace file. As seen in the `packag
 },
 ```
 
-## Configuring Sumo Logic
-
-Configure the `.env` like shown below.
-
-```bash
-SUMOLOGIC_INSTALLATION_TOKEN="<YOUR_SUMOLOGIC_INSTALLATION_TOKEN>"
-```
-
-:::note Configure Sumo Logic Installation Token
-View the [Sumo Logic docs here](https://help.sumologic.com/docs/manage/security/installation-tokens/) to learn more about installation tokens.
-:::
-
-Configure Sumo Logic as a Tracing Backend:
-
-```yaml title=tracetest.datastore.yaml
----
-type: DataStore
-spec:
-  name: Sumo Logic
-  type: sumologic
-  sumologic:
-    # The URL will differ based on your location. View this
-    # docs page to figure out which URL you need:
-    # https://help.sumologic.com/docs/api/getting-started/#which-endpoint-should-i-should-use
-    url: "https://api.sumologic.com/api/"
-    # Create your ID and Key under Administration > Security > Access Keys
-    # in your Sumo Logic account:
-    # https://help.sumologic.com/docs/manage/security/access-keys/#create-your-access-key
-    accessID: "your-access-id"
-    accessKey: "your-access-key"
-```
-
-:::note Configure Sumo Logic API and Access
-- Your Sumo Logic URL will differ based on which region you are using. [Here's a guide which Sumo Logic API endpoint to use](https://help.sumologic.com/docs/api/getting-started/#which-endpoint-should-i-should-use).
-- [Create your ID and Key under Administration > Security > Access Keys in your Sumo Logic account](https://help.sumologic.com/docs/manage/security/access-keys/#create-your-access-key).
-:::
-
-```bash
-tracetest config -t <YOUR_API_TOKEN>
-tracetest apply datastore -f ./tracetest.datastore.yaml
-```
-
 ## Run the Node.js App and Sumo Logic OpenTelemetry Collector with Docker Compose
 
 The [`docker-compose.yaml` file](https://github.com/kubeshop/tracetest/blob/main/examples/quick-start-sumologic-nodejs/docker-compose.yaml) and [`Dockerfile`](https://github.com/kubeshop/tracetest/blob/main/examples/quick-start-sumologic-nodejs/Dockerfile) in the root directory are for the Node.js app.
@@ -158,291 +117,20 @@ And, the `docker-compose.yaml` contains one service for the Node.js app, one ser
 To start it, run this command:
 
 ```bash
-docker compose up -d
+docker compose run tracetest-run
 ```
 
 This will start the Node.js app and Sumo Logic OpenTelemetry Collector and send the traces to Sumo Logic.
 
 ## Run Tracetest Tests
 
-1. Open [Tracetest](https://app.tracetest.io/)
-2. [Configure Sumo Logic as a tracing backend](/configuration/connecting-to-data-stores/sumologic) if you have not already as explained above.
-3. Start creating tests! Make sure to use the `http://app:8080/` URL in your test creation. 
-4. To trigger tests in the CLI, first [install the CLI](/cli/cli-installation-reference), [configure it](/cli/configuring-your-cli), and [run a test](/cli/running-tests). From the root of the quick start directory, run:
-
-```bash
-tracetest configure -t <YOUR_API_TOKEN>
-tracetest run test -f ./test-api.yaml
-```
+This will:
+1. Start the Node.js app, the OpenTelemetry Collector, and send the traces to Sumo Logic.
+2. Start the Tracetest Agent.
+3. Configure the tracing backend and create tests in your environment.
+4. Run the tests.
 
-```mdx-code-block
-  </TabItem>
-  <TabItem value="Tracetest Core" label="Hobby Open-Source Tracetest Core">
-```
-
-## Prerequisites
-
-You will need [Docker](https://docs.docker.com/get-docker/) and [Docker Compose](https://docs.docker.com/compose/install/) installed on your machine to run this quick start app!
-
-## Project Structure
-
-The project is built with Docker Compose. It contains two distinct `docker-compose.yaml` files.
-
-### 1. Node.js App
-The `docker-compose.yaml` file and `Dockerfile` in the root directory are for the Node.js app.
-
-### 2. Tracetest Core
-The `docker-compose.yaml` file, `tracetest-provision.yaml`, and `tracetest.config.yaml` in the `tracetest` directory are for the setting up Tracetest.
-
-The `tracetest` directory is self-contained and will run all the prerequisites for enabling trace-based testing with Tracetest.
-
-### Docker Compose Network
-All `services` in the `docker-compose.yaml` are on the same network and will be reachable by hostname from within other services. E.g. `app:8080` will map to the `app` service.
-
-## Node.js App
-
-The Node.js app is a simple Express app, contained in the `app.js` file.
-
-The OpenTelemetry tracing is contained in the `tracing.otel.grpc.js` or `tracing.otel.http.js` files.
-Traces will be sent to the OpenTelemetry Collector.
-
-Here's the content of the `tracing.otel.grpc.js` file:
-
-```js
-const opentelemetry = require('@opentelemetry/sdk-node')
-const { getNodeAutoInstrumentations } = require('@opentelemetry/auto-instrumentations-node')
-const { OTLPTraceExporter } = require('@opentelemetry/exporter-trace-otlp-grpc');
-
-const sdk = new opentelemetry.NodeSDK({
-  // OTEL_EXPORTER_OTLP_TRACES_ENDPOINT is passed into "new OTLPTraceExporter" automatically
-  traceExporter: new OTLPTraceExporter(),
-  instrumentations: [getNodeAutoInstrumentations()],
-})
-sdk.start()
-```
-
-Choosing the `tracing.otel.grpc.js` file will send traces to Tracetest Agent's `GRPC`.
-
-Configure it an environment variable:
-- Running in Docker: `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://otel-collector:4317`
-
-```bash
-node -r ./tracing.otel.grpc.js app.js
-```
-
-In the `package.json` you will see two npm scripts for running the respective tracers alongside the `app.js`.
-
-```json
-"scripts": {
-  "with-grpc-tracer":"node -r ./tracing.otel.grpc.js app.js",
-  "with-http-tracer":"node -r ./tracing.otel.http.js app.js"
-},
-```
-
-To start the server, run this command:
-
-```bash
-npm run with-grpc-tracer
-# or
-npm run with-http-tracer
-```
-
-As you can see, the `Dockerfile` uses the command above.
-
-```Dockerfile
-FROM node:slim
-WORKDIR /usr/src/app
-COPY package*.json ./
-RUN npm install
-COPY . .
-EXPOSE 8080
-CMD [ "npm", "run", "with-grpc-tracer" ]
-```
-
-And, the `docker-compose.yaml` contains one service for the Node.js app and one service for the Sumo Logic OpenTelemetry Collector.
-
-```yaml
-version: '3'
-services:
-  app:
-    image: quick-start-nodejs
-    extra_hosts:
-      - "host.docker.internal:host-gateway"
-    build: .
-    ports:
-      - "8080:8080"
-    environment:
-      - OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://otel-collector:4317
-
-  otel-collector:
-    image: public.ecr.aws/sumologic/sumologic-otel-collector:0.75.0-sumo-0
-    volumes:
-      - ./collector.config.yaml:/etc/otel/config.yaml
-```
-
-Traces sent to Sumo Logic from the OpenTelemetry Collector.
-
-The `collector.config.yaml` configures the OpenTelemetry Collector. It receives traces via either `grpc` or `http`. Then, exports them to Sumo Logic via the Sumo Logic `extension` and an `installation_token`. 
-
-:::note Configure Sumo Logic Installation Token
-View the [Sumo Logic docs here](https://help.sumologic.com/docs/manage/security/installation-tokens/) to learn more about installation tokens.
-:::
-
-```yaml title="collector.config.yaml"
-receivers:
-  otlp:
-    protocols:
-      grpc:
-      http:
-
-exporters:
-  sumologic:
-
-extensions:
-  sumologic:
-    installation_token: <your-sumologic-installation-token>
-
-service:
-  extensions: [sumologic]
-  pipelines:
-    traces:
-      receivers: [otlp]
-      exporters: [sumologic]
-```
-
-To start it, run this command:
-
-```bash
-docker compose build # optional if you haven't already built the image
-docker compose up
-```
-
-This will start the Node.js app and Sumo Logic OpenTelemetry Collector and send the traces to Sumo Logic.
-
-Let's add trace-based testing by configuring Tracetest.
-
-## Tracetest Core
-
-The `docker-compose.yaml` in the `tracetest` directory is configured with two services.
-
-- **Postgres** - Postgres is a prerequisite for Tracetest to work. It stores trace data when running the trace-based tests.
-- [**Tracetest Core**](https://github.com/kubeshop/tracetest) - Trace-based testing that generates end-to-end tests automatically from traces.
-
-```yaml title="./tracetest/docker-compose.yaml"
-version: "3"
-services:
-  tracetest:
-    image: kubeshop/tracetest:latest
-    platform: linux/amd64
-    volumes:
-      - type: bind
-        source: ./tracetest/tracetest-config.yaml
-        target: /app/tracetest.yaml
-      - type: bind
-        source: ./tracetest/tracetest-provision.yaml
-        target: /app/provisioning.yaml
-    ports:
-      - 11633:11633
-    command: --provisioning-file /app/provisioning.yaml
-    depends_on:
-      postgres:
-        condition: service_healthy
-      otel-collector:
-        condition: service_started
-    healthcheck:
-      test: ["CMD", "wget", "--spider", "localhost:11633"]
-      interval: 1s
-      timeout: 3s
-      retries: 60
-
-  postgres:
-    image: postgres:14
-    environment:
-      POSTGRES_PASSWORD: postgres
-      POSTGRES_USER: postgres
-    healthcheck:
-      test: pg_isready -U "$$POSTGRES_USER" -d "$$POSTGRES_DB"
-      interval: 1s
-      timeout: 5s
-      retries: 60
-
-```
-
-Tracetest Core depends on both Postgres and the Sumo Logic OpenTelemetry Collector from the root `docker-compose.yaml`. Tracetest Core requires config files to be loaded via a volume. The volumes are mapped from the root directory into the `tracetest` directory and the respective config files.
-
-To start both the Node.js app and Tracetest Core we will run this command:
-
-```bash
-docker-compose -f docker-compose.yaml -f tracetest/docker-compose.yaml build
-docker-compose -f docker-compose.yaml -f tracetest/docker-compose.yaml up
-```
-
-The `tracetest-config.yaml` file contains the basic setup of connecting Tracetest Core to the Postgres instance.
-
-```yaml title="tracetest-config.yaml"
-postgres:
-  host: postgres
-  user: postgres
-  password: postgres
-  port: 5432
-  dbname: postgres
-  params: sslmode=disable
-
-```
-
-The `tracetest-provision.yaml` file provisions the trace data store and polling to store in the Postgres database. The data store is set to Sumo Logic, meaning the Tracetest Core will fetch traces from Sumo Logic when tests are run.
-
-You'll need to set Sumo Logic:
-
-- URL
-- Access ID
-- Access Key
-
-:::note Configure Sumo Logic API and Access
-- Your Sumo Logic URL will differ based on which region you are using. [Here's a guide which Sumo Logic API endpoint to use](https://help.sumologic.com/docs/api/getting-started/#which-endpoint-should-i-should-use).
-- [Create your ID and Key under Administration > Security > Access Keys in your Sumo Logic account](https://help.sumologic.com/docs/manage/security/access-keys/#create-your-access-key).
-- View the [Sumo Logic configuration docs](/configuration/connecting-to-data-stores/sumologic) for guidance.
-:::
-
-```yaml title="tracetest-provision.yaml"
----
-type: PollingProfile
-spec:
-  name: Default
-  strategy: periodic
-  default: true
-  periodic:
-    retryDelay: 5s
-    timeout: 10m
-
----
-type: DataStore
-spec:
-  name: Sumo Logic
-  type: sumologic
-  sumologic:
-    url: "https://api.sumologic.com/api/"
-    accessID: "your-access-id"
-    accessKey: "your-access-key"    
-```
-
-## Run Both the Node.js App and Tracetest
-
-To start both the Node.js app and Tracetest, run this command:
-
-```bash
-docker-compose -f docker-compose.yaml -f tracetest/docker-compose.yaml build
-docker-compose -f docker-compose.yaml -f tracetest/docker-compose.yaml up
-```
-
-This will start your Tracetest Core instance on `http://localhost:11633/`.
-
-Open the URL and start creating tests! Make sure to use the `http://app:8080/` URL in your test creation, because your Node.js app and Tracetest Core are in the same network.
-
-```mdx-code-block
-  </TabItem>
-</Tabs>
-```
+Open the URL and start creating tests! Make sure to use the `http://app:8080/` URL in your test creation, because your Node.js app and Tracetest are in the same network.
 
 ## Learn More
 
diff --git a/examples/quick-start-sumologic-nodejs/.env.template b/examples/quick-start-sumologic-nodejs/.env.template
index bfd5627fd2..51ce4ca278 100644
--- a/examples/quick-start-sumologic-nodejs/.env.template
+++ b/examples/quick-start-sumologic-nodejs/.env.template
@@ -1,3 +1,11 @@
-TRACETEST_API_KEY="<YOUR_TRACETEST_API_KEY>"
-TRACETEST_API_TOKEN="<YOUR_TRACETEST_TOKEN>"
+# Get the required information here: https://app.tracetest.io/retrieve-token
+
+TRACETEST_TOKEN="<YOUR_TRACETEST_TOKEN>"
+TRACETEST_ENVIRONMENT_ID="<YOUR_ENV_ID>"
+
+# https://help.sumologic.com/docs/manage/security/installation-tokens/
 SUMOLOGIC_INSTALLATION_TOKEN="<YOUR_SUMOLOGIC_INSTALLATION_TOKEN>"
+
+# https://help.sumologic.com/docs/manage/security/access-keys/#create-an-access-key
+SUMO_LOGIC_ACCESS_ID="<YOUR_SUMO_LOGIC_ACCESS_ID>"
+SUMO_LOGIC_ACCESS_KEY="<YOUR_SUMO_LOGIC_ACCESS_KEY>"
diff --git a/examples/quick-start-sumologic-nodejs/.gitignore b/examples/quick-start-sumologic-nodejs/.gitignore
index d8f337266f..910e5485fe 100644
--- a/examples/quick-start-sumologic-nodejs/.gitignore
+++ b/examples/quick-start-sumologic-nodejs/.gitignore
@@ -1,3 +1,4 @@
 node_modules
 .DS_Store
 .env
+resources/datastore.yaml
diff --git a/examples/quick-start-sumologic-nodejs/Dockerfile.tracetest b/examples/quick-start-sumologic-nodejs/Dockerfile.tracetest
new file mode 100644
index 0000000000..883f239155
--- /dev/null
+++ b/examples/quick-start-sumologic-nodejs/Dockerfile.tracetest
@@ -0,0 +1,11 @@
+FROM alpine
+
+WORKDIR /app
+ARG TRACETEST_IMAGE_VERSION=v1.4.0
+
+RUN apk --update add bash jq curl
+RUN curl -L https://raw.githubusercontent.com/kubeshop/tracetest/main/install-cli.sh | bash -s -- $TRACETEST_IMAGE_VERSION
+
+WORKDIR /resources
+
+ENTRYPOINT ["echo", "Tracetest CLI installed"]
diff --git a/examples/quick-start-sumologic-nodejs/docker-compose.yaml b/examples/quick-start-sumologic-nodejs/docker-compose.yaml
index c7d33edf18..912f9d2cf6 100644
--- a/examples/quick-start-sumologic-nodejs/docker-compose.yaml
+++ b/examples/quick-start-sumologic-nodejs/docker-compose.yaml
@@ -10,6 +10,9 @@ services:
       - OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://otel-collector:4317
       # HTTP
       # - OTEL_EXPORTER_OTLP_TRACES_ENDPOINT=http://otel-collector:4318/v1/traces
+    depends_on:
+      otel-collector:
+          condition: service_started
 
   otel-collector:
     image: public.ecr.aws/sumologic/sumologic-otel-collector:0.75.0-sumo-0
@@ -23,5 +26,44 @@ services:
   tracetest-agent:
     image: kubeshop/tracetest-agent:latest
     environment:
-      # Find the Agent API Key here: https://docs.tracetest.io/configuration/agent
-      - TRACETEST_API_KEY=${TRACETEST_API_KEY}
+      # Get the required information here: https://app.tracetest.io/retrieve-token
+      - TRACETEST_API_KEY=${TRACETEST_TOKEN}
+      - TRACETEST_ENVIRONMENT_ID=${TRACETEST_ENVIRONMENT_ID}
+  
+  tracetest-apply:
+    build:
+      dockerfile: Dockerfile.tracetest
+    volumes:
+      - ./resources:/resources
+    environment:
+      TRACETEST_TOKEN: ${TRACETEST_TOKEN}
+      TRACETEST_ENVIRONMENT_ID: ${TRACETEST_ENVIRONMENT_ID}
+      SUMO_LOGIC_ACCESS_ID: ${SUMO_LOGIC_ACCESS_ID}
+      SUMO_LOGIC_ACCESS_KEY: ${SUMO_LOGIC_ACCESS_KEY}
+    entrypoint:
+      - bash
+      - /resources/apply.sh
+    networks:
+      default: null
+    depends_on:
+      app:
+        condition: service_started
+      tracetest-agent:
+        condition: service_started
+
+  tracetest-run:
+    build:
+      dockerfile: Dockerfile.tracetest
+    volumes:
+      - ./resources:/resources
+    environment:
+      TRACETEST_TOKEN: ${TRACETEST_TOKEN}
+      TRACETEST_ENVIRONMENT_ID: ${TRACETEST_ENVIRONMENT_ID}
+    entrypoint:
+      - bash
+      - /resources/run.sh
+    networks:
+      default: null
+    depends_on:
+      tracetest-apply:
+        condition: service_completed_successfully
\ No newline at end of file
diff --git a/examples/quick-start-sumologic-nodejs/tracetest.datastore.yaml b/examples/quick-start-sumologic-nodejs/resources/apply.sh
similarity index 51%
rename from examples/quick-start-sumologic-nodejs/tracetest.datastore.yaml
rename to examples/quick-start-sumologic-nodejs/resources/apply.sh
index 89fb42fafe..022231da8e 100644
--- a/examples/quick-start-sumologic-nodejs/tracetest.datastore.yaml
+++ b/examples/quick-start-sumologic-nodejs/resources/apply.sh
@@ -1,3 +1,17 @@
+#!/bin/sh
+
+set -e
+
+TOKEN=$TRACETEST_TOKEN
+ENVIRONMENT_ID=$TRACETEST_ENVIRONMENT_ID
+ACCESS_ID=$SUMO_LOGIC_ACCESS_ID
+ACCESS_KEY=$SUMO_LOGIC_ACCESS_KEY
+
+apply() {
+  echo "Configuring TraceTest"
+  tracetest configure --token $TOKEN --environment $ENVIRONMENT_ID
+
+  echo "
 ---
 type: DataStore
 spec:
@@ -12,5 +26,13 @@ spec:
     # Create your ID and Key under Administration > Security > Access Keys
     # in your Sumo Logic account:
     # https://help.sumologic.com/docs/manage/security/access-keys/#create-your-access-key
-    accessID: "your-access-id"
-    accessKey: "your-access-key"
+    accessID: ${ACCESS_ID}
+    accessKey: ${ACCESS_KEY}
+" > /resources/datastore.yaml
+
+  echo "Applying Resources"
+  tracetest apply datastore -f /resources/datastore.yaml
+  tracetest apply test -f /resources/test.yaml
+}
+
+apply
diff --git a/examples/quick-start-sumologic-nodejs/resources/run.sh b/examples/quick-start-sumologic-nodejs/resources/run.sh
new file mode 100644
index 0000000000..05d0f41724
--- /dev/null
+++ b/examples/quick-start-sumologic-nodejs/resources/run.sh
@@ -0,0 +1,16 @@
+#!/bin/sh
+
+set -e
+
+TOKEN=$TRACETEST_TOKEN
+ENVIRONMENT_ID=$TRACETEST_ENVIRONMENT_ID
+
+run() {
+  echo "Configuring Tracetest"
+  tracetest configure --token $TOKEN --environment $ENVIRONMENT_ID
+
+  echo "Running Trace-Based Tests..."
+  tracetest run test -f /resources/test.yaml
+}
+
+run
diff --git a/examples/quick-start-sumologic-nodejs/test-api.yaml b/examples/quick-start-sumologic-nodejs/resources/test.yaml
similarity index 100%
rename from examples/quick-start-sumologic-nodejs/test-api.yaml
rename to examples/quick-start-sumologic-nodejs/resources/test.yaml
diff --git a/examples/quick-start-sumologic-nodejs/tracetest/docker-compose.yaml b/examples/quick-start-sumologic-nodejs/tracetest/docker-compose.yaml
deleted file mode 100644
index bd8a8fb42c..0000000000
--- a/examples/quick-start-sumologic-nodejs/tracetest/docker-compose.yaml
+++ /dev/null
@@ -1,37 +0,0 @@
-version: "3"
-services:
-  tracetest:
-    image: kubeshop/tracetest:${TAG:-latest}
-    platform: linux/amd64
-    volumes:
-      - type: bind
-        source: ./tracetest/tracetest-config.yaml
-        target: /app/tracetest.yaml
-      - type: bind
-        source: ./tracetest/tracetest-provision.yaml
-        target: /app/provisioning.yaml
-    ports:
-      - 11633:11633
-    command: --provisioning-file /app/provisioning.yaml
-    depends_on:
-      postgres:
-        condition: service_healthy
-      otel-collector:
-        condition: service_started
-    healthcheck:
-      test: ["CMD", "wget", "--spider", "localhost:11633"]
-      interval: 1s
-      timeout: 3s
-      retries: 60
-    environment:
-      TRACETEST_DEV: ${TRACETEST_DEV}
-  postgres:
-    image: postgres:14
-    environment:
-      POSTGRES_PASSWORD: postgres
-      POSTGRES_USER: postgres
-    healthcheck:
-      test: pg_isready -U "$$POSTGRES_USER" -d "$$POSTGRES_DB"
-      interval: 1s
-      timeout: 5s
-      retries: 60
diff --git a/examples/quick-start-sumologic-nodejs/tracetest/tracetest-config.yaml b/examples/quick-start-sumologic-nodejs/tracetest/tracetest-config.yaml
deleted file mode 100644
index 5e732f6d38..0000000000
--- a/examples/quick-start-sumologic-nodejs/tracetest/tracetest-config.yaml
+++ /dev/null
@@ -1,7 +0,0 @@
-postgres:
-  host: postgres
-  user: postgres
-  password: postgres
-  port: 5432
-  dbname: postgres
-  params: sslmode=disable
diff --git a/examples/quick-start-sumologic-nodejs/tracetest/tracetest-provision.yaml b/examples/quick-start-sumologic-nodejs/tracetest/tracetest-provision.yaml
deleted file mode 100644
index 24231f86ca..0000000000
--- a/examples/quick-start-sumologic-nodejs/tracetest/tracetest-provision.yaml
+++ /dev/null
@@ -1,22 +0,0 @@
----
-type: PollingProfile
-spec:
-  name: Default
-  strategy: periodic
-  default: true
-  periodic:
-    retryDelay: 5s
-    timeout: 10m
-
----
-type: DataStore
-spec:
-  name: Sumo Logic
-  type: sumologic
-  sumologic:
-    # The URL will differ based on your location. View this
-    # docs page to figure out which URL you need:
-    # https://help.sumologic.com/docs/api/getting-started/#which-endpoint-should-i-should-use
-    url: "https://api.sumologic.com/api/"
-    accessID: "your-access-id"
-    accessKey: "your-access-key"