Skip to content
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.

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

[Tanzu Tile] Add host.name resource attribute #5810

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

crobert-1
Copy link
Contributor

Description:

The host.name resource attribute should come from the Tanzu environment, not the environment in which the collector itself is running.

Note:
No changelog here because this won't have any impact until a new Tanzu Tile release is created.

Testing:
Tested on TAS 10.0 and TAS 6.0. Working as expected. The host.name is populated as the IP address of the BOSH director.

@crobert-1 crobert-1 requested review from a team as code owners January 17, 2025 18:36
@@ -23,8 +23,11 @@ receivers:
<% end %>

processors:
resourcedetection:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we somehow test this file so it doesn't get stale like it did here?

Copy link
Contributor Author

@crobert-1 crobert-1 Jan 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There isn't a quick way to test this automatically. Running a BOSH deployment requires a lot of set up and dependency installs, so it'd be some amount of effort. This file doesn't get changed much and is tested directly with each Tanzu Tile release.

The change to the config here is a bug fix, it didn't actually go stale.

Edit: I can definitely see there being value in adding CI/CD testing for this, my main point is that it would be its own task to track, outside of the scope of this change.

@hughesjj hughesjj merged commit 7daef52 into signalfx:main Jan 21, 2025
4 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jan 21, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants