Skip to content

Bump go.opentelemetry.io/otel/sdk from 0.11.0 to 0.12.0 in /exporter/stackdriverexporter #14

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

Bump go.opentelemetry.io/otel/sdk from 0.11.0 to 0.12.0 in /exporter/stackdriverexporter #14

wants to merge 1 commit into from

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Sep 28, 2020

Bumps go.opentelemetry.io/otel/sdk from 0.11.0 to 0.12.0.

Release notes

Sourced from go.opentelemetry.io/otel/sdk's releases.

Release v0.12.0

Added

  • A SpanConfigure function in go.opentelemetry.io/otel/api/trace to create a new SpanConfig from SpanOptions. (#1108)
  • In the go.opentelemetry.io/otel/api/trace package, NewTracerConfig was added to construct new TracerConfigs. This addition was made to conform with our project option conventions. (#1155)
  • Instrumentation library information was added to the Zipkin exporter. (#1119)
  • The SpanProcessor interface now has a ForceFlush() method. (#1166)
  • More semantic conventions for k8s as resource attributes. (#1167)

Changed

  • Add reconnecting udp connection type to Jaeger exporter. This change adds a new optional implementation of the udp conn interface used to detect changes to an agent's host dns record. It then adopts the new destination address to ensure the exporter doesn't get stuck. This change was ported from jaegertracing/jaeger-client-go#520. (#1063)
  • Replace StartOption and EndOption in go.opentelemetry.io/otel/api/trace with SpanOption. This change is matched by replacing the StartConfig and EndConfig with a unified SpanConfig. (#1108)
  • Replace the LinkedTo span option in go.opentelemetry.io/otel/api/trace with WithLinks. This is be more consistent with our other option patterns, i.e. passing the item to be configured directly instead of its component parts, and provides a cleaner function signature. (#1108)
  • The go.opentelemetry.io/otel/api/trace TracerOption was changed to an interface to conform to project option conventions. (#1109)
  • Move the B3 and TraceContext from within the go.opentelemetry.io/otel/api/trace package to their own go.opentelemetry.io/otel/propagators package. This removal of the propagators is reflective of the OpenTelemetry specification for these propagators as well as cleans up the go.opentelemetry.io/otel/api/trace API. (#1118)
  • Rename Jaeger tags used for instrumentation library information to reflect changes in OpenTelemetry specification. (#1119)
  • Rename ProbabilitySampler to TraceIDRatioBased and change semantics to ignore parent span sampling status. (#1115)
  • Move tools package under internal. (#1141)
  • Move go.opentelemetry.io/otel/api/correlation package to go.opentelemetry.io/otel/api/baggage. (#1142) The correlation.CorrelationContext propagator has been renamed baggage.Baggage. Other exported functions and types are unchanged.
  • Rename ParentOrElse sampler to ParentBased and allow setting samplers depending on parent span. (#1153)
  • In the go.opentelemetry.io/otel/api/trace package, SpanConfigure was renamed to NewSpanConfig. (#1155)
  • Change dependabot.yml to add a Skip Changelog label to dependabot-sourced PRs. (#1161)
  • The configuration style guide has been updated to recommend the use of newConfig() instead of configure(). (#1163)
  • The otlp.Config type has been unexported and changed to otlp.config, along with its initializer. (#1163)
  • Ensure exported interface types include parameter names and update the Style Guide to reflect this styling rule. (#1172)
  • Don't consider unset environment variable for resource detection to be an error. (#1170)
  • Rename go.opentelemetry.io/otel/api/metric.ConfigureInstrument to NewInstrumentConfig and go.opentelemetry.io/otel/api/metric.ConfigureMeter to NewMeterConfig.
  • ValueObserver instruments use LastValue aggregator by default. (#1165)
  • OTLP Metric exporter supports LastValue aggregation. (#1165)
  • Move the go.opentelemetry.io/otel/api/unit package to go.opentelemetry.io/otel/unit. (#1185)
  • Rename Provider to MeterProvider in the go.opentelemetry.io/otel/api/metric package. (#1190)
  • Rename NoopProvider to NoopMeterProvider in the go.opentelemetry.io/otel/api/metric package. (#1190)
  • Rename NewProvider to NewMeterProvider in the go.opentelemetry.io/otel/api/metric/metrictest package. (#1190)
  • Rename Provider to MeterProvider in the go.opentelemetry.io/otel/api/metric/registry package. (#1190)
  • Rename NewProvider to NewMeterProvider in the go.opentelemetry.io/otel/api/metri/registryc package. (#1190)
  • Rename Provider to TracerProvider in the go.opentelemetry.io/otel/api/trace package. (#1190)
  • Rename NoopProvider to NoopTracerProvider in the go.opentelemetry.io/otel/api/trace package. (#1190)
  • Rename Provider to TracerProvider in the go.opentelemetry.io/otel/api/trace/tracetest package. (#1190)
  • Rename NewProvider to NewTracerProvider in the go.opentelemetry.io/otel/api/trace/tracetest package. (#1190)

... (truncated)

Changelog

Sourced from go.opentelemetry.io/otel/sdk's changelog.

[0.12.0] - 2020-09-24

Added

  • A SpanConfigure function in go.opentelemetry.io/otel/api/trace to create a new SpanConfig from SpanOptions. (#1108)
  • In the go.opentelemetry.io/otel/api/trace package, NewTracerConfig was added to construct new TracerConfigs. This addition was made to conform with our project option conventions. (#1155)
  • Instrumentation library information was added to the Zipkin exporter. (#1119)
  • The SpanProcessor interface now has a ForceFlush() method. (#1166)
  • More semantic conventions for k8s as resource attributes. (#1167)

Changed

  • Add reconnecting udp connection type to Jaeger exporter. This change adds a new optional implementation of the udp conn interface used to detect changes to an agent's host dns record. It then adopts the new destination address to ensure the exporter doesn't get stuck. This change was ported from jaegertracing/jaeger-client-go#520. (#1063)
  • Replace StartOption and EndOption in go.opentelemetry.io/otel/api/trace with SpanOption. This change is matched by replacing the StartConfig and EndConfig with a unified SpanConfig. (#1108)
  • Replace the LinkedTo span option in go.opentelemetry.io/otel/api/trace with WithLinks. This is be more consistent with our other option patterns, i.e. passing the item to be configured directly instead of its component parts, and provides a cleaner function signature. (#1108)
  • The go.opentelemetry.io/otel/api/trace TracerOption was changed to an interface to conform to project option conventions. (#1109)
  • Move the B3 and TraceContext from within the go.opentelemetry.io/otel/api/trace package to their own go.opentelemetry.io/otel/propagators package. This removal of the propagators is reflective of the OpenTelemetry specification for these propagators as well as cleans up the go.opentelemetry.io/otel/api/trace API. (#1118)
  • Rename Jaeger tags used for instrumentation library information to reflect changes in OpenTelemetry specification. (#1119)
  • Rename ProbabilitySampler to TraceIDRatioBased and change semantics to ignore parent span sampling status. (#1115)
  • Move tools package under internal. (#1141)
  • Move go.opentelemetry.io/otel/api/correlation package to go.opentelemetry.io/otel/api/baggage. (#1142) The correlation.CorrelationContext propagator has been renamed baggage.Baggage. Other exported functions and types are unchanged.
  • Rename ParentOrElse sampler to ParentBased and allow setting samplers depending on parent span. (#1153)
  • In the go.opentelemetry.io/otel/api/trace package, SpanConfigure was renamed to NewSpanConfig. (#1155)
  • Change dependabot.yml to add a Skip Changelog label to dependabot-sourced PRs. (#1161)
  • The configuration style guide has been updated to recommend the use of newConfig() instead of configure(). (#1163)
  • The otlp.Config type has been unexported and changed to otlp.config, along with its initializer. (#1163)
  • Ensure exported interface types include parameter names and update the Style Guide to reflect this styling rule. (#1172)
  • Don't consider unset environment variable for resource detection to be an error. (#1170)
  • Rename go.opentelemetry.io/otel/api/metric.ConfigureInstrument to NewInstrumentConfig and go.opentelemetry.io/otel/api/metric.ConfigureMeter to NewMeterConfig.
  • ValueObserver instruments use LastValue aggregator by default. (#1165)
  • OTLP Metric exporter supports LastValue aggregation. (#1165)
  • Move the go.opentelemetry.io/otel/api/unit package to go.opentelemetry.io/otel/unit. (#1185)
  • Rename Provider to MeterProvider in the go.opentelemetry.io/otel/api/metric package. (#1190)
  • Rename NoopProvider to NoopMeterProvider in the go.opentelemetry.io/otel/api/metric package. (#1190)
  • Rename NewProvider to NewMeterProvider in the go.opentelemetry.io/otel/api/metric/metrictest package. (#1190)
  • Rename Provider to MeterProvider in the go.opentelemetry.io/otel/api/metric/registry package. (#1190)
  • Rename NewProvider to NewMeterProvider in the go.opentelemetry.io/otel/api/metri/registryc package. (#1190)
  • Rename Provider to TracerProvider in the go.opentelemetry.io/otel/api/trace package. (#1190)
  • Rename NoopProvider to NoopTracerProvider in the go.opentelemetry.io/otel/api/trace package. (#1190)
  • Rename Provider to TracerProvider in the go.opentelemetry.io/otel/api/trace/tracetest package. (#1190)

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 28, 2020
@mx-psi mx-psi closed this Sep 28, 2020
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Sep 28, 2020

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/go_modules/exporter/stackdriverexporter/go.opentelemetry.io/otel/sdk-0.12.0 branch September 28, 2020 14:40
jackgopack4 pushed a commit that referenced this pull request Feb 26, 2025
@NickAnge
feat(telemetrygen): added support for delta temporality (open-telemet…
27d7b1f 
…ry#38146)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description

This PR adds support for configuring metric temporality (delta or
cumulative) in the telemetrygen tool. This allows users to generate
metrics with different temporality types, which is particularly useful
for testing different metric collection scenarios.

##### Changes

- Added `temporalityType` flag for metrics pipeline that accepts values:
`delta` or `cumulative`


<!-- Issue number (e.g. #1234) or full URL to issue, if applicable. -->
#### Link to tracking issue
Fixes open-telemetry#38073 

<!--Describe what testing was performed and which tests were added.-->
#### Testing

Testing was performed by setting up as simple collector with `otlp
`receiver and `debug` exporter

##### Sum Datapoint

```
Resource SchemaURL: https://opentelemetry.io/schemas/1.13.0
Resource attributes:
     -> service.name: Str(telemetrygen)
ScopeMetrics #0
ScopeMetrics SchemaURL: 
InstrumentationScope  
Metric #0
Descriptor:
     -> Name: gen
     -> Description: 
     -> Unit: 
     -> DataType: Histogram
     -> AggregationTemporality: Delta
```

##### Histogram Datapoint

```
Count: 0
Sum: 3940.000000
ExplicitBounds #0: 0.000000
ExplicitBounds #1: 5.000000
ExplicitBounds #2: 10.000000
ExplicitBounds #3: 25.000000
ExplicitBounds #4: 50.000000
ExplicitBounds #5: 75.000000
ExplicitBounds #6: 100.000000
ExplicitBounds #7: 250.000000
ExplicitBounds #8: 500.000000
ExplicitBounds #9: 750.000000
ExplicitBounds #10: 1000.000000
ExplicitBounds #11: 2500.000000
ExplicitBounds #12: 5000.000000
ExplicitBounds #13: 7500.000000
ExplicitBounds #14: 10000.000000
Buckets #0, Count: 0
Buckets #1, Count: 0
Buckets #2, Count: 1
Buckets #3, Count: 0
Buckets #4, Count: 0
Buckets #5, Count: 0
Buckets #6, Count: 3
Buckets #7, Count: 4
Buckets #8, Count: 1
Buckets #9, Count: 1
Buckets #10, Count: 0
Buckets #11, Count: 0
Buckets #12, Count: 0
Buckets #13, Count: 0
Buckets #14, Count: 0
```


- [x] Need to add tests for the config

---------

Signed-off-by: Nikos Angelopoulos <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@mx-psi