chore(examples): Updating vendor examples #3966

xoscar · 2024-08-14T16:10:47Z

This PR...

Changes

Fixes

Checklist

tested locally
added new dependencies
updated the docs
added a test

Loom video

Add your loom video here if your work can be visualized

vercel · 2024-08-14T16:10:50Z

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
tracetest	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Aug 15, 2024 5:16pm

jfermi · 2024-08-14T17:40:12Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-datadog.mdx

+4. Run `docker compose run tracetest-run`.
+5. 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.


Suggested change

Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works.

Follow the sections below for a detailed breakdown of what the example you just ran did and how it works.

jfermi · 2024-08-14T17:41:41Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-datadog.mdx

-Increasing the duration to a more reasonable `500ms` will make the test pass.
-
-![](../img/datadog-recipe-successful-test.png)
+## Running the tests


Suggested change

## Running the tests

## Running the Tests

jfermi · 2024-08-14T17:42:28Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-dynatrace.mdx

+4. Run `docker compose run tracetest-run`.
+5. 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.


Suggested change

Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works.

Follow the sections below for a detailed breakdown of what the example you just ran did and how it works.

jfermi · 2024-08-14T17:42:48Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-dynatrace.mdx

-![](../img/dynatrace-failed-test.png)
-
-Increasing the duration to a more reasonable `500ms` will make the test pass.
+## Running the tests


Suggested change

## Running the tests

## Running the Tests

jfermi · 2024-08-14T17:44:05Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-lightstep.mdx

+4. Run `docker compose run tracetest-run`.
+5. 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.


Suggested change

Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works.

Follow the sections below for a detailed breakdown of what the example you just ran did and how it works.

jfermi · 2024-08-14T17:44:33Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-lightstep.mdx

 ```

-This will start your Tracetest instance on `http://localhost:11633/`.
+## Running the tests


Suggested change

## Running the tests

## Running the Tests

jfermi · 2024-08-14T17:45:07Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-new-relic.mdx

+4. Run `docker compose run tracetest-run`.
+5. 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.


Suggested change

Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works.

Follow the sections below for a detailed breakdown of what the example you just ran did and how it works.

jfermi · 2024-08-14T17:45:25Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-new-relic.mdx


-## Run both the OpenTelemetry Demo app and Tracetest
+## Running the tests


Suggested change

## Running the tests

## Running the Tests

jfermi

Some editing suggestions.

adnanrahic

Tiny suggestions. 👌

adnanrahic · 2024-08-15T09:32:48Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-datadog.mdx

-The `docker-compose.yaml` file, `collector.config.yaml`, `tracetest-provision.yaml`, and `tracetest-config.yaml` in the `tracetest` directory are for setting up Tracetest and the OpenTelemetry Collector.
-
-The `tracetest` directory is self-contained and will run all the prerequisites for enabling OpenTelemetry traces and trace-based testing with Tracetest, as well as routing all traces the OpenTelemetry Demo generates to Datadog.
-
 ### Docker Compose Network

 All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where port `4317` is the port where Tracetest accepts traces.


Suggested change

All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where port `4317` is the port where Tracetest accepts traces.

All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest-agent:4317` in the `collector.config.yaml` will map to the `tracetest-agent` service, where port `4317` is the port where Tracetest Agent accepts traces.

adnanrahic · 2024-08-15T09:34:07Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-dynatrace.mdx

@@ -40,8 +66,6 @@ The `docker-compose.yaml` file and `.env` file in the root directory are for the

 The `docker-compose.yaml` file, `collector.config.yaml`, `tracetest-provision.yaml`, and `tracetest-config.yaml` in the `tracetest` directory are for setting up Tracetest and the OpenTelemetry Collector.

-The `tracetest` directory is self-contained and will run all the prerequisites for enabling OpenTelemetry traces and trace-based testing with Tracetest, as well as routing all traces the OpenTelemetry Demo generates to Dynatrace.
-
 ### Docker Compose Network

 All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where port `4317` is the port where Tracetest accepts traces.


Suggested change

All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where port `4317` is the port where Tracetest accepts traces.

All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest-agent:4317` in the `collector.config.yaml` will map to the `tracetest-agent` service, where port `4317` is the port where Tracetest Agent accepts traces.

adnanrahic · 2024-08-15T09:34:35Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-dynatrace.mdx

-    - test-specs
-
-```
-
 ### Sending Traces to Tracetest and Dynatrace

 The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest's OTLP endpoint `tracetest:4317` in one pipeline, and to Dynatrace in another.


Suggested change

The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest's OTLP endpoint `tracetest:4317` in one pipeline, and to Dynatrace in another.

The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest Agent's OTLP endpoint `tracetest-agent:4317` in one pipeline, and to Dynatrace in another.

adnanrahic · 2024-08-15T09:34:55Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-dynatrace.mdx

@@ -256,23 +130,22 @@ receivers:
        - targets: ['0.0.0.0:8888']

 processors:
-  batch: # this configuration is needed to guarantee that the data is sent correctly to Dynatrace
+  batch: # this configuration is needed to guarantee that the data is sent correctly to Datadog


Suggested change

batch: # this configuration is needed to guarantee that the data is sent correctly to Datadog

batch: # this configuration is needed to guarantee that the data is sent correctly to Dynatrace

adnanrahic · 2024-08-15T09:35:42Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-lightstep.mdx

-    checkoutEndpoint: otel-checkoutservice:5050
-
-```
-
 **How to Send Traces to Tracetest and Lightstep**

 The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest's OTLP endpoint `tracetest:4317` in one pipeline, and to Lightstep in another.


Suggested change

The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest's OTLP endpoint `tracetest:4317` in one pipeline, and to Lightstep in another.

The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest Agent's OTLP endpoint `tracetest-agent:4317` in one pipeline, and to Lightstep in another.

adnanrahic · 2024-08-15T09:36:30Z

docs/docs/examples-tutorials/recipes/running-tracetest-with-new-relic.mdx

-The `docker-compose.yaml` file, `collector.config.yaml`, `tracetest-provision.yaml`, and `tracetest-config.yaml` in the `tracetest` directory are for the setting up Tracetest and the OpenTelemetry Collector.
-
-The `tracetest` directory is self-contained and will run all the prerequisites for enabling OpenTelemetry traces and trace-based testing with Tracetest, as well as routing all traces the OpenTelemetry Demo generates to New Relic.
-
 ### 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. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where the port `4317` is the port where Tracetest accepts traces.


Suggested change

All `services` in the `docker-compose.yaml` are on the same network and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where the port `4317` is the port where Tracetest accepts traces.

All `services` in the `docker-compose.yaml` are on the same network and will be reachable by hostname from within other services. E.g. `tracetest-agent:4317` in the `collector.config.yaml` will map to the `tracetest-agent` service, where the port `4317` is the port where Tracetest Agent accepts traces.

chore(examples): Updating vendor examples

3b8bb2b

vercel bot deployed to Preview August 14, 2024 16:11 View deployment

xoscar added 3 commits August 14, 2024 10:17

updating new relic example

07c20a5

updating new relic example

1dc415a

updating new relic example

4002218

vercel bot deployed to Preview August 14, 2024 16:18 View deployment

updating datadog example

f21a04f

vercel bot deployed to Preview August 14, 2024 16:32 View deployment

updating dynatrace example

7bbe6a1

vercel bot deployed to Preview August 14, 2024 16:40 View deployment

xoscar added 4 commits August 14, 2024 10:50

updating honeycomb example

5b4961d

updating signoz example

52dbb74

updating signoz example

ded849f

PR suggestions updates

4266373

vercel bot deployed to Preview August 14, 2024 17:06 View deployment

updating recipes

5e04b7e

xoscar marked this pull request as ready for review August 14, 2024 17:32

xoscar requested review from adnanrahic, kdhamric and jfermi August 14, 2024 17:32

vercel bot deployed to Preview August 14, 2024 17:32 View deployment

jfermi reviewed Aug 14, 2024

View reviewed changes

adnanrahic approved these changes Aug 15, 2024

View reviewed changes

xoscar added 2 commits August 15, 2024 11:13

Merge branch 'main' into chore-updating-vendors-examples

8d68f67

PR comments update

000e131

vercel bot deployed to Preview August 15, 2024 17:16 View deployment

xoscar merged commit 182c468 into main Aug 15, 2024
38 checks passed

xoscar deleted the chore-updating-vendors-examples branch August 15, 2024 17:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore(examples): Updating vendor examples #3966

chore(examples): Updating vendor examples #3966

xoscar commented Aug 14, 2024

vercel bot commented Aug 14, 2024 •

edited

Loading

jfermi Aug 14, 2024

jfermi Aug 14, 2024

jfermi Aug 14, 2024

jfermi Aug 14, 2024

jfermi Aug 14, 2024

jfermi Aug 14, 2024

jfermi Aug 14, 2024

jfermi Aug 14, 2024

jfermi left a comment

adnanrahic left a comment

adnanrahic Aug 15, 2024

adnanrahic Aug 15, 2024

adnanrahic Aug 15, 2024

adnanrahic Aug 15, 2024

adnanrahic Aug 15, 2024

adnanrahic Aug 15, 2024

	Follow along with the sections below for an in detail breakdown of what the example you just ran did and how it works.
	Follow the sections below for a detailed breakdown of what the example you just ran did and how it works.


		## Run both the OpenTelemetry Demo app and Tracetest
		## Running the tests

	All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest:4317` in the `collector.config.yaml` will map to the `tracetest` service, where port `4317` is the port where Tracetest accepts traces.
	All `services` in the `docker-compose.yaml` are on the same network, defined by the `networks` section on each file, and will be reachable by hostname from within other services. E.g. `tracetest-agent:4317` in the `collector.config.yaml` will map to the `tracetest-agent` service, where port `4317` is the port where Tracetest Agent accepts traces.

	The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest's OTLP endpoint `tracetest:4317` in one pipeline, and to Dynatrace in another.
	The `collector.config.yaml` explains that. It receives traces via either `grpc` or `http`. Then, exports them to Tracetest Agent's OTLP endpoint `tracetest-agent:4317` in one pipeline, and to Dynatrace in another.

	batch: # this configuration is needed to guarantee that the data is sent correctly to Datadog
	batch: # this configuration is needed to guarantee that the data is sent correctly to Dynatrace

chore(examples): Updating vendor examples #3966

chore(examples): Updating vendor examples #3966

Conversation

xoscar commented Aug 14, 2024

Changes

Fixes

Checklist

Loom video

vercel bot commented Aug 14, 2024 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

jfermi left a comment

Choose a reason for hiding this comment

adnanrahic left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

vercel bot commented Aug 14, 2024 •

edited

Loading