-
Notifications
You must be signed in to change notification settings - Fork 156
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
Windows script to install Splunk distro for .NET instead of SFx.NET #4343
Merged
pjanotti
merged 5 commits into
signalfx:main
from
pjanotti:migrate-install-ps-to-otel-dotnet
Feb 28, 2024
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c2b432b
Switch from SFx.NET to Splunk OTel .NET
pjanotti a54deb8
Minor changes to the install script
pjanotti 7e68e73
Update CHANGELOG.md
pjanotti a283f82
Clarify update for .NET instrumentation
pjanotti 47dd750
Remove update for Splunk OTel .NET
pjanotti File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -159,20 +159,20 @@ jobs: | |
name: msi-build | ||
path: ./tests/zeroconfig/windows/testdata/docker-setup/ | ||
|
||
- name: Get latest signalfx-dotnet-tracing release | ||
id: dotnet-tracing | ||
- name: Get latest splunk-otel-dotnet release | ||
id: dotnet-instrumentation | ||
uses: pozetroninc/[email protected] | ||
with: | ||
owner: signalfx | ||
repo: signalfx-dotnet-tracing | ||
repo: splunk-otel-dotnet | ||
excludes: prerelease, draft | ||
token: ${{ secrets.GITHUB_TOKEN }} | ||
|
||
- name: Set SIGNALFX_DOTNET_TRACING_VERSION | ||
- name: Set SPLUNK_OTEL_DOTNET_VERSION | ||
run: | | ||
version="${{ steps.dotnet-tracing.outputs.release }}" | ||
sed -i "s|SIGNALFX_DOTNET_TRACING_VERSION|${version#v}|" tests/zeroconfig/windows/testdata/resource_traces/aspnetcore.yaml | ||
sed -i "s|SIGNALFX_DOTNET_TRACING_VERSION|${version#v}|" tests/zeroconfig/windows/testdata/resource_traces/aspnetfx.yaml | ||
version="${{ steps.dotnet-instrumentation.outputs.release }}" | ||
sed -i "s|SPLUNK_OTEL_DOTNET_VERSION|${version#v}|" tests/zeroconfig/windows/testdata/resource_traces/aspnetcore.yaml | ||
sed -i "s|SPLUNK_OTEL_DOTNET_VERSION|${version#v}|" tests/zeroconfig/windows/testdata/resource_traces/aspnetfx.yaml | ||
shell: bash | ||
|
||
- name: Run the test script | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure what to do here, but
OTEL_RESOURCE_ATTRIBUTES
seems to be conflicting with instrumenting agent and could leak to an instrumented process when in a global scope.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't want to change this on this PR but the main thing here to me is that the
splunk.zc.method
seems to need a different value since we could have multiple instrumentations on the same box. However,deployment.environment
is something that we want for the whole machine. I will have a conversation with Rotel about it before changing it, the current code is in line with what mass deployments are doing.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess the conflict is getting even bigger then? ... since envs don't stack by default and
OTEL_RESOURCE_ATTRIBUTES
can be easily overwritten (due being a generic variable) by a client.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will have to investigate this separately, likely also changing the value that we use for OTel resource attributes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After writing the answer to Aunsh I think it will make more sense to just bail out here: it will be consistent with what is done for the collector MSI: the script just bails out if there is already one version installed. We are also bailing out if SFx.NET is already installed.