-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[exporter/datasetexporter] Upgrade to dataset-go v0.19.0 #33675
[exporter/datasetexporter] Upgrade to dataset-go v0.19.0 #33675
Conversation
There is failing check - https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/9598696641/job/26470817018?pr=33675#step:13:1
However, when I run that command:
And based on the
Or
|
Co-authored-by: Curtis Robert <[email protected]>
component: datasetexporter | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Upgrade dataset-go to v0.19.0 and fix found issues |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
May want to briefly clarity what those "found issues" were under subtext
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small comment on expanding the changelog entry, besides that, LGTM.
Thanks.
I have added those details. My expectation was, that changelog is meant for users - and they do not care whether integration tests are now running when in the past they have been skipped. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This file appears to be no longer used. Since it's in an `internal` directory it's not exposed publicly, so I don't believe it needs a changelog. For context, I believe its original use was to be consumed by `cmd/configschema`, which has since been [deleted](open-telemetry#33384). I believe we simply missed this file in the removal process.
…elemetry#33691) The produced metrics are unnecessarily grouped by empty resources. This change removes the excessive grouping to keep only unique resources
This PR attempts to make schemaURL for TransformContexts. **Description:** <Describe what has changed.> Added a breaking change to creation of TransformContext function for logs. Also made changes to all references of the function. **Link to tracking Issue:** <Issue number if applicable> open-telemetry#30229 --------- Co-authored-by: Evan Bradley <[email protected]> Co-authored-by: Tyler Helmuth <[email protected]>
This has been broken for some time as the definition of GOTEST was removed Signed-off-by: Alex Boten <[email protected]>
…pen-telemetry#33710) A recent issued brought up that the `username` config option is available, but not documented in the README. The `password` option is described in the README, but doesn't include information relevant for Redis >= 6.0. This adds information on both config options. Fixes open-telemetry#33707
…nents (open-telemetry#33695) Adding myself as a codeowner for Windows performance counter and related components per respective call for more volunteers on the respective README files. I have experience with Windows and was a maintainer of the collector some years ago. Per DM I am also removing @djaglowski from `receiver\windowseventlog`, ActiveDirectoryDS, and IIS. cc @alxbl
…etry#33628) **Description:** Labels the `otelarrowexporter` and `otelarrowreceiver` as alpha, adds them to the contribcol. **Link to tracking Issue:** open-telemetry#26491
This updates the code that was using OpenCensus to use mdatagen + otel Fixes open-telemetry#33468 --------- Signed-off-by: Alex Boten <[email protected]>
The expected and actual errors are misplaced. It makes the test output confusing
**Description:** Optimize statsdreceiver code to reduce heap usage Also reduce failCnt increment to reduce memory footprint in cases of tons of malformed statsd messages **Link to tracking Issue:** <Issue number if applicable> **Testing:** - Tested internally and saw a 17% reduction in object allocation from our workloads (with ~2.5k/s statsd metrics input) mostly from reduction of strings.Split Screenshot is from `go tool pprof -http:8081 -diff_base baseline.heap.gz optimized.heap.gz` ![Screenshot 2024-06-20 at 12 45 17 PM](https://github.com/open-telemetry/opentelemetry-collector-contrib/assets/142453/e8065097-2533-4934-9b78-c0e828e075ac) Note: I also saw lots of allocations from attribute.NewSet but idk the best way to go about reducing that. (Screenshot below is from unoptimized statsdreceiver) ![Screenshot 2024-06-20 at 12 44 32 PM](https://github.com/open-telemetry/opentelemetry-collector-contrib/assets/142453/293553c0-92c8-465b-872a-ddb7b68299a0) I tried changing statsDMetricDescription's attrs field to `map[string]any` in the hopes of using attributes.FromRaw in buildGaugeMetric but it would require replacing statsDMetricDescription as the type of the map key in instruments.gauges, etc.
Description: This PR is upgrading dataset-go to version v0.19.0 - https://github.com/scalyr/dataset-go/releases/tag/v0.19.0
This PR is also fixing:
Link to tracking Issue: #33498, #32533, #33675
Testing: Unit tests and integration tests.
Documentation:
fixes #32533