6 Commits

Author SHA1 Message Date
Stephan Behnke
a513035ce9 Open Tempo OTEL HTTP port (#7033)
## What changed?
<!-- Describe what has changed in this PR -->

Open up Grafana Tempo's OTEL HTTP port, too.

## Why?
<!-- Tell your future self why have you made these changes -->

It's useful to send traces via curl.

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
2024-12-24 11:44:46 -08:00
Stephan Behnke
c19b51a743 Grafana Tempo (#7006)
## What changed?
<!-- Describe what has changed in this PR -->

Added Grafana Tempo - an OTEL collector - to the developer setup.

Since we're already using Grafana, Tempo seemed like a logical choice.

## Why?
<!-- Tell your future self why have you made these changes -->

It allows developers to see all the RPC calls they are making (e.g. when
running the server locally or a functional test).

Tempo allows filtering by workflow ID. _(note that not _all_ places are
tagged yet, but lots of them)_

## How did you test it?
<!-- How have you verified this change? Tested locally? Added a unit
test? Checked in staging env? -->

```
make start-grafana-tempo
make OTEL=true start
```
```
tctl --ns default namespace register
tctl wf start --tq test --wid test -wt test
```

<img width="3352" alt="image"
src="https://github.com/user-attachments/assets/5809691a-da32-4a04-8e80-700f8acd47e5"
/>

And running a functional test from the IDE:

<img width="3346" alt="image"
src="https://github.com/user-attachments/assets/061bfaf3-0a34-4b4e-a06c-497dfa3a948a"
/>


## Potential risks
<!-- Assuming the worst case, what can be broken when deploying this
change to production? -->

## Documentation
<!-- Have you made sure this change doesn't falsify anything currently
stated in `docs/`? If significant
new behavior is added, have you described that in `docs/`? -->

Updated docs/development/tracing.md

## Is hotfix candidate?
<!-- Is this PR a hotfix candidate or does it require a notification to
be sent to the broader community? (Yes/No) -->
2024-12-19 17:33:13 -08:00
YeZhu
d4d43259b6 Remove version field from docker compose yaml file (#6610)
## What changed?
Remove the version field from all the docker compose yaml files

## Why?
I followed the dev
[doc](https://github.com/temporalio/temporal/blob/main/develop/docker-compose/README.md)
to setup the local env, and it showed the warning message like
`WARN[0003] /xxxx/temporal/develop/docker-compose/docker-compose.yml:
the attribute `version` is obsolete, it will be ignored, please remove
it to avoid potential confusion`
Some discussions are
[here](https://forums.docker.com/t/docker-compose-yml-version-is-obsolete/141313)
and the `version` field was confirmed to be deprecated. So I want to
raise this PR to remove this deprecated field.

![image](https://github.com/user-attachments/assets/a880a612-7165-45c0-a6ff-97a47c7f36d7)


## How did you test it?
N/A

## Potential risks
N/A

## Documentation
N/A

## Is hotfix candidate?
No

Co-authored-by: Roey Berman <roey@temporal.io>
2024-10-09 10:38:26 -07:00
Ruslan
a4fe3a7cf1 Remove UI v1 from development environment (#3485)
Remove UI v1 from development scripts
2022-10-15 20:33:03 -04:00
Alex Shtin
ede203533f Add Temoporal Web 2.0 to development docker-compose (#2520) 2022-02-18 10:27:27 -08:00
Alex Shtin
af60aeacdc Move development files to develop (#1377) 2021-03-15 17:06:19 -07:00