[pull] main from open-telemetry:main #27
Merged
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
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
Signed-off-by: Alex Boten <[email protected]>
…#27185) **Description:** Allow metadata extractions to be empty list After this is merged, user is allow to specify the metadata to be empty list like following ``` processors: k8sattributes: extract: annotations: - from: pod key: workload tag_name: k8s.annotations.workload labels: - from: pod key: app tag_name: k8s.labels.app metadata: [] ``` **Link to tracking Issue:** fix #14452 --------- Signed-off-by: Ziqi Zhao <[email protected]> Co-authored-by: Dmitrii Anoshin <[email protected]>
The following commands were run to prepare this release: - make chlog-update VERSION=v0.86.0 - sed -i.bak s/0.85.0/0.86.0/g versions.yaml - make multimod-prerelease - make multimod-sync Fixes #27199 --------- Signed-off-by: Alex Boten <[email protected]>
**Description:** Add metadata map for pod and container requests and limits. Will be used to calculate new metrics in a future PR. **Link to tracking Issue:** <Issue number if applicable> #24905 **Testing:** <Describe what testing was performed and which tests were added.> added unit tests
…7210) [](https://renovatebot.com) This PR contains the following updates: | Package | Update | Change | |---|---|---| | [otel/opentelemetry-collector-contrib](https://togithub.com/open-telemetry/opentelemetry-collector-releases) | minor | `0.85.0` -> `0.86.0` | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector-releases (otel/opentelemetry-collector-contrib)</summary> ### [`v0.86.0`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.86.0) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector-releases/compare/v0.85.0...v0.86.0) #### Changelog - [`0f47e46`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/0f47e46) \[chore] prepare v0.86.0 release ([#​409](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/409)) - [`12d8bb5`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/12d8bb5) Bump github.com/goreleaser/nfpm/v2 from 2.32.0 to 2.33.1 ([#​406](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/406)) - [`bf8002e`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/bf8002e) Add support for linux/s390x architecture ([#​384](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/384)) - [`3d5a87e`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/3d5a87e) add routing connector to contrib release ([#​405](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/405)) - [`51982c4`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/51982c4) Bump docker/login-action from 2 to 3 ([#​404](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/404)) - [`63090ea`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/63090ea) Bump docker/setup-buildx-action from 2 to 3 ([#​402](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/402)) - [`8d6c8f2`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/8d6c8f2) Bump docker/setup-qemu-action from 2 to 3 ([#​401](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/401)) - [`a50f8b1`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/a50f8b1) Bump goreleaser/goreleaser-action from 4 to 5 ([#​403](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/403)) </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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNi4xMDcuMiIsInVwZGF0ZWRJblZlciI6IjM2LjEwNy4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
Bump github.com/antonmedv/expr from 1.15.2 to 1.15.3 in /pkg/stanza Bump github.com/antonmedv/expr from 1.15.2 to 1.15.3 in /receiver/receivercreator Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.45.12 to 1.45.16 in /receiver/awsxrayreceiver Bump github.com/aws/aws-sdk-go-v2/config from 1.18.40 to 1.18.42 in /exporter/awskinesisexporter Bump github.com/aws/aws-sdk-go-v2/config from 1.18.40 to 1.18.42 in /extension/sigv4authextension Bump github.com/aws/aws-sdk-go-v2/credentials from 1.13.38 to 1.13.40 in /exporter/awskinesisexporter Bump github.com/aws/aws-sdk-go-v2/credentials from 1.13.38 to 1.13.40 in /extension/sigv4authextension Bump github.com/aws/aws-sdk-go-v2/service/kinesis from 1.18.5 to 1.19.0 in /exporter/awskinesisexporter Bump github.com/hashicorp/consul/api from 1.24.0 to 1.25.1 in /internal/metadataproviders Bump github.com/hashicorp/consul/api from 1.24.0 to 1.25.1 in /processor/resourcedetectionprocessor Bump github.com/influxdata/influxdb-observability/common from 0.5.7 to 0.5.8 in /exporter/influxdbexporter Bump github.com/influxdata/influxdb-observability/common from 0.5.7 to 0.5.8 in /receiver/influxdbreceiver Bump github.com/influxdata/influxdb-observability/influx2otel from 0.5.7 to 0.5.8 in /receiver/influxdbreceiver Bump github.com/influxdata/influxdb-observability/otel2influx from 0.5.7 to 0.5.8 in /exporter/influxdbexporter Bump github.com/sijms/go-ora/v2 from 2.7.17 to 2.7.18 in /receiver/sqlqueryreceiver Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.750 to 1.0.756 in /exporter/tencentcloudlogserviceexporter Bump github.com/vmware/govmomi from 0.30.7 to 0.31.0 in /receiver/vcenterreceiver Bump go.opentelemetry.io/build-tools/checkfile from 0.11.0 to 0.12.0 in /internal/tools Bump go.opentelemetry.io/build-tools/chloggen from 0.11.0 to 0.12.0 in /internal/tools Bump go.opentelemetry.io/build-tools/crosslink from 0.11.0 to 0.12.0 in /internal/tools Bump go.opentelemetry.io/build-tools/issuegenerator from 0.11.0 to 0.12.0 in /internal/tools Bump go.opentelemetry.io/build-tools/multimod from 0.11.0 to 0.12.0 in /internal/tools Bump google.golang.org/api from 0.141.0 to 0.143.0 in /exporter/f5cloudexporter Bump google.golang.org/api from 0.141.0 to 0.143.0 in /exporter/googlecloudpubsubexporter Bump google.golang.org/api from 0.141.0 to 0.143.0 in /receiver/googlecloudpubsubreceiver Bump google.golang.org/api from 0.141.0 to 0.143.0 in /receiver/googlecloudspannerreceiver Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /cmd/telemetrygen Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /examples/demo/client Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /examples/demo/server Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /exporter/coralogixexporter Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /exporter/googlecloudpubsubexporter Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /exporter/opencensusexporter Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /exporter/skywalkingexporter Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /extension/asapauthextension Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /extension/basicauthextension Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /extension/bearertokenauthextension Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /extension/headerssetterextension Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /extension/jaegerremotesampling Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /extension/oauth2clientauthextension Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /extension/sigv4authextension Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /processor/routingprocessor Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /processor/spanmetricsprocessor Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /receiver/googlecloudpubsubreceiver Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /receiver/googlecloudspannerreceiver Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /receiver/jaegerreceiver Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /receiver/opencensusreceiver Bump google.golang.org/grpc from 1.58.1 to 1.58.2 in /receiver/skywalkingreceiver
This PR migrates all tests in the `split` package to the new framework. Notable changes: - No longer a need to have special non-standard tests. These are either redundant, or were absorbed into the standard pattern. - Flush at EOF tests moved into standard pattern. - Encoded newline tests moved into standard pattern. - Removes tests relating to flushing, as these are a concern of the `flush` package now. - Removes tests relating to trimming, as these are a concern of the `trim` package now. - Removes tests for buffer overflow, as these were caused by using `bufio.Scanner`.
This updates the code examples to use the debug exporter instead of the logging exporter. This change will need to be merged after the v0.86.0 release. --------- Signed-off-by: Alex Boten <[email protected]>
Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /exporter/awsemfexporter Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /exporter/kafkaexporter Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /internal/aws/xray/testdata/sampleapp Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /processor/resourcedetectionprocessor Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /receiver/awscontainerinsightreceiver Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /receiver/awsecscontainermetricsreceiver Bump github.com/aws/aws-sdk-go from 1.45.16 to 1.45.17 in /receiver/awsxrayreceiver
…ampled` metric (#26724) **Description:** Previously, the calculation of `count_traces_sampled` was incorrect, resulting in all per-policy metric counts being the same. ``` count_traces_sampled{policy="policy-a", sampled="false"} 50 count_traces_sampled{policy="policy-a", sampled="true"} 50 count_traces_sampled{policy="policy-b", sampled="false"} 50 count_traces_sampled{policy="policy-b", sampled="true"} 50 ``` This issue stemmed from the metrics being incremented based on the final decision of trace sampling, rather than being attributed to the policies causing the sampling. With the fix implemented, the total sampling count can no longer be inferred from the metrics alone. To address this, a new metric, `global_count_traces_sampled`, was introduced to accurately capture the global count of sampled traces. ``` count_traces_sampled{policy="policy-a", sampled="false"} 50 count_traces_sampled{policy="policy-a", sampled="true"} 50 count_traces_sampled{policy="policy-b", sampled="false"} 24 count_traces_sampled{policy="policy-b", sampled="true"} 76 global_count_traces_sampled{sampled="false"} 24 global_count_traces_sampled{sampled="true"} 76 ``` Reusing the `count_traces_sampled` policy metric for this purpose would have either meant: 1. Leaving the policy field empty, which didn't feel very explicit. 2. Setting a global placeholder policy name (such as `final-decision`), which could then potentially collide with existing user-configured policy names without validation. **Link to tracking Issue:** Fixes #25882 **Testing:** Tested with various combinations of `probabilistic`, `latency`, `status_code` and attribute policies (including combinations of `and` and `composite` policies). No unit tests were added, open to suggestions for adding tests for metrics but I couldn't find any examples of it being done elsewhere. **Documentation:** No documentation changes.
**Description:** This PR adds contrib to the list of distributions for the datadogconnector (related PR: open-telemetry/opentelemetry-collector-releases#389). This PR also adds a section in the README of the processor which links to the setup instructions of the connector.
This was missed in a previous merge. Fixes #27245 Signed-off-by: Alex Boten <[email protected]>
…24543) Enhances azuremonitor receiver authentication by using [azure workload identity](https://azure.github.io/azure-workload-identity/docs/). I have added a new config parameter `auth` to specify the used authentication method (default set to service-principal) in order to possibly add more methods in the future. Fixes #24451 **Testing:** Tested on my AKS
…account auth (#27070) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Fix to use the `insecure_skip_verify` config in http client when connecting with kubelet in service account auth mode. **Link to tracking Issue:** [26319](#26319) **Testing:** <Describe what testing was performed and which tests were added.> Unit tests added, e2e test updated **Documentation:** <Describe the documentation added.>
Fix #25843 The issue is that the `go` tool generates directories as per its build OS, so on Windows, `go list -f '{{ .Dir }}' ./...` outputs paths in Windows format, e.g.: "c:\src\otel-col-contrib", however, the tools used by the make expect paths to be in Unix format. This change adds a `sed` expression to convert the Windows paths to Unix paths so they can be passed to tools like `find`.
**Description:** - Adds additional metrics to Splunk Enterprise receiver obtained from API endpoints - Updates tests and docs for these additional metrics **Link to tracking Issue:** #12667 **Testing:** - Additional tests for new endpoints and metrics added to `scraper_test` - Verify current tests also pass **Documentation:** - Newly generated docs entries for additional metrics
**Description:** Implement a first codec for the encoding extension. **Link to tracking Issue:** https://github.com/open-telemetry/opentelemetry-collector/issues/6272 **Testing:** Unit tests. **Documentation:** Some package docs. --------- Co-authored-by: Dmitrii Anoshin <[email protected]>
**Description:** Enable support to extract headers from Kafka Messages and attach them to resource attributes. In later stages in the pipeline, different exporters can utilize this information. **Link to tracking Issue:** [21729](#21729) **Testing:** Added test cases for logs, traces, and metrics. **Documentation:** <Describe the documentation added.> --------- Co-authored-by: Alex Boten <[email protected]>
**Description:** Adds new `k8s.pod.memory.utilization` and `container.memory.utilization` metrics that represent the ratio of memory used vs limits set. The metrics are only emitted for pods/containers that have defined resource limits. It takes advantage of the pod metadata to acquire the container limits. A pod limit is computed as the sum of all the container limits and if any container limit is zero or undefined the pod limit is also considered undefined. **Link to tracking Issue:** Related to #24905 **Testing:** Unit tests and local testing
**Description:** This PR creates a gh action that generates a weekly report on repo statistics. It delivers on the requirements specified in #24672 You can see the sample output here: kevinslin#16 **Link to tracking Issue:** #24672 **Testing:** Manual testing in fork: https://github.com/kevinslin/opentelemetry-collector-contrib/actions Example output: kevinslin#17 **Documentation:** The architecture: - we use `actions/github-script@v6` to make calls to the gh apis - we require installing `js-yaml` in order to parse `metadata.yaml` files in order to get components. this dependency is installed during the github action run and not persisted Some caveats about the logic: - when this action runs, it looks back the previous 7 days and gets issues created in that time period, normalizing times to UTC - eg. if running this on wednesday (eg. 2023-08-25 17:35:00), it will scan issues from the previous wednesday (2023-08-18 00:00:00Z) to beginning of this wednesday (2023-08-28 0:00:00Z) - this action writes the json payload of the report inside the issue. the payload is parsed by future reports to calculate deltas - the report issue has a custom label: `report` - this is used so we can properly filter previous issues when calculating deltas. the [github issues api](https://docs.github.com/en/rest/issues/issues?apiVersion=2022-11-28#list-repository-issues) only does filtering based on labels and `since` date This action currently runs every Tuesday at 1AM UTC --------- Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Tyler Helmuth <[email protected]>
Picking up codeowners from .GITHUB/CODEOWNERS
**Description:** <Describe what has changed.> Allows setting empty metric units in mdatagen. Example of using it https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/27091/files **Tracking Issues:** #27089 #10553
**Description:** The existing k8s example configures the filelog receiver to `start_at: beginning`. This results in a significant amount of data to be ingested on startup, and significant duplicate data on a collector restart. I propose we recommend using `start_at:end` for default k8s log ingestion.
This overhauls a document in `pkg/stanza` which describes how to chain operators together. - Disambiguates the term "pipelines" but introducing the term "operator sequences". - Reworks all examples to show the context of being used in a full receiver configuration. - Removes references to input and output operators, which are either abstracted or unused. - Removes some extraneous examples. - Clarifies how to output from a non-linear pipeline.
**Description:** Test for open-telemetry/opentelemetry-collector/pull/8723
This PR just streamlines some test code.
Follows: #28206 This PR fixes a setup problem with a particular test and further enhances it to make it more robust. The problem was that it restarts a single operator, which is not strictly supported behavior. Instead, a new operator should be created from the same config. The test involves moving a file and then validating that a log written to the original file location is read correctly. This enhances the test to also validate that additional logs written to the original (moved) file will be read as well.
Signed-off-by: Alex Boten <[email protected]>
**Description:** Fixes an issue with the grammar where named parameters had to have a space after the `=`. **Link to tracking Issue:** Closes #27638 **Testing:** Added a new unit test
Follows #28228 This normalizes calls to `Start` and `Stop` across the test suite. In some cases, `poll` is called directly in order to trigger behavior independently of timing. However, we should _either_ use `poll` directly, or use both `Start` and `Stop` exactly once. In the future, I expect `poll` will be exported and tested directly as part of an internal package.
Follows #28419 This discards the separate "roller" and implements the same functionality directly in `fileconsumer.Manager`. The motivation for this is to move towards a system of managing files where each file is managed by only one list at a time. This PR retains two overlapping slices of readers (`previousPollFiles` and `knownFiles`), but the functionality does not change. #27823 should get us the rest of the way there.
The following commands were run to prepare this release: - make chlog-update VERSION=v0.88.0 - sed -i.bak s/0.87.0/0.88.0/g versions.yaml - make multimod-prerelease - make multimod-sync
**Description:** Added documentation to describe how to use the AAD Auth Proxy to enable AAD based authentication. **Link to tracking Issue:** 24451 **Testing:** None - documentation change. **Documentation:** New AUTHENTICATION.md page describing how to configure the Exporter and the Auth Proxy to work together.
**Description:** Add a config option to periodically flush metrics, instead of flushing on every push. **Link to tracking Issue:** <Issue number if applicable> #27679 **Testing:** <Describe what testing was performed and which tests were added.> Added tests that verify metrics are flushed asynchronously **Documentation:** <Describe the documentation added.> Documentation added to `config.go` --------- Co-authored-by: Juraci Paixão Kröhling <[email protected]>
The docs for the `headers_setter` extension state that the `from_context` config option does not work if the batch processor is used. I believe this comment is out of date, because it seems that the [PR](open-telemetry/opentelemetry-collector#7578) linked to the [issue](open-telemetry/opentelemetry-collector#4544) has been merged. Note that I haven't tested that this actually works with the header setter extension. Please let me know if you think testing is necessary. Co-authored-by: Juraci Paixão Kröhling <[email protected]>
**Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Add new k8s.node.condition metric, so that we can deprecate k8s.node.condition_* metrics. **Link to tracking Issue:** <Issue number if applicable> #27617 **Testing:** <Describe what testing was performed and which tests were added.> - added unit tests **Documentation:** <Describe the documentation added.> - added docs
…onds instead of milliseconds (#27665) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Measures latency in seconds instead of milliseconds, as the metric name indicates. Previously, milliseconds was used. This unit is still available via the feature gate `processor.servicegraph.legacyLatencyUnitMs`. This is a breaking change. **Link to tracking Issue:** <Issue number if applicable> #27488 **Testing:** <Describe what testing was performed and which tests were added.> Tests are updated **Documentation:** <Describe the documentation added.> --------- Co-authored-by: Curtis Robert <[email protected]> Co-authored-by: Juraci Paixão Kröhling <[email protected]>
…parsed event log (#27864) **Description:** Adds parsing for Execution and Security sections of the event log, as defined in the schema here: https://learn.microsoft.com/en-us/windows/win32/wes/eventschema-systempropertiestype-complextype **Link to tracking Issue:** #27810 **Testing:** * Added some unit tests * Tested on a windows machine to make sure it parsed correctly on a real system --------- Co-authored-by: Paulo Janotti <[email protected]>
**Description:** Bumps image to latest released version to have the `debug` exporter available. **Link to tracking Issue:** Fixes #28553
… that the component's logger is available to contexts (#27660) **Description:** <Describe what has changed.> Passes `component.TelemetrySettings` to all path parsers so that they can pass the component's logger down to current/future contexts' getters/setters **Link to tracking Issue:** #22076 **Testing:** N/A, i'm assuming a successful compile and tests passing are sufficient **Documentation:** N/A Co-authored-by: Tyler Helmuth <[email protected]>
Merge release/v0.88.x branch into main
`fileconsumer.Manager.poll` leaves files open so that the next poll cycle can use them. In tests, the direct use of this function should be accompanied by explicit action to clean up the files.
Bump github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp from 1.19.1 to 1.20.0 in /exporter/datadogexporter Bump github.com/IBM/sarama from 1.41.2 to 1.41.3 in /exporter/kafkaexporter Bump github.com/IBM/sarama from 1.41.2 to 1.41.3 in /receiver/kafkareceiver Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.1 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.1 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.1 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.1 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.1 in /receiver/awsxrayreceiver Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.45.26 to 1.46.2 in /receiver/awsxrayreceiver Bump github.com/aws/aws-sdk-go-v2/service/kinesis from 1.19.2 to 1.20.0 in /exporter/awskinesisexporter Bump github.com/fsnotify/fsnotify from 1.6.0 to 1.7.0 in /exporter/prometheusremotewriteexporter Bump github.com/golangci/golangci-lint from 1.54.1 to 1.55.0 in /internal/tools Bump github.com/klauspost/compress from 1.17.1 to 1.17.2 in /exporter/fileexporter Bump github.com/klauspost/compress from 1.17.1 to 1.17.2 in /exporter/sapmexporter Bump github.com/prometheus/common from 0.44.0 to 0.45.0 in /exporter/prometheusexporter Bump github.com/prometheus/common from 0.44.0 to 0.45.0 in /testbed Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.767 to 1.0.772 in /exporter/tencentcloudlogserviceexporter Bump github.com/wavefronthq/wavefront-sdk-go from 0.14.0 to 0.15.0 in /exporter/tanzuobservabilityexporter Bump go.opentelemetry.io/collector/component from 0.87.1-0.20231023033326-37116a25be8d to 0.88.0 in /receiver/awsxrayreceiver Bump go.opentelemetry.io/collector/processor from 0.87.1-0.20231023033326-37116a25be8d to 0.88.0 in /processor/logstransformprocessor Bump google.golang.org/api from 0.147.0 to 0.148.0 in /exporter/f5cloudexporter Bump google.golang.org/api from 0.147.0 to 0.148.0 in /receiver/googlecloudpubsubreceiver Bump google.golang.org/api from 0.147.0 to 0.148.0 in /receiver/googlecloudspannerreceiver Bump google.golang.org/grpc from 1.58.3 to 1.59.0 in /examples/demo/client Bump k8s.io/api from 0.28.2 to 0.28.3 in /extension/observer/k8sobserver Bump k8s.io/api from 0.28.2 to 0.28.3 in /internal/aws/k8s Bump k8s.io/api from 0.28.2 to 0.28.3 in /internal/metadataproviders Bump k8s.io/api from 0.28.2 to 0.28.3 in /processor/k8sattributesprocessor Bump k8s.io/apimachinery from 0.28.2 to 0.28.3 in /exporter/datadogexporter Bump k8s.io/apimachinery from 0.28.2 to 0.28.3 in /extension/observer/k8sobserver Bump k8s.io/apimachinery from 0.28.2 to 0.28.3 in /internal/aws/k8s Bump k8s.io/apimachinery from 0.28.2 to 0.28.3 in /internal/k8sconfig Bump k8s.io/apimachinery from 0.28.2 to 0.28.3 in /internal/metadataproviders Bump k8s.io/apimachinery from 0.28.2 to 0.28.3 in /receiver/kubeletstatsreceiver Bump k8s.io/client-go from 0.28.2 to 0.28.3 in /extension/observer/k8sobserver Bump k8s.io/client-go from 0.28.2 to 0.28.3 in /internal/aws/k8s Bump k8s.io/client-go from 0.28.2 to 0.28.3 in /internal/k8sconfig Bump k8s.io/client-go from 0.28.2 to 0.28.3 in /internal/kubelet Bump k8s.io/client-go from 0.28.2 to 0.28.3 in /internal/metadataproviders Bump k8s.io/client-go from 0.28.2 to 0.28.3 in /processor/k8sattributesprocessor Bump sigs.k8s.io/controller-runtime from 0.16.2 to 0.16.3 in /exporter/loadbalancingexporter --------- Signed-off-by: Alex Boten <[email protected]> Co-authored-by: Alex Boten <[email protected]>
Bump github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp from 1.19.1 to 1.20.0 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /exporter/awscloudwatchlogsexporter Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /exporter/awsxrayexporter Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /exporter/datadogexporter Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /extension/observer/ecsobserver Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /internal/aws/awsutil Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /internal/aws/cwlogs Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /internal/aws/k8s Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /internal/aws/proxy Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /internal/aws/xray Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /internal/metadataproviders Bump github.com/aws/aws-sdk-go from 1.46.2 to 1.46.3 in /receiver/awsxrayreceiver Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.767 to 1.0.772 in /exporter/tencentcloudlogserviceexporter Bump go.opentelemetry.io/collector/component from 0.87.1-0.20231023033326-37116a25be8d to 0.88.0 in /receiver/awsxrayreceiver Bump k8s.io/apimachinery from 0.28.2 to 0.28.3 in /receiver/kubeletstatsreceiver
…e formats (#25096) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> Adding a Translator to convert from Azure Resource Log format (for now) to OTel. **Link to tracking Issue:** <Issue number if applicable> #18210 **Testing:** <Describe what testing was performed and which tests were added.> Performed manual validation testing between Event Hubs and OTel and added unit tests to cover new use case to allow multiple resources to be included in a batch. Existing tests moved to new package. **Documentation:** <Describe the documentation added.> None was necessary as this format is already supported by the Event Hub Receiver.
**Description:** Fix flakiness in the `TestGettingTrackingData/Timeout_waiting_for_response` test. The root cause of the issue is that the `client` and `server` are connected to same pipe and if the server attempts to read after the client is closed it reports error EOF and the test code expects no error from the read operation. The issue is not specific to Windows. The fix was to give control to each test case of the read and write functions so this type of synchronization issue can be properly handled while keeping the test code coverage. **Link to tracking Issue:** Fix #25188 **Testing:** Multiple local runs with various cpu settings. **Documentation:** N/A Co-authored-by: Alex Boten <[email protected]>
This PR enhances the internal `trie` struct (which is not yet in use anywhere in the codebase) such that a node may contain any value. The motivation for this is that I believe we may soon be able to migrate `knownFiles` and `previousPollFiles` to tries, which will prove out the functionality of the trie and also should improve efficiency of the package overall.
Although the persister is generally expected, we can easily protect against cases where it is not provided and save some work as well. This becomes more important with #27823 which interacts with the persister during the Stop function.
…er.org/multierr (#27908) **Description:** <Describe what has changed.> use errors.Join instead of go.uber.org/multierr **Link to tracking Issue:** <Issue number if applicable> #25121 **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.>
**Description:** Add a new traces config `trace_buffer` that specifies the number of Datadog Agent TracerPayloads to buffer before dropping. **Link to tracking Issue:** Fixes #28577 **Testing:** <Describe what testing was performed and which tests were added.> **Documentation:** <Describe the documentation added.>
](https://renovatebot.com){kind=link}
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.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )