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

feat: enable dns instrumentation by default #1543

Merged
merged 2 commits into from
Sep 22, 2020

Conversation

naseemkullah
Copy link
Member

Which problem is this PR solving?

Short description of the changes

  • added dns to the list of enabled plugins
  • adjust README accordingly, and mention the new hapi and koa plugins

@naseemkullah
Copy link
Member Author

This should be followed up by a duplicate README change in the contrib repo.

@naseemkullah naseemkullah changed the title feat: enable dns tracing by default feat: enable dns instrumentation by default Sep 17, 2020
also updates README to reflect the change, while adding links to hapi
and koa instrumentation that were missing
@codecov
Copy link

codecov bot commented Sep 17, 2020

Codecov Report

Merging #1543 into master will increase coverage by 1.09%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1543      +/-   ##
==========================================
+ Coverage   92.72%   93.82%   +1.09%     
==========================================
  Files          66      154      +88     
  Lines        1733     4762    +3029     
  Branches      360      951     +591     
==========================================
+ Hits         1607     4468    +2861     
- Misses        126      294     +168     
Impacted Files Coverage Δ
packages/opentelemetry-node/src/config.ts 100.00% <ø> (ø)
packages/opentelemetry-core/src/context/context.ts 95.83% <0.00%> (ø)
...kages/opentelemetry-web/src/StackContextManager.ts 97.05% <0.00%> (ø)
...metry-core/src/context/propagation/B3Propagator.ts 100.00% <0.00%> (ø)
...ore/src/correlation-context/correlation-context.ts 100.00% <0.00%> (ø)
...ckages/opentelemetry-core/src/common/attributes.ts
...resource-detector-gcp/src/detectors/GcpDetector.ts 95.55% <0.00%> (ø)
...emetry-core/src/platform/node/RandomIdGenerator.ts 87.50% <0.00%> (ø)
...detector-aws/src/detectors/AwsBeanstalkDetector.ts 95.23% <0.00%> (ø)
...sync-hooks/src/AbstractAsyncHooksContextManager.ts 98.11% <0.00%> (ø)
... and 92 more

@dyladan dyladan added the enhancement New feature or request label Sep 21, 2020
@naseemkullah
Copy link
Member Author

@naseemkullah naseemkullah deleted the enable-dns branch September 29, 2020 04:25
pichlermarc pushed a commit to dynatrace-oss-contrib/opentelemetry-js that referenced this pull request Dec 15, 2023
…try#1543)

chore: fix typo in test description

Noticed ECS on Fargate is missing some cloud resource attributes.
Comparing similar implementations like the Go ECS detector (https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/5fff1040a2844d4d435359b8108202317762593d/processor/resourcedetectionprocessor/internal/aws/ecs/ecs.go#L69);
they determine these missing values based on the metadata. This implements them in a similar fashion.

Co-authored-by: Haddas Bronfman <85441461+haddasbronfman@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants