Skip to content

Update naming of Workers #35232

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maycmlee merged 3 commits into from
Mar 13, 2026
Merged

Update naming of Workers #35232

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3960d3a
update link
maycmlee Mar 12, 2026
4d1d32d
fix args
maycmlee Mar 12, 2026
3ea2fe8
update
maycmlee Mar 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 18 additions & 11 deletions ...shortcodes/observability_pipelines/install_worker/pod_cluster_name_worker.en.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,28 +1,35 @@
By default, a Worker's hostname is the machine's hostname, such as `COMP-JLXPKWTGJF`. If you run your pipeline across multiple clusters or containers, assign each Worker a unique hostname based on the Pod name and cluster name to make them easier to identify.

In the Helm chart [`values.yaml`][101]

1. Configure the environment variable `POD_NAME` to be automatically set to the Pod's name.
In the Helm chart:
1. Configure the environment variable [`POD_NAME`][101] to be automatically set to the Pod's name.
```yaml
env:
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
```
1. Set the [`CLUSTER_NAME`][102] environment variable in the Helm chart.
1. Set the `CLUSTER_NAME` environment variable in the Helm chart.
```
env:
- name: CLUSTER_NAME
value: "<MY_CLUSTER_NAME>"
```
1. To assign unique Worker names, configure [`VECTOR_HOSTNAME`][103] to the `POD_NAME` and `CLUSTER_NAME`.
1. Set the `VECTOR_HOSTNAME` to the `POD_NAME` and `CLUSTER_NAME`.
```yaml
args:
- >
export VECTOR_HOSTNAME="${POD_NAME}.${CLUSTER_NAME}";
exec /usr/bin/observability-pipelines-worker run
env:
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name

- name: CLUSTER_NAME
value: "<MY_CLUSTER_NAME>"

- name: VECTOR_HOSTNAME
value: "$(CLUSTER_NAME)_$(POD_NAME)"
```

[101]: https://github.com/DataDog/helm-charts/blob/3cbc416fb81e5a733caf38bcc5a9f86f424187cc/charts/observability-pipelines-worker/values.yaml#L156C3-L159C33
[102]: https://github.com/DataDog/helm-charts/blob/3cbc416fb81e5a733caf38bcc5a9f86f424187cc/charts/observability-pipelines-worker/values.yaml#L154-L155
[103]: https://github.com/DataDog/helm-charts/blob/3cbc416fb81e5a733caf38bcc5a9f86f4103187cc/charts/observability-pipelines-worker/values.yaml#L141-L142

[101]: https://github.com/DataDog/helm-charts/blob/main/charts/observability-pipelines-worker/values.yaml
Loading