Increased request latency discovered in 0.106.1 (> 0.105.0) #10858

arielvalentin · 2024-08-12T20:12:11Z

Describe the bug

This issue was originally reported in CNCF slack by Srinivas Bevara and confirmed by @codeboten who asked me to open this issue

After Upgrade to v0.106.1 from v0.104.0 we have run into issues where we see an increase in request latency being reported by both the collector's internal telemetry and our ingress proxies.

Memory remains unaffected however pprof is reporting garbage collection seems to have increased due internal telemetry tracing related allocations:

This is unexpected since tracing telemetry is disabled in our deployments.

Steps to reproduce

Run a load test comparing v0.104.0 and v0.106.1

What did you expect to see?

p99 Request latency and throughput should be comparable between both versions ~74ms
Internal telemetry must not generate recording spans when it is disabled

What did you see instead?

An increase in p99 latency to > 1s
Profiling reveals increased objected allocations related to internal telemetry span data
Profiling reveals an increase in time spent in GC

What version did you use?

v0.106.1

What config did you use?

Our configuration has many transformations and connector pipelines. The bare minimum you may likely need is the one you use for benchmarking.

Environment

Ubuntu 20.04.1

Additional context

Screen shots of increased p99 latency and CPU and steady memory

…are configured Previously the service was returning an instance of a SDK tracer provider regardless of whether there were any processors configured causing resources to be consumed unnecessarily. Fixes open-telemetry#10858 Signed-off-by: Alex Boten <[email protected]>

codeboten · 2024-08-12T23:23:55Z

After some discussion amongst maintainers, we want to provide a quick fix for this issue via the feature gate service.noopTracerProvider, and further investigate what's the cause of this problem before deciding if there should be a permanent configuration option to set a no-op tracer provider.

Returning a noop tracer provider if no tracing is configured in the telemetry settings would break the current behaviour, which the zpages extension relies on to provide telemetry about traces.

arielvalentin · 2024-08-13T01:19:34Z

Was there a recent change in zpages results in an increase in the number spans being allocated?

bvsvas · 2024-08-16T06:16:30Z

Thanks, @arielvalentin, for taking this up and raising a GitHub issue.

arielvalentin · 2024-08-16T15:41:30Z

@codeboten ~~did this feature flag make it into v0.107.0?~~

Yes it did https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.107.0

arielvalentin · 2024-08-24T15:20:53Z

I recently upgraded to v0.107.0 from v0.104.0. During off peak times performance is about on-par but during our high peak times our p99 skyrockets and memory spikes forcing the memory limiter to trigger hard limits responding with 503s.

I have enabled the feature gate to ensure we are using the noop-tracer but there still seems to be an increase in memory allocations and latency.

Our heavy usage of OTTL has not changed much between versions and as far as I can tell that is what appears the most in the profiles along with a high number of context objects being allocated by the noop-tracer.

profiles-20240823.tar.gz

codeboten · 2024-08-24T15:25:40Z

Re-opening to continue the investigation

TylerHelmuth · 2024-08-24T15:27:00Z

@arielvalentin Did the OTTL performance degrade, or are you saying it remained the majority?

arielvalentin · 2024-08-24T15:33:19Z

The profiles revealed that in 104 seemed to show OTTL execute was where it spent most of its time and allocations but our performance was pretty good ~15K spans per second per collector. p99 19ms.

Other than seeing the increased allocations to context objects related to nooptracer, the profiles between 104 and 107 look about the same to me so I don't have a reason to believe there is a regression in OTTL performance.

I'll see if I can dig up my 104 profiles and attach them as well.

pavolloffay · 2024-08-26T09:23:45Z

From @arielvalentin

I have enabled the feature gate to ensure we are using the noop-tracer but there still seems to be an increase in memory allocations and latency.

Other than seeing the increased allocations to context objects related to nooptracer, the profiles between 104 and 107 look about the same to me so I don't have a reason to believe there is a regression in OTTL performance.

So can be service.noopTracerProvider considered as a workaround?

iblancasa · 2024-08-26T09:30:48Z

So can be service.noopTracerProvider considered as a workaround?

I would say "no" because

there still seems to be an increase in memory allocations and latency.

codeboten · 2024-08-26T17:50:25Z

Investigating this further, this might be related to open-telemetry/opentelemetry-collector-contrib#33508

codeboten · 2024-08-26T18:41:55Z

I just ran load tests for v0.107.0 and here's what i have when i enabled the noop tracer provider feature gate:

Before using --feature-gates service.noopTracerProvider

With --feature-gates service.noopTracerProvider

This seems different than what you're seeing @arielvalentin, can you confirm that the feature gate is enabled?

arielvalentin · 2024-08-26T20:21:08Z

Yes. We currently run it with --feature-gates service.noopTracerProvider

You can see in the profiles I attached the noopTracer is used:

arielvalentin · 2024-08-26T21:24:05Z

Here are profiles for 104 profiles-104.tar.gz

codeboten · 2024-08-26T21:28:19Z

thanks @arielvalentin, I missed that when i looked your attached profiles a couple of days ago. good to know that using the no-op tracer provider at least reduces the overall memory consumption, even if its still higher than before the change to add tracing to ottl.

arielvalentin · 2024-08-27T14:49:36Z

No worries @codeboten

Something I may have not mentioned already, but my colleague @antonio had observed the latency regression as early as 105.

We may downgrade to 105 and collect profiles there as well.

antonio · 2024-08-27T15:20:50Z

Something I may have not mentioned already, but my colleague @antonio had observed the latency regression as early as 105.

That's correct. Notice how request duration went significantly up in the graph below, when I tested 105 back in July.

Investigating this further, this might be related to open-telemetry/opentelemetry-collector-contrib#33508

The time of when this PR was merged does indeed align with when we started seeing the issue.

BinaryFissionGames · 2024-08-28T02:56:38Z

Just adding what I've found here real quick;

I've done a quick benchmark to see the difference between an actual tracer impl, vs noop tracer, vs all tracing removed in ottl via the transform processor. You can see the benchmark here. All it does is run the transform processor with a batch of 100 logs, with a simple set operation (which seems like a pretty normal workload).

These are the results:

goos: darwin
goarch: arm64
pkg: github.com/open-telemetry/opentelemetry-collector-contrib/processor/transformprocessor
cpu: Apple M3 Pro
                 │ no-tracing.txt │           noop-tracer.txt            │           test-tracer.txt            │
                 │     sec/op     │    sec/op     vs base                │    sec/op     vs base                │
SetLogRecords-12      50.29µ ± 1%   120.55µ ± 4%  +139.70% (p=0.002 n=6)   426.21µ ± 5%  +747.43% (p=0.002 n=6)

                 │ no-tracing.txt │            noop-tracer.txt            │            test-tracer.txt            │
                 │      B/op      │     B/op       vs base                │     B/op       vs base                │
SetLogRecords-12     96.21Ki ± 0%   227.45Ki ± 0%  +136.42% (p=0.002 n=6)   758.38Ki ± 1%  +688.28% (p=0.002 n=6)

                 │ no-tracing.txt │           noop-tracer.txt           │           test-tracer.txt           │
                 │   allocs/op    │  allocs/op   vs base                │  allocs/op   vs base                │
SetLogRecords-12      1.402k ± 0%   3.802k ± 0%  +171.18% (p=0.002 n=6)   9.802k ± 0%  +599.14% (p=0.002 n=6)

You can see that even the noop tracer increases these benchmarks by quite a bit. And it adds up with what I'm seeing in both the issue I posted and here, which is that the overhead of tracing each individual evaluation of the StatementSequence seems like overkill.

Of course, if you do more processing in a single ottl statement, you'd probably get numbers that look a little less striking, so take the exact numbers here with a grain of salt. I don't think the scenario is all too unlikely, though.

It feels like there should not be tracing in StatementSequence at all, but maybe a few metric counters instead. The overhead of the tracing just doesn't seem worth it.

arielvalentin · 2024-08-28T15:19:21Z

I have got some more for you here v0.107.4 profiles-20240828.tar.gz

cc: @songy23

TylerHelmuth · 2024-08-28T16:05:34Z

I am going to submit a PR to revert the ottl tracing stuff.

iblancasa · 2024-08-28T16:43:17Z

I am going to submit a PR to revert the ottl tracing stuff.

How about placing it behind a feature gate?

arielvalentin · 2024-08-28T21:18:47Z

Thanks again for investigating. I am on the path to downgrade to 0.104.0 and will be eagerly awaiting the next release.

Once it's out, I will deploy to a subset of our canary instances and report back profiles and latency info.

arielvalentin · 2024-08-29T13:40:36Z

@bvsvas have you all had a chance to generate profiles?

IIRC you all were not using OTTL so the latency you all reported would not be related to the transformers right?

This is the snippet you posted in slack:

service:
  extensions: [apmauth, pprof]
  pipelines:
    traces:
      receivers: [otlp/withauth]
      processors: [probabilistic_sampler]
      exporters: [customexporter]
    metrics:
      receivers: [otlp/withauth, prometheus]
      processors: [cumulativetodelta, resource]
      exporters: [customexporter]

**Description:** Reverts #33508 since it was causing performance issues **Link to tracking Issue:** <Issue number if applicable> Reopens #33433 Related to open-telemetry/opentelemetry-collector#10858 Closes #34890

This is to address some of the memory concerns around the SDK's noop tracer provider. Instead of using the published noop tracer provider, we implement our own to avoid the cost of context propagation, which has been proven to be high enough to cause issues for end users. Part of open-telemetry#10858 Signed-off-by: Alex Boten <[email protected]>

arielvalentin · 2024-09-04T14:32:57Z

👋🏼 Is there a release schedule/project board handy I can subscribe to?

codeboten · 2024-09-04T18:38:11Z

The release schedule is documented here: https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/release.md#release-schedule

This is to address some of the memory concerns around the SDK's noop tracer provider. Instead of using the published noop tracer provider, we implement our own to avoid the cost of context propagation, which has been proven to be high enough to cause issues for end users. Part of open-telemetry#10858 Signed-off-by: Alex Boten <[email protected]>

This is to address some of the memory concerns around the SDK's noop tracer provider. Instead of using the published noop tracer provider, we implement our own to avoid the cost of context propagation, which has been proven to be high enough to cause issues for end users. Part of #10858 --------- Signed-off-by: Alex Boten <[email protected]>

* [chore]: enable bool-compare rule from testifylint (#34912) #### Description Testifylint is a linter that provides best practices with the use of testify. This PR enables [bool-compare](https://github.com/Antonboom/testifylint?tab=readme-ov-file#bool-compare) rule from [testifylint](https://github.com/Antonboom/testifylint) It's linter provided by golangci-lint. Here all available rules are activated except those who require to be fixed. This PR only fixes bool-compare so the quantity of changes stays reasonnable for reviewers. Signed-off-by: Matthieu MOREL <[email protected]> * [pkg/ottl] Remove tracing from OTTL (#34910) **Description:** Reverts https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/33508 since it was causing performance issues **Link to tracking Issue:** <Issue number if applicable> Reopens https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/33433 Related to https://github.com/open-telemetry/opentelemetry-collector/issues/10858 Closes https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34890 * [chore]: enable len rule from testifylint (#34921) #### Description Testifylint is a linter that provides best practices with the use of testify. This PR enables [len](https://github.com/Antonboom/testifylint?tab=readme-ov-file#len) rule from [testifylint](https://github.com/Antonboom/testifylint) * [chore][receiver/nginx] Update README for consistency (#34923) **Description:** <Describe what has changed.>  This just cleans up the README a bit: 1. Make case of `NGINX` consistent. Happy to change it to `nginx` if that's preferred. 2. Remove empty `Details` section 3. Cleanup description of the `collection_interval` config option. This is the same config option many other receivers have, so I don't think the concept needs explained in-depth here. 4. Remove disclaimer that the component's status is beta and configuration is subject to change. The README's header states this component is beta, so I don't think it needs to be repeated. * [processor/redaction] add support for redacting metrics and logs attributes (#34609) **Description:** This PR extends the redaction processor to also support the redaction of attributes within logs and metrics. **Link to tracking Issue:** #34479 **Testing:** Extended the existing unit tests to also cover the redaction of logs and metrics **Documentation:** Adapted the readme to reflect the changes --------- Signed-off-by: Florian Bacher <[email protected]> * [chore] Fix linter issues (#34937) **Description:** <Describe what has changed.>  #34609 and #34921 conflicted. This fixes CI * [receiver/gitproviderreceiver] rename to githubreceiver (#34731) **Description:** <Describe what has changed.> Renames `gitproviderreceiver` to `githubreceiver` to better align with OpenTelemetry Semantic Conventions v1.27.0+ and allow for tracing and log signals in the future. --------- Co-authored-by: Andrzej Stencel <[email protected]> Co-authored-by: Pablo Baeyens <[email protected]> * [chore][CODEOWNERS] Change account references to match new username (#34929) [Failing CI/CD action](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/10616610306/job/29427492169#step:16:13) Failure output: ``` cd cmd/githubgen && go install . githubgen 2024/08/2[9](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/10616610306/job/29427492169#step:16:10) 14:07:14 codeowners are not members: kkujawa-sumo make: *** [Makefile:296: gengithub] Error 1 ``` It appears that the user @kkujawa-sumo has been renamed to @kasia-kujawa. This updates all references to resolve our code owners check to ensure all code owners are members of the OpenTelemetry organization. * [chore] refactor filter processor test to use generated test harness (#34940) The code in telemetry_test.go was mostly doing something the code generated by mdatagen was doing. Updated the tests to use that instead. Signed-off-by: Alex Boten <[email protected]> * [chore] use generated test harness for groupbyattrs processor (#34941) Like https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34940 but for the groupsbyattrs processor. Signed-off-by: Alex Boten <[email protected]> * [chore] update core to pull in telemetry settings changes (#34930) Signed-off-by: Alex Boten <[email protected]> * [receiver/splunkhec] fix memory leak (#34911) **Description:** Fix memory leak when the receiver is used for both metrics and logs at the same time **Link to tracking Issue:** <Issue number if applicable> Fixes #34886 * [chore] Updating @MovieStoreGuy affiliation (#34947) * [chore]: Update README.md (#34725) Alolita Sharma works at Apple now. :) **Description:** <Describe what has changed.>  **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.> * [connector/servicegraph]Fix incorrectly reversed latency settings(resolve #34562 unit fail) (#34933) **Description:** <Describe what has changed.> This PR resolves the #34562 unit failure and adds back this bugfix after revert #34865. * [chore]: enable error-nil and nil-compare rules from testifylint (#34936) #### Description Testifylint is a linter that provides best practices with the use of testify. This PR enables [error-nil](https://github.com/Antonboom/testifylint?tab=readme-ov-file#error-nil) and [nil-compare](https://github.com/Antonboom/testifylint?tab=readme-ov-file#nil-compare) rules from [testifylint](https://github.com/Antonboom/testifylint) It also adds testifylint as tool to use with a make command * [connector/count] fix typo in metric.datapoint.count (#34961) **Documentation:** The documentation mentions a metric called "metric.data_point.count" but the metric is actually called "metric.datapoint.count" Co-authored-by: Sean Marciniak <[email protected]> * [chore] Upgrade arvo package (#34962) **Description:** Upgrading the arvo package used, it appears to be causing build issues on integer overflows * Update module github.com/shirou/gopsutil/v4 to v4.24.8 (#34970) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/shirou/gopsutil/v4](https://redirect.github.com/shirou/gopsutil) | `v4.24.7` -> `v4.24.8` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fshirou%2fgopsutil%2fv4/v4.24.8?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fshirou%2fgopsutil%2fv4/v4.24.8?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fshirou%2fgopsutil%2fv4/v4.24.7/v4.24.8?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fshirou%2fgopsutil%2fv4/v4.24.7/v4.24.8?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>shirou/gopsutil (github.com/shirou/gopsutil/v4)</summary> ### [`v4.24.8`](https://redirect.github.com/shirou/gopsutil/releases/tag/v4.24.8) [Compare Source](https://redirect.github.com/shirou/gopsutil/compare/v4.24.7...v4.24.8)  #### What's Changed ##### disk - fix(IOCountersWithContext): Fix the issue of not using names to fil ter devices in func IOCountersWithContext of the windows implementation by [@zmyzheng](https://redirect.github.com/zmyzheng) in [https://github.com/shirou/gopsutil/pull/1688](https://redirect.github.com/shirou/gopsutil/pull/1688) - \[disk]\[windows]: ignore network drive when not ready by [@shirou](https://redirect.github.com/shirou) in [https://github.com/shirou/gopsutil/pull/1699](https://redirect.github.com/shirou/gopsutil/pull/1699) ##### process - Fix parsing of /proc/pid/smaps when path is empty by [@pgimalac](https://redirect.github.com/pgimalac) in [https://github.com/shirou/gopsutil/pull/1691](https://redirect.github.com/shirou/gopsutil/pull/1691) - Refactoring the algorithm for calculating CPU usage by [@TheBestLL](https://redirect.github.com/TheBestLL) in [https://github.com/shirou/gopsutil/pull/1692](https://redirect.github.com/shirou/gopsutil/pull/1692) - Fix panic on OpenBSD and FreeBSD systems if KinfoProc size has an unexpected size by [@fivitti](https://redirect.github.com/fivitti) in [https://github.com/shirou/gopsutil/pull/1694](https://redirect.github.com/shirou/gopsutil/pull/1694) ##### Other Changes - Fix badge link in README.md by [@Yurunsoft](https://redirect.github.com/Yurunsoft) in [https://github.com/shirou/gopsutil/pull/1695](https://redirect.github.com/shirou/gopsutil/pull/1695) - fix golangcilint errors, ignore gosec G115 by [@shirou](https://redirect.github.com/shirou) in [https://github.com/shirou/gopsutil/pull/1697](https://redirect.github.com/shirou/gopsutil/pull/1697) - fix: golangci lint with max -> maxConn by [@shirou](https://redirect.github.com/shirou) in [https://github.com/shirou/gopsutil/pull/1693](https://redirect.github.com/shirou/gopsutil/pull/1693) #### New Contributors 🎉 - [@zmyzheng](https://redirect.github.com/zmyzheng) made their first contribution in [https://github.com/shirou/gopsutil/pull/1688](https://redirect.github.com/shirou/gopsutil/pull/1688) - [@Yurunsoft](https://redirect.github.com/Yurunsoft) made their first contribution in [https://github.com/shirou/gopsutil/pull/1695](https://redirect.github.com/shirou/gopsutil/pull/1695) - [@pgimalac](https://redirect.github.com/pgimalac) made their first contribution in [https://github.com/shirou/gopsutil/pull/1691](https://redirect.github.com/shirou/gopsutil/pull/1691) - [@TheBestLL](https://redirect.github.com/TheBestLL) made their first contribution in [https://github.com/shirou/gopsutil/pull/1692](https://redirect.github.com/shirou/gopsutil/pull/1692) - [@fivitti](https://redirect.github.com/fivitti) made their first contribution in [https://github.com/shirou/gopsutil/pull/1694](https://redirect.github.com/shirou/gopsutil/pull/1694) **Full Changelog**: https://github.com/shirou/gopsutil/compare/v4.24.7...v4.24.8 </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), 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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <[email protected]> * Update module github.com/ClickHouse/clickhouse-go/v2 to v2.28.2 (#34968) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/ClickHouse/clickhouse-go/v2](https://redirect.github.com/ClickHouse/clickhouse-go) | `v2.28.1` -> `v2.28.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fClickHouse%2fclickhouse-go%2fv2/v2.28.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fClickHouse%2fclickhouse-go%2fv2/v2.28.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fClickHouse%2fclickhouse-go%2fv2/v2.28.1/v2.28.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fClickHouse%2fclickhouse-go%2fv2/v2.28.1/v2.28.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>ClickHouse/clickhouse-go (github.com/ClickHouse/clickhouse-go/v2)</summary> ### [`v2.28.2`](https://redirect.github.com/ClickHouse/clickhouse-go/blob/HEAD/CHANGELOG.md#v2282-2024-08-30----Release-notes-generated-using-configuration-in-githubreleaseyml-at-main---) [Compare Source](https://redirect.github.com/ClickHouse/clickhouse-go/compare/v2.28.1...v2.28.2) #### What's Changed ##### Fixes 🐛 - Validate connection in bad state before query execution in the stdlib database/sql driver by [@jkaflik](https://redirect.github.com/jkaflik) in [https://github.com/ClickHouse/clickhouse-go/pull/1396](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1396) ##### Other Changes 🛠 - Update README with newer Go versions by [@jkaflik](https://redirect.github.com/jkaflik) in [https://github.com/ClickHouse/clickhouse-go/pull/1393](https://redirect.github.com/ClickHouse/clickhouse-go/pull/1393) **Full Changelog**: https://github.com/ClickHouse/clickhouse-go/compare/v2.28.1...v2.28.2 </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), 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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <[email protected]> * Update All github.com/datadog packages to v0.56.2 (#34965) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/DataDog/datadog-agent/comp/core/config](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2fconfig/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2fconfig/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2fconfig/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2fconfig/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/comp/core/hostname/hostnameinterface](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2fhostname%2fhostnameinterface/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2fhostname%2fhostnameinterface/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2fhostname%2fhostnameinterface/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2fhostname%2fhostnameinterface/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/comp/core/log](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2flog/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2flog/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2flog/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fcore%2flog/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/comp/logs/agent/config](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2flogs%2fagent%2fconfig/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2flogs%2fagent%2fconfig/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2flogs%2fagent%2fconfig/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2flogs%2fagent%2fconfig/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2flogsagentpipeline/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2flogsagentpipeline/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2flogsagentpipeline/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2flogsagentpipeline/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/comp/otelcol/logsagentpipeline/logsagentpipelineimpl](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2flogsagentpipeline%2flogsagentpipelineimpl/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2flogsagentpipeline%2flogsagentpipelineimpl/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2flogsagentpipeline%2flogsagentpipelineimpl/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2flogsagentpipeline%2flogsagentpipelineimpl/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/comp/otelcol/otlp/components/exporter/logsagentexporter](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fexporter%2flogsagentexporter/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fexporter%2flogsagentexporter/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fexporter%2flogsagentexporter/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fexporter%2flogsagentexporter/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/comp/otelcol/otlp/components/metricsclient](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fmetricsclient/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fmetricsclient/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fmetricsclient/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fmetricsclient/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/comp/otelcol/otlp/components/statsprocessor](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fstatsprocessor/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fstatsprocessor/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fstatsprocessor/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2fotelcol%2fotlp%2fcomponents%2fstatsprocessor/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/comp/trace/compression/impl-gzip](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2ftrace%2fcompression%2fimpl-gzip/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2ftrace%2fcompression%2fimpl-gzip/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2ftrace%2fcompression%2fimpl-gzip/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fcomp%2ftrace%2fcompression%2fimpl-gzip/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/pkg/config/model](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fconfig%2fmodel/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fconfig%2fmodel/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fconfig%2fmodel/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fconfig%2fmodel/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/pkg/config/setup](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fconfig%2fsetup/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fconfig%2fsetup/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fconfig%2fsetup/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fconfig%2fsetup/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/pkg/logs/sources](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2flogs%2fsources/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2flogs%2fsources/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2flogs%2fsources/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2flogs%2fsources/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/pkg/obfuscate](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fobfuscate/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fobfuscate/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fobfuscate/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fobfuscate/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/pkg/proto](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fproto/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fproto/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fproto/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2fproto/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/pkg/trace](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2ftrace/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2ftrace/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2ftrace/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2ftrace/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | | [github.com/DataDog/datadog-agent/pkg/util/hostname/validate](https://redirect.github.com/DataDog/datadog-agent) | `v0.56.0` -> `v0.56.2` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2futil%2fhostname%2fvalidate/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2futil%2fhostname%2fvalidate/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2futil%2fhostname%2fvalidate/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fdatadog-agent%2fpkg%2futil%2fhostname%2fvalidate/v0.56.0/v0.56.2?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), 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 these updates again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <[email protected]> * Update module github.com/snowflakedb/gosnowflake to v1.11.1 (#34971) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/snowflakedb/gosnowflake](https://redirect.github.com/snowflakedb/gosnowflake) | `v1.11.0` -> `v1.11.1` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fsnowflakedb%2fgosnowflake/v1.11.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fsnowflakedb%2fgosnowflake/v1.11.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fsnowflakedb%2fgosnowflake/v1.11.0/v1.11.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fsnowflakedb%2fgosnowflake/v1.11.0/v1.11.1?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>snowflakedb/gosnowflake (github.com/snowflakedb/gosnowflake)</summary> ### [`v1.11.1`](https://redirect.github.com/snowflakedb/gosnowflake/releases/tag/v1.11.1): Release [Compare Source](https://redirect.github.com/snowflakedb/gosnowflake/compare/v1.11.0...v1.11.1) - Please check Snowflake [community page for release notes](https://docs.snowflake.com/en/release-notes/clients-drivers/golang). </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), 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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <[email protected]> * [exporter/loki] Document the migration from the Loki Exporter to the Loki V3 OTLP endpoint (#34918) **Description:** <Describe what has changed.> Document how to migrate from the now deprecated OTel Collector Loki Exporter to the new Loki V3 OTLP endpoint and new OTel log format --------- Co-authored-by: Curtis Robert <[email protected]> Co-authored-by: Sandeep Sukhani <[email protected]> * [connector/spanmetrics] Improve consistency between metrics generated by spanmetricsconnector (#34485) **Link to tracking Issue:** #33227 #32818 **Documentation:** added an entry to the changelog explaining the deprecated metrics. --------- Signed-off-by: Israel Blancas <[email protected]> Signed-off-by: Juraci Paixão Kröhling <[email protected]> Co-authored-by: Murphy Chen <[email protected]> Co-authored-by: Rafael Pax <[email protected]> Co-authored-by: Juraci Paixão Kröhling <[email protected]> * Update module google.golang.org/grpc to v1.66.0 (#34978) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [google.golang.org/grpc](https://redirect.github.com/grpc/grpc-go) | `v1.65.0` -> `v1.66.0` | [![age](https://developer.mend.io/api/mc/badges/age/go/google.golang.org%2fgrpc/v1.66.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/google.golang.org%2fgrpc/v1.66.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/google.golang.org%2fgrpc/v1.65.0/v1.66.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/google.golang.org%2fgrpc/v1.65.0/v1.66.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>grpc/grpc-go (google.golang.org/grpc)</summary> ### [`v1.66.0`](https://redirect.github.com/grpc/grpc-go/releases/tag/v1.66.0): Release 1.66.0 [Compare Source](https://redirect.github.com/grpc/grpc-go/compare/v1.65.0...v1.66.0) ### New Features - metadata: stabilize `ValueFromIncomingContext` ([#7368](https://redirect.github.com/grpc/grpc-go/issues/7368)) - Special Thanks: [@KarthikReddyPuli](https://redirect.github.com/KarthikReddyPuli) - client: stabilize the `WaitForStateChange` and `GetState` methods, which were previously experimental. ([#7425](https://redirect.github.com/grpc/grpc-go/issues/7425)) - xds: Implement ADS flow control mechanism ([#7458](https://redirect.github.com/grpc/grpc-go/issues/7458)) - See [https://github.com/grpc/grpc/issues/34099](https://redirect.github.com/grpc/grpc/issues/34099) for context. - balancer/rls: Add metrics for data cache and picker internals ([#7484](https://redirect.github.com/grpc/grpc-go/issues/7484), [#7495](https://redirect.github.com/grpc/grpc-go/issues/7495)) - xds: LRS load reports now include the `total_issued_requests` field. ([#7544](https://redirect.github.com/grpc/grpc-go/issues/7544)) ### Bug Fixes - grpc: Clients now return status code INTERNAL instead of UNIMPLEMENTED when the server uses an unsupported compressor. This is consistent with the [gRPC compression spec](https://redirect.github.com/grpc/grpc/blob/master/doc/compression.md#compression-method-asymmetry-between-peers). ([#7461](https://redirect.github.com/grpc/grpc-go/issues/7461)) - Special Thanks: [@Gayathri625](https://redirect.github.com/Gayathri625) - transport: Fix a bug which could result in writes busy looping when the underlying `conn.Write` returns errors ([#7394](https://redirect.github.com/grpc/grpc-go/issues/7394)) - Special Thanks: [@veshij](https://redirect.github.com/veshij) - client: fix race that could lead to orphaned connections and associated resources. ([#7390](https://redirect.github.com/grpc/grpc-go/issues/7390)) - xds: use locality from the connected address for load reporting with pick_first ([#7378](https://redirect.github.com/grpc/grpc-go/issues/7378)) - without this fix, if a priority contains multiple localities with pick_first, load was reported for the wrong locality - client: prevent hanging during ClientConn.Close() when the network is unreachable ([#7540](https://redirect.github.com/grpc/grpc-go/issues/7540)) ### Performance Improvements - transport: double buffering is avoided when using an http connect proxy and the target server waits for client to send the first message. ([#7424](https://redirect.github.com/grpc/grpc-go/issues/7424)) - codec: Implement a new `Codec` which uses buffer recycling for encoded message ([#7356](https://redirect.github.com/grpc/grpc-go/issues/7356)) - introduce a `mem` package to facilitate buffer reuse ([#7432](https://redirect.github.com/grpc/grpc-go/issues/7432)) - Special Thanks: [@PapaCharlie](https://redirect.github.com/PapaCharlie) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), 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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <[email protected]> * [vcenterreceiver] Updated units on several metrics (#34946) **Description:** <Describe what has changed.>  The following change works to update several metrics units to be more inline with the semantics declared here: https://opentelemetry.io/docs/specs/semconv/general/metrics/#instrument-units Specifically it changes all the uses of `sec` to `s` and also updates the incorrect unit usage of `{MHz}` to `MHz` on a couple metrics. **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> All golden package tests were updated, as well as integration tests. **Documentation:** <Describe the documentation added.> Documentation was updated with mdatagen with the use of `make generate` * Update module github.com/SAP/go-hdb to v1.12.0 (#34973) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [github.com/SAP/go-hdb](https://redirect.github.com/SAP/go-hdb) | `v1.11.3` -> `v1.12.0` | [![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fSAP%2fgo-hdb/v1.12.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fSAP%2fgo-hdb/v1.12.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fSAP%2fgo-hdb/v1.11.3/v1.12.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | [![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fSAP%2fgo-hdb/v1.11.3/v1.12.0?slim=true)](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>SAP/go-hdb (github.com/SAP/go-hdb)</summary> ### [`v1.12.0`](https://redirect.github.com/SAP/go-hdb/blob/HEAD/RELEASENOTES.md#v1120) [Compare Source](https://redirect.github.com/SAP/go-hdb/compare/v1.11.3...v1.12.0) ##### Changes - Changed 'prometheus' into own go module to reduce dependencies on go-hdb. </details> --- ### Configuration 📅 **Schedule**: Branch creation - "on tuesday" (UTC), 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. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).  --------- Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: opentelemetrybot <[email protected]> Co-authored-by: Yang Song <[email protected]> * [chore][pkg/stanza] Speed up file deduplication in finder (#34888) **Description:** <Describe what has changed.> For large numbers of files, the logic that deduplicates the filenames between matches is costly. This is mainly due to the O(n^2) deduping algorithm used. If we instead use a map (as a hashset), we can make this ~O(n). This PR speeds up the deduplication logic, as well as adds a benchmark for a case where the filelog receiver is polling many files at once. **Testing:** <Describe what testing was performed and which tests were added.> Running the added benchmark and comparing with benchstat, we can see a large increase in speed for the large number of files case (10000 monitored files), at the cost of a very slight increase in memory usage: ``` goos: darwin goarch: arm64 pkg: github.com/open-telemetry/opentelemetry-collector-contrib/pkg/stanza/fileconsumer/matcher/internal/finder cpu: Apple M3 Pro │ old.txt │ new.txt │ │ sec/op │ sec/op vs base │ Find10kFiles-12 198.636m ± 6% 8.696m ± 16% -95.62% (p=0.002 n=6) │ old.txt │ new.txt │ │ B/op │ B/op vs base │ Find10kFiles-12 5.416Mi ± 0% 5.581Mi ± 0% +3.04% (p=0.002 n=6) │ old.txt │ new.txt │ │ allocs/op │ allocs/op vs base │ Find10kFiles-12 80.06k ± 0% 80.25k ± 0% +0.23% (p=0.002 n=6) ``` * [receiver/mysql] client, convert NULL to int64 (#34411) **Description:** <Describe what has changed.> bug fix, receiver/mysql client.go raise error when the TABLE_ROWS column is NULL, fix it in the SQL query, convert the NULL to 0. **Link to tracking Issue:** <Issue number if applicable> https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34195 **Testing:** <Describe what testing was performed and which tests were added.> run command "make test" in the receiver/mysqlreceiver, all the test case passed. **Documentation:** <Describe the documentation added.> --------- Signed-off-by: Jian Li <[email protected]> * [testbed] - Add scenarios to handle large files (#34417) **Description:** Add test cases covering large files to existing testbed. This PR adds following scenarios: Scenario 1: Ensure that all logs are captured for files that reach a size of 2GB. Scenario 2: Ensure that all logs are captured for files that reach a size of 6GB Scenario 3: Ensure that all logs are captured for a file of approximately 1.5GB that contains prewritten data. **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34288 **Testing:** Added --------- Co-authored-by: Antoine Toulme <[email protected]> * Avoid rendering the whole event to get only the provider name (#34914) **Description:** The code was always getting the event as a XML string that was unmarshalled into a type only to obtain the provider name. That can be done in a cheaper fashion by requesting the `System` properties of the event and reading only the provider name. **Link to tracking Issue:** Fixes #34755 **Testing:** The benchmark below is only good to compare memory usage, which shows that this change is already beneficial. See the changes for the benchmark code. ```terminal goos: windows goarch: amd64 pkg: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/windowseventlogreceiver cpu: Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz │ .\old.txt │ .\pr.txt │ │ sec/op │ sec/op vs base │ ReadWindowsEventLogger/10-16 1.255 ± 0% 1.255 ± 0% ~ (p=0.912 n=10) ReadWindowsEventLogger/100-16 1.379 ± 9% 1.256 ± 0% ~ (p=0.190 n=10) ReadWindowsEventLogger/1_000-16 2.633 ± 5% 2.507 ± 0% ~ (p=0.063 n=10) geomean 1.658 1.581 -4.62% │ .\old.txt │ .\pr.txt │ │ B/op │ B/op vs base │ ReadWindowsEventLogger/10-16 3.228Mi ± 6% 2.190Mi ± 8% -32.17% (p=0.000 n=10) ReadWindowsEventLogger/100-16 5.399Mi ± 42% 2.276Mi ± 4% -57.85% (p=0.000 n=10) ReadWindowsEventLogger/1_000-16 26.12Mi ± 8% 17.66Mi ± 4% -32.38% (p=0.000 n=10) geomean 7.693Mi 4.448Mi -42.18% │ .\old.txt │ .\pr.txt │ │ allocs/op │ allocs/op vs base │ ReadWindowsEventLogger/10-16 67.18k ± 7% 44.74k ± 9% -33.40% (p=0.000 n=10) ReadWindowsEventLogger/100-16 112.87k ± 42% 46.69k ± 4% -58.64% (p=0.000 n=10) ReadWindowsEventLogger/1_000-16 551.6k ± 8% 368.0k ± 4% -33.28% (p=0.000 n=10) geomean 161.1k 91.61k -43.14% ``` **Documentation:** N/A * [chore] add Tyler to CODEOWNERS for githubreceiver (#34963) **Description:** Adding @TylerHelmuth (GitHub Actions Receiver component sponsor) as codeowner in the GitHub Receiver after the decision to incorporate the tracing and log capability mentioned in #27460 into the GitHub receiver was made. * Update README.md (#34990) I think this URL has changed? * [extension/opamp] Add support for polling interval in HTTP client (#34811) **Description:** <Describe what has changed.>  Adds support for configuring polling interval for the OpAMP HTTP client. **Link to tracking Issue:** #34749 **Testing:** Adjusted unit test, manually tested **Documentation:** Added to README --------- Signed-off-by: Matej Gera <[email protected]> Co-authored-by: Evan Bradley <[email protected]> * [receiver/apache] Invalid endpoint should not cause panic (#34992) **Description:** The receiver crashes if it fails to parse the endpoint. **Link to tracking Issue:** N/A **Testing:** Add a test covering this case. **Documentation:** Changelog updated. * [chore]: enable compares and empty rules from testifylint (#34976) #### Description Testifylint is a linter that provides best practices with the use of testify. This PR enables [compares](https://github.com/Antonboom/testifylint?tab=readme-ov-file#compares) and [empty](https://github.com/Antonboom/testifylint?tab=readme-ov-file#empty) rules from [testifylint](https://github.com/Antonboom/testifylint) Signed-off-by: Matthieu MOREL <[email protected]> * [receiver/githubreceiver] promote githubreceiver to alpha status (#34960) **Description:** Promotes the GitHub receiver to alpha status --------- Co-authored-by: Sean Marciniak <[email protected]> * [connector/datadog] Improve performance in cases with many peer tags (#34945) **Description:** Improves performance of Datadog connector when there are many peer tags and `connector.datadogconnector.NativeIngest` is enabled **Link to tracking Issue:** Related to https://github.com/DataDog/datadog-agent/pull/28908 **Testing:** Added new benchmark tests, results: ``` % go test -bench . -benchmem -benchtime=1000x goos: darwin goarch: arm64 pkg: github.com/open-telemetry/opentelemetry-collector-contrib/connector/datadogconnector cpu: Apple M1 Max BenchmarkPeerTags_Native-10 1000 22851735 ns/op 9147 B/op 118 allocs/op BenchmarkPeerTags_Legacy-10 1000 27704684 ns/op 12157 B/op 152 allocs/op PASS ``` * [chore] upgrading pulsar client v0.13.1 (#34951) **Description:** Upgraded client and fix https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34213 * [processor/interval] Update config structure for interval processor (#34926) **Description:** This PR addresses comments made in #34805 after it was merged The gist is change in configuration from ```yaml interval: 60s gauge_pass_through: false summary_pass_through: false ``` to ```yaml interval: 60s pass_through: gauge: false summary: false ``` **Link to tracking Issue:** #34920 Signed-off-by: Arthur Silva Sens <[email protected]> * [extension/solarwindsapmsettingsextension] Added remaining implementation of solarwindsapmsettingsextension (#33315) **Description:** <Describe what has changed.>  - Added logic for `refresh` function **Link to tracking Issue:** <Issue number if applicable> [27668](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/27668) **Testing:** <Describe what testing was performed and which tests were added.> Manually tested against test server ``` extensions: solarwindsapmsettings: endpoint: "apm-testcollector.click:443" key: "any:any" service: extensions: [solarwindsapmsettings] ``` **Documentation:** <Describe the documentation added.> - Updated README to remove the support of `/tmp/solarwinds-apm-settings-raw` file --------- Co-authored-by: Antoine Toulme <[email protected]> * feat: Support Prometheus Created Timestamps (#34596) **Description:** exporter/prometheusexporter now supports Prometheus Created Timestamps. **Link to tracking Issue:** Fix #32521 **Testing:** Unit tests were extended with the new scope **Documentation:** No documentation was added so far, looking for direction about where would be the best place for it :) Signed-off-by: Arthur Silva Sens <[email protected]> * [receiver/sqlquery] support attributes for logs (#34599) **Description:** Introduced a new configuration option, attribute_columns, for log queries. This option was already available for metric queries. Note: If an attribute column is missing in the result set, the collection process fails with an error to maintain consistency with metric query behaviour. Conversely, in the existing implementation, if the body column is absent, log body will be populated with an empty string. For consistency, it might be preferable for both behaviours to align. However, since this could introduce a breaking change, it may be more appropriate to implement this adjustment in a separate PR. **Link to tracking Issue:** [24459](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/24459) **Testing:** Added column `attribute` in test set, and verification in the integration test **Documentation:** Migrated description for `attribute_columns` from metrics queries section to general "Queries" section, updated example configuration --------- Co-authored-by: Curtis Robert <[email protected]> * [receiver/kafkareceiver]: allow tunable fetch sizes (#34431) **Description:** This commit adds the ability to tune the minimum, default and maximum fetch sizes for the Kafka Receiver in the OpenTelemetry configuration file. The defaults are kept consistent with the defaults imposed by [sarama](https://pkg.go.dev/github.com/shopify/sarama#Config) **Link to tracking Issue:** Resolves https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/22741 **Testing:** Built the image with `make docker-otelcontribcol`, uploaded to [Docker Hub](https://hub.docker.com/r/ckaczynski/otelcontribcol) to pull the image into our Kubernetes deployment, and hit the cluster with 200k logs per second with the following settings: ``` default_fetch_size: 15728640 # 15MB max_fetch_size: 31457280 # 30MB min_fetch_size: 1048576 # 1MB ``` These limits are absurdly high for no reason other than because I just wanted to set them higher and see how far I could push it in our cluster. No new tests were added, but added to existing configuration tests in config.go and factory.go **Documentation:** Added the new configuration options to the receiver's README --------- Co-authored-by: Israel Blancas <[email protected]> Co-authored-by: Sean Marciniak <[email protected]> * [exporter/splunkhec] drop empty log events (#34871) **Description:** Drop empty log events Log records with no body are dropped by Splunk on reception as they contain no log message, albeit they may have attributes. This PR removes those logs from consideration to be exported. This is in tune with the behavior of splunkhecreceiver, which refuses HEC events with no event (#19769) * [exporter/signalfx] Fix goroutine leaks (#32781) **Description:** This change is a refactor to allow us to enable `goleak` checks in each of the exporter's sub-directories, as well as the signalfx receiver (which uses the signalfxexporter in a test). The main idea is to use `start`/`shutdown` for each package's functionality, rather than relying on the top level context cancel of the exporter. The addition of start and shutdowns for each package means we can more closely control the lifecycle of each as needed, and enable `goleak` for each package. The memory leaks being fixed are: 1. Call the `TTLMap.Shutdown` so the ticker is properly stopped: `t.prevPts.Shutdown()`. 2. Don't block waiting for a request if the context is cancelled. **Link to tracking issue:** #30438 --------- Co-authored-by: Sean Marciniak <[email protected]> * [chore] make update-otel to 48b11ba (#34956) Bumps core libraries to open-telemetry/opentelemetry-collector@48b11ba1c5f83497aa09604a7d0ac7e7c3d93a5d --------- Signed-off-by: Pablo Baeyens <[email protected]> * [chore][receiver/filelog] Change plaintext name: filelog -> file log (#34984) **Description:** <Describe what has changed.>  Updated the name of the file log receiver to be two words. Updated some references as well where I thought it made sense, reviewers are welcome to suggest changes. **Link to tracking Issue:** <Issue number if applicable> Resolves #34943 * [chore] Fix flaky test by ignoring metrics order (#35002) See https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/10696785646/job/29652663151?pr=34985#step:6:570 * fix: handle OTLPJSON unmarshal error (#34784) **Description:** <Describe what has changed.>  Handles the error that the Unmarshaler can return in case an invalid OTLPJSON is provided, this avoids sending a nil signal to the corresponding consumer. The fix logs the error and continues the execution: ```go t, err := tracesUnmarshaler.UnmarshalTraces([]byte(token.AsString())) if err != nil { c.logger.Error("could extract traces from otlp json", zap.Error(err)) continue } ``` **Link to tracking Issue:** <Issue number if applicable> https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/34782 **Testing:** <Describe what testing was performed and which tests were added.> Factory tests moved to connector tests using the `golden` + compare testing packages. Testdata includes a file with an invalid json for each signal. **Documentation:** <Describe the documentation added.> NA * [chore] Fix flaky test in filelog receiver (#35012) Quick fix for https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/35007. Ideally we should not need to depend on order of files returned from the finder but there are apparently some subtle implications which need to be better understood before we remove the assumption. * Bump github.com/opencontainers/runc from 1.1.13 to 1.1.14 in /cmd/otelcontribcol (#34991) Bumps [github.com/opencontainers/runc](https://github.com/opencontainers/runc) from 1.1.13 to 1.1.14. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/opencontainers/runc/releases">github.com/opencontainers/runc's releases</a>.</em></p> <blockquote> <h2>runc v1.1.14 -- "年を取っていいことは、驚かなくなることね。"</h2> <p>This is the fourteenth patch release in the 1.1.z release branch of runc. It includes a fix for a low severity security issue (CVE-2024-45310) as well as some minor build-related fixes (including Go 1.23 support).</p> <ul> <li>Fix <a href="https://github.com/opencontainers/runc/security/advisories/GHSA-jfvp-7x6p-h2pv">CVE-2024-45310</a>, a low-severity attack that allowed maliciously configured containers to create empty files and directories on the host.</li> <li>Add support for Go 1.23. (<a href="https://redirect.github.com/opencontainers/runc/issues/4360">#4360</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4372">#4372</a>)</li> <li>Revert "allow overriding VERSION value in Makefile" and add EXTRA_VERSION. (<a href="https://redirect.github.com/opencontainers/runc/issues/4370">#4370</a>, <a href="https://redirect.github.com/opencontainers/runc/issues/4382">#4382</a>)</li> <li>rootfs: consolidate mountpoint creation logic. (<a href="https://redirect.github.com/opencontainers/runc/issues/4359">#4359</a>)</li> </ul> <h3>Static Linking Notices</h3> <p>The <code>runc</code> binary distributed with this release are <em>statically linked</em> with the following <a href="https://www.gnu.org/licenses/old-licenses/lgpl-2.1.en.html">GNU LGPL-2.1</a> licensed libraries, with <code>runc</code> acting as a "work that uses the Library":</p> <ul> <li><a href="https://github.com/seccomp/libseccomp">libseccomp</a></li> </ul> <p>The versions of these libraries were not modified from their upstream versions, but in order to comply with the LGPL-2.1 (§6(a)), we have attached the complete source code for those libraries which (when combined with the attached runc source code) may be used to exercise your rights under the LGPL-2.1.</p> <p>However we strongly suggest that you make use of your distribution's packages or download them from the authoritative upstream sources, especially since these libraries are related to the security of your containers.</p>  <p>Thanks to all of the contributors who made this release possible:</p> <ul> <li>Akihiro Suda <a href="mailto:[email protected]">akihiro.s…

**Description:** Reverts open-telemetry#33508 since it was causing performance issues **Link to tracking Issue:** <Issue number if applicable> Reopens open-telemetry#33433 Related to open-telemetry/opentelemetry-collector#10858 Closes open-telemetry#34890

arielvalentin added the bug Something isn't working label Aug 12, 2024

codeboten mentioned this issue Aug 12, 2024

[service] Allow users to disable the tracer provider via the feature gate service.noopTracerProvider #10859

Merged

dmitryax closed this as completed in #10859 Aug 12, 2024

dmitryax closed this as completed in 998412c Aug 12, 2024

codeboten reopened this Aug 24, 2024

TylerHelmuth mentioned this issue Aug 27, 2024

[processor/transform] Tracing taking more CPU resources than expected open-telemetry/opentelemetry-collector-contrib#34890

Closed

This was referenced Aug 28, 2024

[pkg/ottl] Remove tracing from OTTL open-telemetry/opentelemetry-collector-contrib#34910

Merged

Tracing overhead and memory usage open-telemetry/opentelemetry-go#5410

Open

arielvalentin changed the title ~~Increased request latency in 0.106.1~~ Increased request latency discovered in 0.106.1 (> 0.105.0) Aug 29, 2024

codeboten mentioned this issue Aug 30, 2024

[service] implement a noop tracer provider #11026

Merged

codeboten mentioned this issue Sep 9, 2024

Provide mechanism to disable internal tracing #10481

Open

codeboten mentioned this issue Dec 11, 2024

tracer newRecordingSpan memory leak #11875

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Increased request latency discovered in 0.106.1 (> 0.105.0) #10858

Increased request latency discovered in 0.106.1 (> 0.105.0) #10858

arielvalentin commented Aug 12, 2024 •

edited

Loading

codeboten commented Aug 12, 2024

arielvalentin commented Aug 13, 2024

bvsvas commented Aug 16, 2024

arielvalentin commented Aug 16, 2024 •

edited

Loading

arielvalentin commented Aug 24, 2024

codeboten commented Aug 24, 2024

TylerHelmuth commented Aug 24, 2024

arielvalentin commented Aug 24, 2024

pavolloffay commented Aug 26, 2024

iblancasa commented Aug 26, 2024

codeboten commented Aug 26, 2024

codeboten commented Aug 26, 2024

arielvalentin commented Aug 26, 2024

arielvalentin commented Aug 26, 2024

codeboten commented Aug 26, 2024

arielvalentin commented Aug 27, 2024

antonio commented Aug 27, 2024 •

edited

Loading

BinaryFissionGames commented Aug 28, 2024

arielvalentin commented Aug 28, 2024 •

edited

Loading

TylerHelmuth commented Aug 28, 2024

iblancasa commented Aug 28, 2024

arielvalentin commented Aug 28, 2024

arielvalentin commented Aug 29, 2024

arielvalentin commented Sep 4, 2024

codeboten commented Sep 4, 2024

Increased request latency discovered in 0.106.1 (> 0.105.0) #10858

Increased request latency discovered in 0.106.1 (> 0.105.0) #10858

Comments

arielvalentin commented Aug 12, 2024 • edited Loading

codeboten commented Aug 12, 2024

arielvalentin commented Aug 13, 2024

bvsvas commented Aug 16, 2024

arielvalentin commented Aug 16, 2024 • edited Loading

arielvalentin commented Aug 24, 2024

codeboten commented Aug 24, 2024

TylerHelmuth commented Aug 24, 2024

arielvalentin commented Aug 24, 2024

pavolloffay commented Aug 26, 2024

iblancasa commented Aug 26, 2024

codeboten commented Aug 26, 2024

codeboten commented Aug 26, 2024

arielvalentin commented Aug 26, 2024

arielvalentin commented Aug 26, 2024

codeboten commented Aug 26, 2024

arielvalentin commented Aug 27, 2024

antonio commented Aug 27, 2024 • edited Loading

BinaryFissionGames commented Aug 28, 2024

arielvalentin commented Aug 28, 2024 • edited Loading

TylerHelmuth commented Aug 28, 2024

iblancasa commented Aug 28, 2024

arielvalentin commented Aug 28, 2024

arielvalentin commented Aug 29, 2024

arielvalentin commented Sep 4, 2024

codeboten commented Sep 4, 2024

arielvalentin commented Aug 12, 2024 •

edited

Loading

arielvalentin commented Aug 16, 2024 •

edited

Loading

antonio commented Aug 27, 2024 •

edited

Loading

arielvalentin commented Aug 28, 2024 •

edited

Loading