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

[resourcedetection/aws] Use values in accordance to semantic conventions #2556

Merged

Conversation

pmm-sumo
Copy link
Contributor

@pmm-sumo pmm-sumo commented Mar 4, 2021

Description:

Values used for cloud.infrastructure_service by AWS detectors were not following semantic conventions. This change fixes it.

Link to tracking Issue: Closes specification/#1377

Testing: Unit test cases updated

Documentation: No changes

@pmm-sumo pmm-sumo requested review from anuraaga and jrcamp as code owners March 4, 2021 14:52
@pmm-sumo pmm-sumo requested a review from a team March 4, 2021 14:52
@pmm-sumo pmm-sumo changed the title Use values in accordance to semantic conventions [resourcedetection/aws] Use values in accordance to semantic conventions Mar 4, 2021
@codecov
Copy link

codecov bot commented Mar 4, 2021

Codecov Report

Merging #2556 (5ac3d5b) into main (2c48687) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2556   +/-   ##
=======================================
  Coverage   91.17%   91.18%           
=======================================
  Files         419      419           
  Lines       20983    20983           
=======================================
+ Hits        19132    19134    +2     
+ Misses       1383     1382    -1     
+ Partials      468      467    -1     
Flag Coverage Δ
integration 69.22% <ø> (-0.07%) ⬇️
unit 90.06% <100.00%> (+<0.01%) ⬆️

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

Impacted Files Coverage Δ
...resourcedetectionprocessor/internal/aws/ec2/ec2.go 78.46% <100.00%> (ø)
...resourcedetectionprocessor/internal/aws/ecs/ecs.go 85.24% <100.00%> (ø)
.../internal/aws/elasticbeanstalk/elasticbeanstalk.go 100.00% <100.00%> (ø)
receiver/k8sclusterreceiver/watcher.go 97.64% <0.00%> (+2.35%) ⬆️

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 2c48687...5ac3d5b. Read the comment docs.

Copy link
Member

@bogdandrutu bogdandrutu left a comment

Choose a reason for hiding this comment

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

@anuraaga please confirm this is ok

@bogdandrutu bogdandrutu merged commit 6b181b7 into open-telemetry:main Mar 8, 2021
This was referenced Mar 15, 2021
pmatyjasek-sumo referenced this pull request in pmatyjasek-sumo/opentelemetry-collector-contrib Apr 28, 2021
ljmsc referenced this pull request in ljmsc/opentelemetry-collector-contrib Feb 21, 2022
* Optimize evictedQueue impl and use

Avoid unnecessary allocations in the recordingSpan by using an
evictedQueue type instead of a pointer to one.

Lazy allocate the evictedQueue queue to prevent unnecessary operations
for spans without any use of the queue.

Document the evictedQueue

* Fix grammar
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.

cloud.infrastructure_service incosistency
3 participants