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

Add VMScaleSetName field to Azure resource detection processor #2890

Merged
merged 1 commit into from
Mar 26, 2021
Merged

Add VMScaleSetName field to Azure resource detection processor #2890

merged 1 commit into from
Mar 26, 2021

Conversation

pmcollins
Copy link
Member

The Splunk/SFx exporter needs a VMScaleSetName to generate the azure_resource_id.

Tested on Azure as a standalone VM and in a Scale Set.

README updated.

The Splunk/SFx exporter will need this to generate an azure_resource_id.

Tested on Azure as a standalone VM and in a Scale Set.
@codecov
Copy link

codecov bot commented Mar 26, 2021

Codecov Report

Merging #2890 (f24bfb9) into main (359d6e4) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2890   +/-   ##
=======================================
  Coverage   91.60%   91.60%           
=======================================
  Files         450      450           
  Lines       22191    22192    +1     
=======================================
+ Hits        20327    20328    +1     
  Misses       1394     1394           
  Partials      470      470           
Flag Coverage Δ
integration 69.09% <ø> (-0.07%) ⬇️
unit 90.54% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
...ourcedetectionprocessor/internal/azure/metadata.go 77.41% <ø> (ø)
...resourcedetectionprocessor/internal/azure/azure.go 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 359d6e4...f24bfb9. Read the comment docs.

@pmcollins pmcollins marked this pull request as ready for review March 26, 2021 16:01
@pmcollins pmcollins requested a review from a team March 26, 2021 16:01
@bogdandrutu
Copy link
Member

@pmcollins I would suggest to also open a specification issue to ensure that we will define this in the semantic conventions. Reason should not be that Splunk needs it, if only Splunk needs it we should customize somewhere else, but I believe this is important information for more users.

@bogdandrutu bogdandrutu merged commit a6237b0 into open-telemetry:main Mar 26, 2021
pmatyjasek-sumo pushed a commit to pmatyjasek-sumo/opentelemetry-collector-contrib that referenced this pull request Apr 28, 2021
…telemetry#2890)

The Splunk/SFx exporter will need this to generate an azure_resource_id.

Tested on Azure as a standalone VM and in a Scale Set.
alexperez52 referenced this pull request in open-o11y/opentelemetry-collector-contrib Aug 18, 2021
Bumps [github.com/uber/jaeger-lib](https://github.com/uber/jaeger-lib) from 2.4.0+incompatible to 2.4.1+incompatible.
- [Release notes](https://github.com/uber/jaeger-lib/releases)
- [Changelog](https://github.com/jaegertracing/jaeger-lib/blob/master/CHANGELOG.md)
- [Commits](jaegertracing/jaeger-lib@v2.4.0...v2.4.1)

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants