-
Notifications
You must be signed in to change notification settings - Fork 0
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
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.102.0 #41
Merged
ymotongpoo
merged 1 commit into
main
from
renovate/go.opentelemetry.io-collector-exporter-0.x
Jun 5, 2024
Merged
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.102.0 #41
ymotongpoo
merged 1 commit into
main
from
renovate/go.opentelemetry.io-collector-exporter-0.x
Jun 5, 2024
Conversation
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
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.92.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.93.0
Jan 24, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
January 24, 2024 06:12
f6520c6
to
e225346
Compare
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
February 7, 2024 01:07
e225346
to
783fe68
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.93.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.94.0
Feb 7, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
February 8, 2024 01:11
783fe68
to
a05ac84
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.94.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.94.1
Feb 8, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
February 20, 2024 18:47
a05ac84
to
8201574
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.94.1
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.95.0
Feb 20, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
March 4, 2024 16:56
8201574
to
80add9c
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.95.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.96.0
Mar 4, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
March 25, 2024 23:18
80add9c
to
9fd0ec3
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.96.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.97.0
Mar 25, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
April 10, 2024 23:43
9fd0ec3
to
cc08af1
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.97.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.98.0
Apr 10, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
April 22, 2024 22:43
cc08af1
to
4a78f1d
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.98.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.99.0
Apr 22, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
May 6, 2024 19:19
4a78f1d
to
0a3aaf8
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.99.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.100.0
May 6, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
May 21, 2024 23:07
0a3aaf8
to
1a84ca5
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.100.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.101.0
May 21, 2024
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
June 4, 2024 11:42
1a84ca5
to
753c68d
Compare
renovate
bot
changed the title
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.101.0
fix(deps): update module go.opentelemetry.io/collector/exporter to v0.102.0
Jun 4, 2024
ℹ Artifact update noticeFile name: exporter/discordexporter/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
2 times, most recently
from
June 4, 2024 12:04
5666280
to
b0a8802
Compare
renovate
bot
force-pushed
the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
from
June 4, 2024 12:05
b0a8802
to
6b5d969
Compare
renovate
bot
deleted the
renovate/go.opentelemetry.io-collector-exporter-0.x
branch
June 5, 2024 01:20
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
v0.91.0
->v0.102.0
Release Notes
open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/exporter)
v0.102.0
Compare Source
🛑 Breaking changes 🛑
envprovider
: Restricts Environment Variable names. Environment variable names must now be ASCII only and start with a letter or an underscore, and can only contain underscores, letters, or numbers. (#9531)confighttp
: Apply MaxRequestBodySize to the result of a decompressed body (#10289)When using compressed payloads, the Collector would verify only the size of the compressed payload.
This change applies the same restriction to the decompressed content. As a security measure, a limit of 20 MiB was added, which makes this a breaking change.
For most clients, this shouldn't be a problem, but if you often have payloads that decompress to more than 20 MiB, you might want to either configure your
client to send smaller batches (recommended), or increase the limit using the MaxRequestBodySize option.
💡 Enhancements 💡
mdatagen
: auto-generate utilities to test component telemetry (#19783)mdatagen
: support setting an AttributeSet for async instruments (#9674)mdatagen
: support using telemetry level in telemetry builder (#10234)This allows components to set the minimum level needed for them to produce telemetry. By default, this is set to configtelemetry.LevelBasic. If the telemetry level is below that minimum level, then the noop meter is used for metrics.
mdatagen
: add support for bucket boundaries for histograms (#10218)releases
: add documentation in how to verify the image signatures using cosign (#9610)🧰 Bug fixes 🧰
batchprocessor
: ensure attributes are set on cardinality metadata metric (#9674)batchprocessor
: Fixing processor_batch_metadata_cardinality which was broken in v0.101.0 (#10231)batchprocessor
: respect telemetry level for all metrics (#10234)exporterhelper
: Fix potential deadlocks in BatcherSender shutdown (#10255)v0.101.0
Compare Source
💡 Enhancements 💡
mdatagen
: generate documentation for internal telemetry (#10170)mdatagen
: add ability to use metadata.yaml to automatically generate instruments for components (#10054)The
telemetry
section in metadata.yaml is used to generateinstruments for components to measure telemetry about themselves.
confmap
: Allow Converters to write logs during startup (#10135)otelcol
: Enable logging during configuration resolution (#10056)🧰 Bug fixes 🧰
mdatagen
: Run package tests when goleak is skipped (#10125)v0.100.0
Compare Source
🛑 Breaking changes 🛑
service
: Thevalidate
sub-command no longer validates that each pipeline's type is the same as its component types (#10031)💡 Enhancements 💡
semconv
: Add support for v1.25.0 semantic convention (#10072)builder
: remove the need to go get a module to address ambiguous import paths (#10015)pmetric
: Support parsing metric.metadata from OTLP JSON. (#10026)🧰 Bug fixes 🧰
exporterhelper
: Fix enabled config option for batch sender (#10076)v0.99.0
Compare Source
🛑 Breaking changes 🛑
builder
: Add strict version checking when using the builder. Add the temporary flag--skip-strict-versioning
for skipping this check. (#9896)Strict version checking will error on major and minor version mismatches
between the
otelcol_version
configured and the builder version or versionsin the go.mod. This check can be temporarily disabled by using the
--skip-strict-versioning
flag. This flag will be removed in a future minor version.
telemetry
: Distributed internal metrics across different levels. (#7890)The internal metrics levels are updated along with reported metrics:
basic
tonormal
, which can be overridden withservice::telmetry::metrics::level
configuration.normal
level:processor_batch_batch_send_size
processor_batch_metadata_cardinality
processor_batch_timeout_trigger_send
processor_batch_size_trigger_send
detailed
level:💡 Enhancements 💡
confighttp
: Disable concurrency in zstd compression (#8216)cmd/builder
: Allow configuringconfmap.Provider
s in the builder. (#4759)If no providers are specified, the defaults are used.
The default providers are: env, file, http, https, and yaml.
To configure providers, use the
providers
key in your OCB buildmanifest with a list of Go modules for your providers.
The modules will work the same as other Collector components.
mdatagen
: enable goleak tests by default via mdatagen (#9959)cmd/mdatagen
: support excluding some metrics based on string and regexes in resource_attributes (#9661)cmd/mdatagen
: Generate config and factory tests covering their requirements. (#9940)The tests are moved from cmd/builder.
confmap
: AddProviderSettings
,ConverterSettings
,ProviderFactories
, andConverterFactories
fields toconfmap.ResolverSettings
(#9516)This allows configuring providers and converters, which are instantiated by
NewResolver
using the given factories.🧰 Bug fixes 🧰
exporter/otlp
: Allow DNS scheme to be used in endpoint (#4274)service
: fix record sampler configuration (#9968)service
: ensure the tracer provider is configured via go.opentelemetry.io/contrib/config (#9967)otlphttpexporter
: Fixes a bug that was preventing the otlp http exporter from propagating status. (#9892)confmap
: Fix decoding negative configuration values into uints (#9060)v0.98.0
Compare Source
🛑 Breaking changes 🛑
service
: emit internal collector metrics with _ instead of / with OTLP export (#9774)This is addressing an issue w/ the names of the metrics generated by the Collector for its
internal metrics. Note that this change only impacts users that emit telemetry using OTLP, which
is currently still in experimental support. The prometheus metrics already replaced
/
with_
and they will do the same with
_
.💡 Enhancements 💡
mdatagen
: Adds unsupported platforms to the README header (#9794)confmap
: Clarify the use of embedded structs to make unmarshaling composable (#7101)nopexporter
: Promote the nopexporter to beta (#7316)nopreceiver
: Promote the nopreceiver to beta (#7316)otlpexporter
: Checks for port in the config validation for the otlpexporter (#9505)service
: Validate pipeline type against component types (#8007)🧰 Bug fixes 🧰
configtls
: Fix issue whereIncludeSystemCACertsPool
was not consistently used betweenServerConfig
andClientConfig
. (#9835)component
: Fix issue where thecomponents
command wasn't properly printing the component type. (#9856)otelcol
: Fix issue where thevalidate
command wasn't properly printing valid component type. (#9866)receiver/otlp
: Fix bug where the otlp receiver did not properly respond with a retryable error code when possible for http (#9357)v0.97.0
Compare Source
🛑 Breaking changes 🛑
telemetry
: Remove telemetry.useOtelForInternalMetrics stable feature gate (#9752)🚀 New components 🚀
exporter/nop
: Add thenopexporter
to serve as a placeholder exporter in a pipeline (#7316)This is primarily useful for starting the Collector with only extensions enabled
or to test Collector pipeline throughput.
receiver/nop
: Add thenopreceiver
to serve as a placeholder receiver in a pipeline (#7316)This is primarily useful for starting the Collector with only extensions enabled.
💡 Enhancements 💡
configtls
: Validates TLS min_version and max_version (#9475)Introduces
Validate()
method in TLSSetting.configcompression
: Mark module as Stable. (#9571)cmd/mdatagen
: Use go package name for the scope name by default and add an option to provide the scope name in metadata.yaml. (#9693)cmd/mdatagen
: Generate the lifecycle tests for components by default. (#9683)It's encouraged to have lifecycle tests for all components enadled, but they can be disabled if needed
in metadata.yaml with
skip_lifecycle: true
andskip_shutdown: true
undertests
section.cmd/mdatagen
: optimize the mdatagen for the case like batchprocessor which use a common struct to implement consumer.Traces, consumer.Metrics, consumer.Logs in the meantime. (#9688)🧰 Bug fixes 🧰
exporterhelper
: Fix persistent queue size backup on reads. (#9740)processor/batch
: Prevent starting unnecessary goroutines. (#9739)otlphttpexporter
: prevent error on empty response body when content type is application/json (#9666)confmap
: confmap honorsUnmarshal
methods on config embedded structs. (#6671)otelcol
: Respect telemetry configuration when running as a Windows service (#5300)v0.96.0
Compare Source
🛑 Breaking changes 🛑
configgrpc
: Remove deprecatedGRPCClientSettings
,GRPCServerSettings
, andServerConfig.ToListenerContext
. (#9616)confighttp
: Remove deprecatedHTTPClientSettings
,NewDefaultHTTPClientSettings
, andCORSSettings
. (#9625)confignet
: Removes deprecatedNetAddr
andTCPAddr
(#9614)💡 Enhancements 💡
configtls
: Addinclude_system_ca_certs_pool
to configtls, allowing to load system certs and additional custom certs. (#7774)otelcol
: AddConfigProviderSettings
toCollectorSettings
(#4759)This allows passing a custom list of
confmap.Provider
s tootelcol.NewCommand
.pdata
: Update to OTLP v1.1.0 (#9587)Introduces Span and SpanLink flags.
confmap
: Update mapstructure to use a maintained fork, github.com/go-viper/mapstructure/v2. (#9634)https://github.com/mitchellh/mapstructure/issues/349/349 for context.
🧰 Bug fixes 🧰
configretry
: Allow max_elapsed_time to be set to 0 for indefinite retries (#9641)client
: MakeMetadata.Get
thread safe (#9595)v0.95.0
Compare Source
🛑 Breaking changes 🛑
all
: scope name for all generated Meter/Tracer funcs now includes full package name (#9494)💡 Enhancements 💡
confighttp
: Adds support for Snappy decompression of HTTP requests. (#7632)configretry
: Validatemax_elapsed_time
, ensure it is larger thanmax_interval
andinitial_interval
respectively. (#9489)configopaque
: Mark module as stable (#9167)otlphttpexporter
: Add support for json content encoding when exporting telemetry (#6945)confmap/converter/expandconverter, confmap/provider/envprovider, confmap/provider/fileprovider, confmap/provider/httprovider, confmap/provider/httpsprovider, confmap/provider/yamlprovider
: Split confmap.Converter and confmap.Provider implementation packages out of confmap. (#4759, #9460)v0.94.1
Compare Source
This patch release reverts a dependency update that caused intermittent test failures.
v0.94.0
Compare Source
🛑 Breaking changes 🛑
receiver/otlp
: Update gRPC code fromcodes.InvalidArgument
tocodes.Internal
when a permanent error doesn't contain a gRPC status (#9415)🚩 Deprecations 🚩
configgrpc
: Deprecate GRPCClientSettings, use ClientConfig instead (#6767)💡 Enhancements 💡
mdatagen
: Add a generated test that checks the config struct usingcomponenttest.CheckConfigStruct
(#9438)component
: Addcomponent.UseLocalHostAsDefaultHost
feature gate that changes default endpoints from 0.0.0.0 to localhost (#8510)The only component in this repository affected by this is the OTLP receiver.
confighttp
: Add support of Host header (#9395)mdatagen
: Remove use of ReportFatalError in generated tests (#9439)🧰 Bug fixes 🧰
service
: fix opencensus bridge configuration in periodic readers (#9361)otlpreceiver
: Fix goroutine leak when GRPC server is started but HTTP server is unsuccessful (#9165)otlpexporter
: PartialSuccess is treated as success, logged as warning. (#9243)v0.93.0
Compare Source
🛑 Breaking changes 🛑
exporterhelper
: remove deprecated exporterhelper.RetrySettings and exporterhelper.NewDefaultRetrySettings (#9256)configopaque
: configopaque.String implementsfmt.Stringer
andfmt.GoStringer
, outputting [REDACTED] when formatted with the %s, %q or %#v verbs(#​9213) This may break applications that rely on the previous behavior of opaque strings with
fmt.Sprintfto e.g. build URLs or headers. Explicitly cast the opaque string to a string before using it in
fmt.Sprintf` to restore the previous behavior.🚀 New components 🚀
extension/memory_limiter
: Introduce amemory_limiter
extension which receivers can use to reject incoming requests when collector doesn't have enough memory (#8632)The extension has the same configuration interface and behavior as the existing
memory_limiter
processor, which potentially can be deprecated and removed in the future💡 Enhancements 💡
configtls
: addcipher_suites
to configtls. (#8105)Users can specify a list of cipher suites to pick from. If left blank, a safe default list is used.
service
: marktelemetry.useOtelForInternalMetrics
as stable (#816)exporters
: Cleanup log messages for export failures (#9219)Keep the "dropped" wording for failures happened after the enabled queue.
🧰 Bug fixes 🧰
configgrpc
: Update dependency to address a potential crash in the grpc instrumentation (#9296)otlpreceiver
: Ensure OTLP receiver handles consume errors correctly (#4335)Make sure OTLP receiver returns correct status code and follows the receiver contract (gRPC)
zpagesextension
: Remove mention of rpcz page from zpages extension (#9328)v0.92.0
Compare Source
🛑 Breaking changes 🛑
exporters/sending_queue
: Do not re-enqueue failed batches, rely on the retry_on_failure strategy instead. (#8382)The current re-enqueuing behavior is not obvious and cannot be configured. It takes place only for persistent queue
and only if
retry_on_failure::enabled=true
even ifretry_on_failure
is a setting for a different backoff retrystrategy. This change removes the re-enqueuing behavior. Consider increasing
retry_on_failure::max_elapsed_time
to reduce chances of data loss or set it to 0 to keep retrying until requests succeed.
confmap
: Make the optionWithErrorUnused
enabled by default when unmarshaling configuration (#7102)The option
WithErrorUnused
is now enabled by default, and a new optionWithIgnoreUnused
is introduced to ignoreerrors about unused fields.
status
: DeprecateReportComponentStatus
in favor ofReportStatus
. This new function does not return an error. (#9148)🚩 Deprecations 🚩
connectortest
: Deprecate connectortest.New[Metrics|Logs|Traces]Router in favour of connector.New[Metrics|Logs|Traces]Router (#9095)exporterhelper
: Deprecate exporterhelper.RetrySettings in favor of configretry.BackOffConfig (#9091)extension/ballast
: Deprecatememory_ballast
extension. (#8343)Use
GOMEMLIMIT
environment variable instead.connector
: Deprecate [Metrics|Logs|Traces]Router in favour of [Metrics|Logs|Traces]RouterAndConsumer (#9095)💡 Enhancements 💡
exporterhelper
: Add RetrySettings validation function (#9089)Validate that time.Duration, multiplier values in configretry are non-negative, and randomization_factor is between 0 and 1
service
: Enabletelemetry.useOtelForInternalMetrics
by updating the flag to beta (#7454)The metrics generated should be consistent with the metrics generated
previously with OpenCensus. Users can disable the behaviour
by setting
--feature-gates -telemetry.useOtelForInternalMetrics
atcollector start.
mdatagen
: move component from contrib to core (#9172)semconv
: Generated Semantic conventions 1.22.0. (#8686)confignet
: Adddialer_timeout
config option. (#9066)processor/memory_limiter
: Update config validation errors (#9059)exporterhelper
: Add config Validate for TimeoutSettings (#9104)🧰 Bug fixes 🧰
memorylimiterprocessor
: Fixed leaking goroutines from memorylimiterprocessor (#9099)cmd/otelcorecol
: Fix the code detecting if the collector is running as a service on Windows. (#7350)Removed the
NO_WINDOWS_SERVICE
environment variable given it is not needed anymore.otlpexporter
: remove dependency of otlphttpreceiver on otlpexporter (#6454)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.