### Run Full Example Commands

Source: https://docs.tracetest.io/tools-and-integrations/artillery-plugin

Commands to run the full example setup, including starting Docker Compose and executing the Artillery plugin test.

```bash
docker compose up -d  
npm run test:plugin  

```

--------------------------------

### Running the Full Example

Source: https://docs.tracetest.io/tools-and-integrations/artillery-engine

Commands to run the complete example setup using Docker Compose and npm.

```bash
docker compose up -d  
npm run test:engine  
```

--------------------------------

### Clone Tracetest Project

Source: https://docs.tracetest.io/examples-tutorials/recipes/testing-kafka-go-api-with-opentelemetry-tracetest

Clone the Tracetest project repository to access the Go and Kafka quickstart example. Navigate to the example directory to begin setup.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/quick-start-go-and-kafka
```

--------------------------------

### Install Dependencies and Run Example

Source: https://docs.tracetest.io/tools-and-integrations/artillery-plugin

Install project dependencies using npm and execute the plugin test to run the Artillery and Tracetest integration example.

```bash
npm i
npm run test:plugin
```

--------------------------------

### Create Demonstration Setting

Source: https://docs.tracetest.io/openapi

Creates a demonstration setting used as quick start examples on Tracetest.

```APIDOC
## POST /demos

### Description
Create a demonstration used on Tracetest as quick start examples.

### Method
POST

### Endpoint
/demos

### Request Body
- **type** (string) - Required - Value: "Demo" Represents the type of this resource. It should always be set as 'Demo'.
- **spec** (object) - Required - Represents the attributes of a Demonstration API.
  - **id** (string) - Required - The unique identifier for the demonstration.
  - **type** (string) - Required - The type of the demonstration, e.g., "otelstore".
  - **name** (string) - Required - The name of the demonstration.
  - **enabled** (boolean) - Required - Indicates if the demonstration is enabled.
  - **pokeshop** (object) - Optional - Configuration for the pokeshop service.
    - **httpEndpoint** (string) - Required - The HTTP endpoint for the pokeshop service.
    - **grpcEndpoint** (string) - Required - The gRPC endpoint for the pokeshop service.
    - **kafkaBroker** (string) - Required - The Kafka broker address for the pokeshop service.
  - **opentelemetryStore** (object) - Optional - Configuration for the OpenTelemetry store.
    - **frontendEndpoint** (string) - Required - The frontend endpoint for the OpenTelemetry store.
    - **productCatalogEndpoint** (string) - Required - The product catalog endpoint for the OpenTelemetry store.
    - **cartEndpoint** (string) - Required - The cart endpoint for the OpenTelemetry store.
    - **checkoutEndpoint** (string) - Required - The checkout endpoint for the OpenTelemetry store.

### Request Example
```json
{
  "type": "Demo",
  "spec": {
    "id": "string",
    "type": "otelstore",
    "name": "string",
    "enabled": true,
    "pokeshop": {
      "httpEndpoint": "string",
      "grpcEndpoint": "string",
      "kafkaBroker": "string"
    },
    "opentelemetryStore": {
      "frontendEndpoint": "string",
      "productCatalogEndpoint": "string",
      "cartEndpoint": "string",
      "checkoutEndpoint": "string"
    }
  }
}
```

### Response
#### Success Response (201)
- **type** (string) - Description of the created demonstration.
- **spec** (object) - Attributes of the created demonstration.

#### Response Example
```json
{
  "type": "Demo",
  "spec": {
    "id": "string",
    "type": "otelstore",
    "name": "string",
    "enabled": true,
    "pokeshop": {
      "httpEndpoint": "string",
      "grpcEndpoint": "string",
      "kafkaBroker": "string"
    },
    "opentelemetryStore": {
      "frontendEndpoint": "string",
      "productCatalogEndpoint": "string",
      "cartEndpoint": "string",
      "checkoutEndpoint": "string"
    }
  }
}
```
```

--------------------------------

### Install Specific Version Example (v0.12.1)

Source: https://docs.tracetest.io/cli/cli-installation-reference

Example of installing a specific version (v0.12.1) of the Tracetest CLI using the installation script. Note that previously installed versions via package managers might take precedence depending on your PATH.

```bash
curl -L https://raw.githubusercontent.com/kubeshop/tracetest/main/install-cli.sh | bash -s -- v0.12.1  
```

--------------------------------

### Clone Tracetest and Navigate to Example

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-grafana-cloud-tempo-pokeshop

Clone the Tracetest repository and navigate to the Grafana Cloud Tempo Pokeshop example directory to begin the setup.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/tracetest-grafana-cloud-tempo-pokeshop
```

--------------------------------

### Clone Tracetest Repository and Navigate to TypeScript Quickstart

Source: https://docs.tracetest.io/tools-and-integrations/typescript

Clone the Tracetest GitHub repository and navigate to the TypeScript quickstart example directory to run the provided demo.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/quick-start-typescript
```

--------------------------------

### Clone Tracetest Project and Navigate to Quickstart

Source: https://docs.tracetest.io/tools-and-integrations/artillery-engine

Clone the Tracetest repository and navigate to the Artillery quick-start example directory to begin.

```bash
git clone https://github.com/kubeshop/tracetest  
cd tracetest/examples/quick-start-artillery  
```

--------------------------------

### Clone Tracetest AWS X-Ray Node.js Example

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-aws-x-ray-adot

Clone the Tracetest project and navigate to the AWS X-Ray Node.js Quickstart directory to run the example.

```bash
git clone https://github.com/kubeshop/tracetest  
cd tracetest/examples/tracetest-amazon-x-ray-adot  
```

--------------------------------

### Clone Tracetest Project and Navigate

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-signoz-pokeshop

Clone the Tracetest repository and navigate to the SigNoz Pokeshop Quickstart directory to begin the setup.

```bash
git clone https://github.com/kubeshop/tracetest  
cd tracetest/examples/tracetest-signoz-pokeshop  
```

--------------------------------

### Run Example Deployment

Source: https://docs.tracetest.io/examples-tutorials/recipes/testing-distributed-services-with-tyk-opentelemetry-tracetest

Execute the Docker Compose setup to run trace-based tests using the Tracetest Playwright integration.

```bash
docker-compose run tracetest-run  

```

--------------------------------

### Clone Tracetest Jaeger Node.js Example

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-jaeger

Clone the Tracetest project and navigate to the Jaeger Node.js quickstart directory to run the example.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/quick-start-jaeger-nodejs
```

--------------------------------

### Clone Tracetest Project

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-python-app-with-opentelemetry-collector-and-tracetest

Clone the Tracetest project repository and navigate to the Python quickstart example directory.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/quick-start-python
```

--------------------------------

### Clone Tracetest Tempo Node.js Example

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-tempo

Clone the Tracetest project and navigate to the Grafana Tempo Node.js Quickstart directory to run the example.

```bash
git clone https://github.com/kubeshop/tracetest  
cd tracetest/examples/quick-start-tempo-nodejs  
```

--------------------------------

### Clone Tracetest Project

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-honeycomb

Clone the Tracetest repository and navigate to the Node.js Quickstart example directory.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/tracetest-honeycomb
```

--------------------------------

### Install Tracetest Server CLI

Source: https://docs.tracetest.io/core/getting-started/overview

Use the Tracetest CLI to install the Tracetest server. This command initiates the installation process.

```bash
tracetest server install  
```

--------------------------------

### Docker Compose Up Command

Source: https://docs.tracetest.io/tools-and-integrations/typescript

This command starts the Docker Compose services defined in the docker-compose.yml file, setting up the necessary environment for the example.

```bash
docker compose up -d  

```

--------------------------------

### Clone Tracetest Azure App Insights Example

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-azure-app-insights-collector

Clone the Tracetest project and navigate to the Azure Node.js Quickstart directory to run the example.

```bash
git clone https://github.com/kubeshop/tracetest  
cd tracetest/examples/tracetest-azure-app-insights-collector  
```

--------------------------------

### Install Dependencies

Source: https://docs.tracetest.io/examples-tutorials/recipes/testing-lambda-functions-with-opentelemetry-tracetest

Install the necessary project dependencies by running this command in the root folder of the cloned repository.

```bash
npm i  
```

--------------------------------

### Clone Tracetest AWS X-Ray Pokeshop Example

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-aws-x-ray-pokeshop

Clone the Tracetest project and navigate to the AWS X-Ray Pokeshop Quickstart directory to begin.

```bash
git clone https://github.com/kubeshop/tracetest  
cd tracetest/examples/tracetest-amazon-x-ray-pokeshop  
```

--------------------------------

### Clone Tracetest Project

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-opensearch

Clone the Tracetest repository and navigate to the OpenSearch Node.js quickstart example directory.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/quick-start-opensearch-nodejs
```

--------------------------------

### Start Tracetest with Docker Compose

Source: https://docs.tracetest.io/core/getting-started/overview

Use Docker Compose to start Tracetest Core, an OpenTelemetry Collector, and the Pokeshop sample application. This command assumes you have Docker installed and the docker-compose.yaml file present.

```bash
docker compose -f docker-compose.yaml up -d
```

--------------------------------

### Tracetest Start Command Synopsis

Source: https://docs.tracetest.io/cli/reference/tracetest_start

This is the basic command to start Tracetest. Use flags to configure its behavior.

```bash
tracetest start [flags]
```

--------------------------------

### Start Tracetest Agent

Source: https://docs.tracetest.io/examples-tutorials/recipes/provisioning-developer-environment-script

Start the Tracetest agent, providing your API key and the environment ID it should connect to.

```bash
tracetest start --api-key $TRACETEST_TOKEN --environment $ENVIRONMENT_ID
```

--------------------------------

### Node.js App Start Script with Tracing

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-azure-app-insights

Configure the Node.js package.json to preload the tracing configuration when starting the application.

```json
"scripts": {  
  "start": "node -r ./tracing.js app.js"  
},  

```

--------------------------------

### tracetest start

Source: https://docs.tracetest.io/cli/reference/tracetest_start

Starts Tracetest with various configuration options.

```APIDOC
## tracetest start

### Description
Start using Tracetest.

### Synopsis
```
tracetest start [flags]
```

### Options
```
      --api-key string              agent api key  
      --collector-endpoint string   address of the OTel Collector endpoint  
      --environment string          environment id  
  -h, --help                        help for start  
      --insecure                    allow insecure connections to control plane  
  -l, --log-level string            set the agent log level (default "debug")  
  -m, --mode string                 set how the agent will start (default "desktop")  
      --organization string         organization id  
      --token string                token authentication key  
```

### Options inherited from parent commands
```
  -c, --config string       config file will be used by the CLI (default "config.yml")  
  -o, --output string       output format [pretty|json|yaml]  
  -s, --server-url string   server url  
      --skip-verify         skip verification of the server certificate (allows self signed, for example)  
  -v, --verbose             display debug information  
```
```

--------------------------------

### Run Pokeshop Demo, ADOT, and Tracetest Agent with Docker Compose

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-aws-x-ray-pokeshop

Execute this command to start the Pokeshop app, OpenTelemetry Collector, Tracetest Agent, and run the configured tests. This command orchestrates the entire setup defined in the `docker-compose.yaml` file.

```bash
docker compose run tracetest-run  
```

--------------------------------

### Clone Tracetest Example Repository

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-lightstep

Clone the Tracetest project and navigate to the specific example directory for Lightstep integration.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/tracetest-lightstep
```

--------------------------------

### Install Tracetest Server Command

Source: https://docs.tracetest.io/cli/reference/tracetest_server_install

Use this command to install a new Tracetest server. Various flags can be used to customize the installation, such as specifying the run environment and installation mode.

```bash
tracetest server install [flags]
```

--------------------------------

### Install Tracetest Server with Kubernetes

Source: https://docs.tracetest.io/core/getting-started/overview

Apply the Kubernetes manifest to install the Tracetest server. Ensure you have kubectl configured.

```bash
kubectl apply -f ./tracetest-kubernetes-manifests.yaml
```

--------------------------------

### Clone Tracetest Examples

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tests-with-tracetest-graphql-pokeshop

Clone the Tracetest GitHub repository and navigate to the Pokeshop GraphQL example directory to get started.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/tracetest-jaeger-graphql-pokeshop
```

--------------------------------

### Run Kind Cluster Setup Script

Source: https://docs.tracetest.io/install/on-prem-helm-kind

Execute the setup script to configure a local Kind cluster with Tracetest On-Prem and a demo application. You will be prompted for a license key.

```bash
sh ./scripts/setup_kind_cluster.sh --install-demo  
```

--------------------------------

### Initialize Local Repository for Services

Source: https://docs.tracetest.io/ci-cd-automation/github-actions-pipeline-with-secrets

Create a local directory structure and copy the example services into your new repository. Initialize a new Git repository and commit the initial files.

```bash
# sandbox folder to store our files  
mkdir github-actions-test  
cd ./github-actions-test  
  
mkdir my-repository  
cd ./my-repository  

cd ..  

git clone git@github.com:kubeshop/tracetest.git  
cp -r ./tracetest/examples/tracetest-with-github-action-and-secrets/services ./my-repository  

cd ./my-repository  

# remove the .git folder to start a new repository  
rm -rf .git  
git init  

git add .  
git commit -m "Initial commit"  
```

--------------------------------

### Tempo Configuration File Example

Source: https://docs.tracetest.io/configuration/connecting-to-data-stores/tempo

A full example of a Tempo configuration file, detailing server, distributor, ingester, compactor, and storage settings.

```yaml
# tempo.config.yaml  
  
auth_enabled: false  
server:  
  http_listen_port: 80  
  grpc_listen_port: 9095  
distributor:  
  receivers: # This configuration will listen on all ports and protocols that Tempo is capable of.  
    jaeger: # the receives all come from the OpenTelemetry collector.  more configuration information can  
      protocols: # be found here: https://github.com/open-telemetry/opentelemetry-collector/tree/master/receiver.  
        thrift_http: #  
        grpc: # For a production deployment you should only enable the receivers you need!  
        thrift_binary:  
        thrift_compact:  
    zipkin:  
    otlp:  
      protocols:  
        http:  
        grpc:  
    opencensus:  
ingester:  
  trace_idle_period: 10s # The length of time after a trace has not received spans to consider it complete and flush it.  
  max_block_bytes: 1_000_000 # Cut the head block when it hits this size or ...  
  #traces_per_block: 1_000_000  
  max_block_duration: 5m #   this much time passes.  
compactor:  
  compaction:  
    compaction_window: 1h # Blocks in this time window will be compacted together.  
    max_compaction_objects: 1000000 # Maximum size of compacted blocks.  
    block_retention: 1h  
    compacted_block_retention: 10m  
storage:  
  trace:  
    backend: local # Backend configuration to use.  
    wal:  
      path: /tmp/tempo/wal # Where to store the the wal locally.  
      #bloom_filter_false_positive: .05 # Bloom filter false positive rate.  Lower values create larger filters but fewer false positives.  
      #index_downsample: 10             # Number of traces per index record.  
    local:  
      path: /tmp/tempo/blocks  
    pool:  
      max_workers: 100 # The worker pool mainly drives querying, but is also used for polling the blocklist.  
      queue_depth: 10000  

```

--------------------------------

### Clone Tracetest Repository

Source: https://docs.tracetest.io/examples-tutorials/recipes/testing-distributed-services-with-tyk-opentelemetry-tracetest

Clone the Tracetest GitHub repository to access example applications, including the Tyk Gateway quick start example.

```bash
git clone https://github.com/kubeshop/tracetest.git
cd tracetest/examples/quick-start-tyk
```

--------------------------------

### Clone Tracetest Project

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-playwright-performance-tests-with-artillery-and-tracetest

Clone the Tracetest GitHub repository to access the Artillery + Playwright quickstart example. Navigate to the example directory to begin.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/quick-start-artillery-playwright
```

--------------------------------

### Start Pokeshop Demo App with Docker Compose

Source: https://docs.tracetest.io/tools-and-integrations/cypress

Run the Pokeshop Demo App using Docker Compose with the specified configuration files.

```bash
docker compose -f docker-compose.yml -f docker-compose.e2e.yml up  

```

--------------------------------

### Shopping Cart API Response Example

Source: https://docs.tracetest.io/live-examples/opentelemetry-store/use-cases/check-shopping-cart-contents

This is an example of the JSON payload returned by the GET /api/cart endpoint, showing the user ID and items in the cart.

```json
{
  "userId": "8c0465e2-32bb-4ecb-a9c8-5a2861629ff1",
  "items": [
    {
      "productId": "66VCHSJNUP",
      "quantity" : 1,
      "product": {
        "id": "66VCHSJNUP",
        "name": "Starsense Explorer Refractor Telescope",
        "description": "The first telescope that uses your smartphone to analyze the night sky and calculate its position in real time. StarSense Explorer is ideal for beginners thanks to the app’s user-friendly interface and detailed tutorials. It’s like having your own personal tour guide of the night sky",
        "picture": "/images/products/StarsenseExplorer.jpg",
        "priceUsd": {
          "currencyCode": "USD",
          "units": 349,
          "nanos": 950000000
        },
        "categories": [
          "telescopes"
        ]
      }
    }
  ]
}
```

--------------------------------

### Clone and Run Example Services

Source: https://docs.tracetest.io/ci-cd-automation/github-actions-pipeline-with-secrets

Clone the Tracetest repository and set up the example payment ecosystem services using Docker Compose. Ensure you have your Tracetest Agent API key.

```bash
git clone git@github.com:kubeshop/tracetest.git  
cd ./tracetest/examples/tracetest-with-github-action-and-secrets  
TRACETEST_API_KEY=<your-agent-key> docker compose up  
```

--------------------------------

### Start Tracetest with Docker Compose

Source: https://docs.tracetest.io/core/getting-started/overview

Start the Tracetest Server and its dependencies using Docker Compose after installation. This command exposes the Web UI on http://localhost:11633.

```bash
docker compose -f tracetest/docker-compose.yaml up -d  
```

--------------------------------

### Start Next.js Development Server

Source: https://docs.tracetest.io/examples-tutorials/recipes/testing-vercel-functions-with-opentelemetry-tracetest

Command to start the Next.js development server, which includes running the Vercel Function. This command assumes a standard Next.js project setup.

```bash
npm run dev  

```

--------------------------------

### Delete a Demonstration

Source: https://docs.tracetest.io/openapi

Deletes a demonstration setting used as quick start examples in Tracetest.

```APIDOC
## DELETE /demos/{demoId}

### Description
Delete a demonstration used on Tracetest as quick start examples.

### Method
DELETE

### Endpoint
/demos/{demoId}

### Parameters
#### Path Parameters
- **demoId** (string) - Required - ID of a demonstration used on Tracetest as quick start examples.

### Responses
#### Success Response (204)
successful operation

#### Error Response (400)
invalid demo, some data was sent in incorrect format.

#### Error Response (404)
demo not found

#### Error Response (500)
problem deleting a demo
```

--------------------------------

### Configure Tracetest Installation (Kubernetes)

Source: https://docs.tracetest.io/core/getting-started/overview

Interactive prompt to choose between installing Tracetest with a demo tracing environment and app, or just Tracetest for Kubernetes.

```bash
How do you want to run TraceTest? [type to search]:  
  Using Docker Compose  
> Using Kubernetes  
```

```bash
Do you have OpenTelemetry based tracing already set up, or would you like us to install a demo tracing environment and app? [type to search]:   
  I have a tracing environment already - Just install Tracetest.  
> Just learning tracing! Install Tracetest, OpenTelemetry Collector and the sample app.  
```

--------------------------------

### Install Bash Completion for macOS

Source: https://docs.tracetest.io/cli/reference/tracetest_completion_bash

For macOS users, install bash autocompletion by directing the output to the appropriate directory managed by Homebrew. You will need to start a new shell session for the changes to apply.

```bash
tracetest completion bash > $(brew --prefix)/etc/bash_completion.d/tracetest
```

--------------------------------

### Start Pokeshop API with Docker Compose (Pokeshop Repo)

Source: https://docs.tracetest.io/getting-started/create-trace-based-test

Clone the Pokeshop repository and start the API using Docker Compose. This is an alternative method to set up the Pokeshop API.

```bash
git clone --depth 1 https://github.com/kubeshop/pokeshop.git  
cd pokeshop  

docker compose up -d --build  
```

--------------------------------

### List Demonstrations

Source: https://docs.tracetest.io/openapi

Retrieves a list of demonstrations available in Tracetest, which serve as quick start examples for using the platform.

```APIDOC
## List Demonstrations 

List demonstrations used on Tracetest as quick start examples.

### Method
GET

### Endpoint
/demos

### Parameters
#### Query Parameters
- **take** (integer) - Optional - Default: 20. Indicates how many resources can be returned by each page.
- **skip** (integer) - Optional - Default: 0. Indicates how many resources will be skipped when paginating.
- **sortBy** (string) - Optional - Enum: "type", "enabled". Indicates the sort field for the resources.
- **sortDirection** (string) - Optional - Enum: "asc", "desc". Indicates the sort direction for the resources.

### Responses
#### Success Response (200)
- A list of demonstrations available on Tracetest.
```

--------------------------------

### Clone Tracetest Project

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-sumologic

Clone the Tracetest project repository to access the Sumo Logic Node.js quickstart example.

```bash
git clone https://github.com/kubeshop/tracetest
cd tracetest/examples/quick-start-sumologic-nodejs
```

--------------------------------

### Clone Tracetest Project

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-tracetest-with-grafana-cloud-tempo

Clone the Tracetest repository and navigate to the Grafana Cloud Tempo Node.js quickstart example directory.

```bash
git clone https://github.com/kubeshop/tracetest  
cd tracetest/examples/quick-start-grafana-cloud-tempo-nodejs  
```

--------------------------------

### Start Pokeshop Application with Docker Compose

Source: https://docs.tracetest.io/web-ui/trace-mode

This command starts the Pokeshop application and its associated services using Docker Compose. It requires a .env file with specific configurations for Tracetest agent and environment.

```bash
docker compose -f docker-compose.yml -f docker-compose.e2e.yml up -d
```

--------------------------------

### Run the OpenTelemetry Demo with Docker Compose

Source: https://docs.tracetest.io/live-examples/opentelemetry-store/overview

Start the OpenTelemetry Demo microservices using Docker Compose. The `--no-build` flag uses pre-built images from ghcr, significantly speeding up startup. Omit this flag to build images from source, which can take over 20 minutes.

```bash
docker compose up --no-build
```

--------------------------------

### Tracetest Server Install Options

Source: https://docs.tracetest.io/cli/reference/tracetest_server_install

These are the specific options for the 'tracetest server install' command. Use '--force' to overwrite existing files, specify the Kubernetes context, or define the 'run-environment' and 'mode'.

```bash
  -f, --force                                 Overwrite existing files  
  -h, --help                                  help for install  
      --kubernetes-context string             Kubernetes context used to install Tracetest. It will be only used if 'run-environment' is set as 'kubernetes'.  
      --mode (with-demo|just-tracetest)       Indicate the type of demo environment to be installed with Tracetest. It can be 'with-demo' or 'just-tracetest'. (default none)  
      --run-environment (docker|kubernetes)   Type of environment were Tracetest will be installed. It can be 'docker' or 'kubernetes'. (default none)  
```

--------------------------------

### Enable Pokeshop Demo with CLI

Source: https://docs.tracetest.io/configuration/demo

Use this YAML resource definition to enable the Pokeshop demo. Specify the file when running the 'tracetest apply demo' command.

```yaml
type: Demo
spec:
  type: pokeshop
  enabled: true
  name: pokeshop
  opentelemetryStore: {}
  pokeshop:
    httpEndpoint: http://demo-pokemon-api.demo.svc.cluster.local
    grpcEndpoint: demo-pokemon-api.demo:8082

```

--------------------------------

### Clone Tracetest Pokeshop Demo App

Source: https://docs.tracetest.io/tools-and-integrations/cypress

Clone the official Tracetest Pokeshop Demo App repository to your local machine to follow the quickstart example.

```bash
git clone https://github.com/kubeshop/pokeshop.git
cd pokeshop
```

--------------------------------

### Configure Tracetest Installation (Docker Compose)

Source: https://docs.tracetest.io/core/getting-started/overview

Interactive prompt to choose between installing Tracetest with a demo tracing environment and app, or just Tracetest.

```bash
How do you want to run Tracetest? [type to search]:  
> Using Docker Compose  
  Using Kubernetes  
```

```bash
Do you have OpenTelemetry based tracing already set up, or would you like us to install a demo tracing environment and app? [type to search]:   
  I have a tracing environment already. - Just install Tracetest.  
> Just learning tracing! Install Tracetest, OpenTelemetry Collector and the sample app.  
```

--------------------------------

### Display Tracetest CLI Tool Version

Source: https://docs.tracetest.io/cli/reference/tracetest_version

Use this command to display the current version of the Tracetest CLI. No specific setup is required beyond having the CLI installed.

```bash
tracetest version [flags]
```

--------------------------------

### Set Up Remote Repository and Push

Source: https://docs.tracetest.io/ci-cd-automation/github-actions-pipeline-with-secrets

Add the remote origin for your GitHub repository and push the initial commit to the main branch. Replace placeholders with your actual GitHub username and repository name.

```bash
git remote add origin https://github.com/<your-github-user>/<your-github-name>.git  
git push origin main  
```

--------------------------------

### Tracetest Selector Example

Source: https://docs.tracetest.io/examples-tutorials/recipes/running-python-app-with-opentelemetry-collector-and-tracetest

Use this CSS selector to identify specific spans in your trace data within the Tracetest UI. It targets HTTP GET requests to the \"/automatic\" endpoint.

```css
span[tracetest.span.type="http" name="/automatic" http.target="/automatic" http.method="GET"]  

```