Bump github.com/klauspost/compress from 1.11.1 to 1.14.2 in /exporter/honeycombexporter #1234
Conversation
This file contains hidden or 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
Bumps [github.com/klauspost/compress](https://github.com/klauspost/compress) from 1.11.1 to 1.14.2. - [Release notes](https://github.com/klauspost/compress/releases) - [Changelog](https://github.com/klauspost/compress/blob/master/.goreleaser.yml) - [Commits](klauspost/compress@v1.11.1...v1.14.2) --- updated-dependencies: - dependency-name: github.com/klauspost/compress dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
the
dependencies
Author
|
Superseded by #1295. |
dependabot
bot
deleted the
dependabot/go_modules/exporter/honeycombexporter/github.com/klauspost/compress-1.14.2
branch
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Removes `cmd/oteltestbedcol` from list since it has no Makefile <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#35606
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…atus (open-telemetry#35648) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Refactors the `extension/healthcheckv2extension/internal/status` into `pkg/status`. This exposes the aggregator to be used by other extensions to gather component status information using the `extension.StatusWatcher`. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Closes open-telemetry#34692 <!--Describe what testing was performed and which tests were added.--> #### Testing Being it was a refactor and all the same tests provided coverage, no additional testing was added. <!--Describe the documentation added.--> #### Documentation Added a `README.md` to the `pkg/status` to provide information on where this package can be used. --------- Co-authored-by: Matthew Wear <[email protected]>
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…elemetry#35771) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Update OTel mode to implementation to serialize log body into body.* fields <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…rning error to avoid upstream retries (open-telemetry#35740) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Log metrics validation error instead of returning to avoid upstream retries <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#35741 Fixes Wrong comparison func implement in translator/prometheusremotewrite. <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: Juraj Michalek <[email protected]>
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Follow up from open-telemetry#35703. Draft starting the work on adding support for remote write 2.0 in the translation package. Adding support for translating gauges. This is first iteration and to keep the PR small * we don't handle duplicate metrics * only support gauges * don't handle other labels than metric name * don't handle exemplars * don't handle metadata <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#33661 Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Juraj Michalek <[email protected]> Co-authored-by: Arthur Silva Sens <[email protected]> Co-authored-by: David Ashpole <[email protected]>
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…telemetry#35642) #### Description Follow [the contract](https://github.com/open-telemetry/opentelemetry-collector/blob/df3c9e38a80ccc3b14705462be2e2e51c628a3b3/receiver/doc.go#L10) for cloudflare receiver <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Related open-telemetry#5909 <!--Describe what testing was performed and which tests were added.--> #### Testing Added
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
#### Description Add a new receiver to handle systemd service state reporting as metrics. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#33532
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
… prefix conflict in OTel mapping mode (open-telemetry#35651) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Metric names should be flattened and exported as is, even when one metric name is a prefix of another. Same for attributes for all logs, metrics and traces. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…-telemetry#35776) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Version of MySQL older than 8.0.22 use the `show slave status` vs `show replica status` view to retrieve replication metrics. This allows for both the newer & older views to work and retrieve data for the two actual replica metrics available (`mysql.replica.time_behind_source` & `mysql.replica.sql_delay`). <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#35217 <!--Describe what testing was performed and which tests were added.--> #### Testing Manual testing against MySQL versions 8.0, 8.0.37, & MariaDB Ver 15.1 Distrib 10.5.26-MariaDB <!--Describe the documentation added.--> #### Documentation None needed <!--Please delete paragraphs that you did not use before submitting.-->
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
#### Description Adds initial implementation of ntpreceiver. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#34375
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…only (open-telemetry#35839) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Make OTel mapping mode use RequireDataStream in docappender, which means it will only send to data streams. This prevents auto creating regular indices in OTel mapping mode due to a race condition in Elasticsearch where otel-data index templates are not ready. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…emetry#35865) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Enable gzip compression by default, at hardcoded level BestSpeed. To disable compression, set `compression` to `none`. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…telemetry#35767) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Fixes an issue where the Kafka receiver would block on shutdown. There was an earlier fix for this issue [here](open-telemetry#32720). This does solve the issue, but it was only applied to the traces receiver, not the logs or metrics receiver. The issue is this go routine in the `Start()` functions for logs and metrics: ```go go func() { if err := c.consumeLoop(ctx, metricsConsumerGroup); err != nil { componentstatus.ReportStatus(host, componentstatus.NewFatalErrorEvent(err)) } }() ``` The `consumeLoop()` function returns a `context.Canceled` error when `Shutdown()` is called, which is expected. However `componentstatus.ReportStatus()` blocks while attempting to report this error. The reason/bug for this can be found [here](open-telemetry/opentelemetry-collector#9824). The previously mentioned PR fixed this for the traces receiver by checking if the error returned by `consumeLoop()` is `context.Canceled`: ```go go func() { if err := c.consumeLoop(ctx, consumerGroup); !errors.Is(err, context.Canceled) { componentstatus.ReportStatus(host, componentstatus.NewFatalErrorEvent(err)) } }() ``` Additionally, this is `consumeLoop()` for the traces receiver, with the logs and metrics versions being identical: ```go func (c *kafkaTracesConsumer) consumeLoop(ctx context.Context, handler sarama.ConsumerGroupHandler) error { for { // `Consume` should be called inside an infinite loop, when a // server-side rebalance happens, the consumer session will need to be // recreated to get the new claims if err := c.consumerGroup.Consume(ctx, c.topics, handler); err != nil { c.settings.Logger.Error("Error from consumer", zap.Error(err)) } // check if context was cancelled, signaling that the consumer should stop if ctx.Err() != nil { c.settings.Logger.Info("Consumer stopped", zap.Error(ctx.Err())) return ctx.Err() } } } ``` This does fix the issue, however the only error that can be returned by `consumeLoop()` is a canceled context. When we create the context and cancel function, we use `context.Background()`: ```go ctx, cancel := context.WithCancel(context.Background()) ``` This context is only used by `consumeLoop()` and the cancel function is only called in `Shutdown()`. Because `consumeLoop()` can only return a `context.Canceled` error, this PR removes this unused code for the logs, metrics, and traces receivers. Instead, `consumeLoop()` still logs the `context.Canceled` error but it does not return any error and the go routine simply just calls `consumeLoop()`. Additional motivation for removing the call to `componentstatus.ReportStatus()` is the underlying function called by it, `componentstatus.Report()` says it does not need to be called during `Shutdown()` or `Start()` as the service already does so for the given component, [comment here](https://github.com/open-telemetry/opentelemetry-collector/blob/main/component/componentstatus/status.go#L21-L25). Even if there wasn't a bug causing this call to block, the component still shouldn't call it since it would only be called during `Shutdown()`. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#30789 <!--Describe what testing was performed and which tests were added.--> #### Testing Tested in a build of the collector with these changes scraping logs from a Kafka instance. When the collector is stopped and `Shutdown()` gets called, the receiver did not block and the collector stopped gracefully as expected.
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…llback (open-telemetry#35769) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Out of the discussions at open-telemetry#35758 I realized that `ProcessWithCallback` does not handle the error returned by the callback function. Since the error of the parse function is handled I think we should handle this of the callback too. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: ChrsMark <[email protected]>
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adding full support for handling labels. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#33661 Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Juraj Michalek <[email protected]> Co-authored-by: Arthur Silva Sens <[email protected]> Co-authored-by: David Ashpole <[email protected]>
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR introduces a benchmark test for the receiver adapter which tests the performance of handling the log entries sent to the `LogEmitter`, which are then received and converted by the receiver adapter. The changes have been made based on the comment linked here: open-telemetry#35669 (comment) <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Part of open-telemetry#35453 <!--Describe what testing was performed and which tests were added.--> #### Testing Added additional benchmark tests --------- Signed-off-by: Florian Bacher <[email protected]>
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…-telemetry#35750) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR is to add `otlp_v1` into the list of valid `record_type` input. Otherwise when `record_type` sets to `otlp_v1`, we get error: ``` 2024-10-23T16:53:09.823Z info [email protected]/service.go:135 Setting up own telemetry... 2024-10-23T16:53:09.824Z info telemetry/metrics.go:70 Serving metrics {"address": "localhost:8888", "metrics level": "Normal"} Error: failed to build pipelines: failed to create "awsfirehose" receiver for data type "metrics": unrecognized record type ``` <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> --------- Co-authored-by: Matthew Wear <[email protected]>
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
open-telemetry#35834) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Fixed issue in which Operators with DropOnErrorQuiet are not dropping log entries on error. Note: This issue was introduced by a bug fix meant to ensure Silent Operators are not logging errors (open-telemetry#35010). With this fix, this side effect bug has been resolved. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes 35010 <!--Describe what testing was performed and which tests were added.--> #### Testing Added UT
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Add new uptime scraper to emit the `system.uptime` metric <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#31627 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit test added. Also tested locally (Linux VM) with following config: ```yaml receivers: hostmetrics: scrapers: uptime: exporters: debug: verbosity: detailed service: pipelines: metrics: receivers: - hostmetrics exporters: - debug ``` <details><summary>Details</summary> <p> ```console $ make genotelcontribcol [...] $ make RUN_CONFIG=config-uptime.yaml run 2024-10-23T13:24:48.195+0200 info [email protected]/service.go:135 Setting up own telemetry... 2024-10-23T13:24:48.195+0200 info telemetry/metrics.go:70 Serving metrics {"address": "localhost:8888", "metrics level": "Normal"} 2024-10-23T13:24:48.195+0200 info builders/builders.go:26 Development component. May change in the future. {"kind": "exporter", "data_type": "metrics", "name": "debug"} 2024-10-23T13:24:48.199+0200 info [email protected]/service.go:207 Starting otelcontribcol... {"Version": "0.112.0-dev", "NumCPU": 7} 2024-10-23T13:24:48.199+0200 info extensions/extensions.go:39 Starting extensions... 2024-10-23T13:24:48.199+0200 info [email protected]/service.go:230 Everything is ready. Begin running and processing data. 2024-10-23T13:24:49.202+0200 info Metrics {"kind": "exporter", "data_type": "metrics", "name": "debug", "resource metrics": 1, "metrics": 1, "data points": 1} 2024-10-23T13:24:49.202+0200 info ResourceMetrics #0 Resource SchemaURL: https://opentelemetry.io/schemas/1.9.0 ScopeMetrics #0 ScopeMetrics SchemaURL: InstrumentationScope github.com/open-telemetry/opentelemetry-collector-contrib/receiver/hostmetricsreceiver/internal/scraper/uptimescraper 0.112.0-dev Metric #0 Descriptor: -> Name: system.uptime -> Description: The time the system has been running -> Unit: s -> DataType: Sum -> IsMonotonic: false -> AggregationTemporality: Cumulative NumberDataPoints #0 StartTimestamp: 2024-10-22 18:23:22 +0000 UTC Timestamp: 2024-10-23 11:24:49.202512199 +0000 UTC Value: 61287.000000 {"kind": "exporter", "data_type": "metrics", "name": "debug"} 2024-10-23T13:25:49.206+0200 info Metrics {"kind": "exporter", "data_type": "metrics", "name": "debug", "resource metrics": 1, "metrics": 1, "data points": 1} 2024-10-23T13:25:49.206+0200 info ResourceMetrics #0 Resource SchemaURL: https://opentelemetry.io/schemas/1.9.0 ScopeMetrics #0 ScopeMetrics SchemaURL: InstrumentationScope github.com/open-telemetry/opentelemetry-collector-contrib/receiver/hostmetricsreceiver/internal/scraper/uptimescraper 0.112.0-dev Metric #0 Descriptor: -> Name: system.uptime -> Description: The time the system has been running -> Unit: s -> DataType: Sum -> IsMonotonic: false -> AggregationTemporality: Cumulative NumberDataPoints #0 StartTimestamp: 2024-10-22 18:23:22 +0000 UTC Timestamp: 2024-10-23 11:25:49.206657828 +0000 UTC Value: 61347.000000 {"kind": "exporter", "data_type": "metrics", "name": "debug"} 2024-10-23T13:26:49.205+0200 info Metrics {"kind": "exporter", "data_type": "metrics", "name": "debug", "resource metrics": 1, "metrics": 1, "data points": 1} 2024-10-23T13:26:49.205+0200 info ResourceMetrics #0 Resource SchemaURL: https://opentelemetry.io/schemas/1.9.0 ScopeMetrics #0 ScopeMetrics SchemaURL: InstrumentationScope github.com/open-telemetry/opentelemetry-collector-contrib/receiver/hostmetricsreceiver/internal/scraper/uptimescraper 0.112.0-dev Metric #0 Descriptor: -> Name: system.uptime -> Description: The time the system has been running -> Unit: s -> DataType: Sum -> IsMonotonic: false -> AggregationTemporality: Cumulative NumberDataPoints #0 StartTimestamp: 2024-10-22 18:23:22 +0000 UTC Timestamp: 2024-10-23 11:26:49.2051249 +0000 UTC Value: 61407.000000 {"kind": "exporter", "data_type": "metrics", "name": "debug"} 2024-10-23T13:27:49.210+0200 info Metrics {"kind": "exporter", "data_type": "metrics", "name": "debug", "resource metrics": 1, "metrics": 1, "data points": 1} 2024-10-23T13:27:49.210+0200 info ResourceMetrics #0 Resource SchemaURL: https://opentelemetry.io/schemas/1.9.0 ScopeMetrics #0 ScopeMetrics SchemaURL: InstrumentationScope github.com/open-telemetry/opentelemetry-collector-contrib/receiver/hostmetricsreceiver/internal/scraper/uptimescraper 0.112.0-dev Metric #0 Descriptor: -> Name: system.uptime -> Description: The time the system has been running -> Unit: s -> DataType: Sum -> IsMonotonic: false -> AggregationTemporality: Cumulative NumberDataPoints #0 StartTimestamp: 2024-10-22 18:23:22 +0000 UTC Timestamp: 2024-10-23 11:27:49.21007371 +0000 UTC Value: 61467.000000 {"kind": "exporter", "data_type": "metrics", "name": "debug"} ^C 2024-10-23T13:27:54.204+0200 info [email protected]/collector.go:328 Received signal from OS {"signal": "interrupt"} 2024-10-23T13:27:54.204+0200 info [email protected]/service.go:266 Starting shutdown... 2024-10-23T13:27:54.204+0200 info extensions/extensions.go:66 Stopping extensions... 2024-10-23T13:27:54.204+0200 info [email protected]/service.go:280 Shutdown complete. ``` </p> </details> <!--Describe the documentation added.--> #### Documentation Updated readme & generated scraper docs <!--Please delete paragraphs that you did not use before submitting.-->
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…SON status: ok (open-telemetry#36029) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Changing the `/api/v1/check_run` response for service checks to be on par with the datadog api spec as per https://docs.datadoghq.com/api/latest/service-checks/ This is the same implementation as the PR for the series endpoints open-telemetry#35744 <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#36027 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests updated and are passing <!--Describe the documentation added.--> #### Documentation Changelog updated
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…#35985) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description - This PR changes stability to `alpha` - Updates README.md for more clarity and detailed config <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue [open-telemetry#32669] <!--Describe what testing was performed and which tests were added.--> #### Testing No additional testing needed <!--Describe the documentation added.--> #### Documentation Adds clarification of config, additional detail to detailed config, and notes about when and how to use which telemetry type. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: jeremyh <[email protected]>
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…ce detector (open-telemetry#35737) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR fixes the issue described at open-telemetry#34210. Each detector's docs should list the resource attributes as they are defined by the `metadata.yml` files. This PR links each detector to its `documentation.md` as a reference for the respective Resource Atrributes. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#34210 <!--Describe what testing was performed and which tests were added.--> #### Testing ~ <!--Describe the documentation added.--> #### Documentation Added <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: ChrsMark <[email protected]>
mackjmr
pushed a commit
that referenced
this pull request
Nov 19, 2024
…e system is mounted (open-telemetry#36000) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Do not set the default value of HOST_PROC_MOUNTINFO to respect root_path <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#35990
jackgopack4
pushed a commit
that referenced
this pull request
Nov 19, 2025
…emetry#44388) <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#44280
jackgopack4
pushed a commit
that referenced
this pull request
Nov 19, 2025
…tic Cloud IDs when sent with multiple dollar sign separators (open-telemetry#44325) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description The CloudID decoder was incorrectly using `strings.Cut()`, which only splits at the first delimiter, resulting in malformed URLs when the decoded CloudID contained multiple `$` separators. Changed to use `strings.Split()` to match the reference implementation from the [go-elasticsearch](https://github.com/elastic/go-elasticsearch/blob/4739f334675880df102135bcca6104c8c63b59db/elasticsearch.go#L474) library. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#44306 <!--Describe what testing was performed and which tests were added.--> #### Testing Added tests to validate this behaviour and the expected output. Signed-off-by: Paulo Dias <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…pen-telemetry#44340) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR promotes the feature gate `receiver.azureeventhubreceiver.UseAzeventhubs` to Beta as no issues seem been reported for the time this feature was in Alpha stage. This is also a preparation for future removal usage of the Go module [github.com/Azure/go-autorest](https://github.com/Azure/go-autorest) since it has been deprecated. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Relates to open-telemetry#44335 <!--Describe the documentation added.--> #### Documentation Updated documentation accordingly <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Paulo Dias <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…de attribute (open-telemetry#43000) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds a feature gate to use [the latest semantic conventions](https://opentelemetry.io/docs/specs/semconv/registry/attributes/otel/#otel-status-code) for the status code attribute on generated metrics. Changes: | Old Attribute | New Attribute | | --- | --- | | `status.code=STATUS_CODE_ERROR` | `otel.status_code=ERROR` | | `status.code=STATUS_CODE_OK` | `otel.status_code=OK` | | `status.code=STATUS_CODE_UNSET` | *(no attribute)* | <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Partially Fixes open-telemetry#42103 <!--Describe what testing was performed and which tests were added.--> #### Testing Added new test case `"Test using new status code attribute"` <!--Describe the documentation added.--> #### Documentation README updated, changelog entry added <!--Please delete paragraphs that you did not use before submitting.-->
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…y#44243) #### Description Add benchmarks for several common scenarios of Prometheus Receiver <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#44195 <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Arthur Silva Sens <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…les (open-telemetry#44267) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR is to regenerate the `*_expected.yaml` testing files using `golden.WriteLogs(t, expectedFile, logs)` in `resourcelogs_to_logs_test.go`. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue There is no issue for this. I'm putting it in a separate PR so it can be more clear open-telemetry#44266 does not break the other existing log categories.
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR changes the tailsampling processor to do all work (append traces to a batch, decide on which traces from a batch are sampled, forward to the next processor) in a single goroutine. At Grafana Labs we have found that there is significant contention between the various mutexes such that little performance is gained by allowing traces to be updated while a policy evaluation is occurring. In addition, the locking adds a lot of complexity which makes future improvements more challenging, and introduces subtle concurrency issues such as seen in the tracking issue linked below. We (mostly @Logiraptor) also experimented with using multiple workers, each with their own goroutine to process traces but we found little improvement as yet again various contention issues showed up. See Logiraptor#1 (or the first commit in this PR) for more details. If additional performance is necessary for slow decision tick latencies I would suggest adding parallelism just to the call to `makeDecision`, which would allow additional CPUs to be used without adding contention on `idToTrace` or other locations. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#41656 Working towards open-telemetry#43876 <!--Describe what testing was performed and which tests were added.--> #### Testing Tests were updated to make sure the tick behavior remains correct and consistent. In addition, the syncBatcher needed to be updated to properly implement `Stop`. --------- Co-authored-by: Patrick Oyarzun <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…pen-telemetry#44393) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Fixed OTTL grammar to treat the string literal `"nil"` as ordinary text instead of a `nil` value. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#44374 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests <!--Describe the documentation added.--> #### Documentation No changes <!--Please delete paragraphs that you did not use before submitting.--> Co-authored-by: Yang Song <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…pen-telemetry#42401) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Add support for exposing Redis sentinel and mode metrics. Redis Sentinel metrics with Redis mode: ```sh # HELP redis_mode Redis server mode # TYPE redis_mode gauge redis_mode{mode="sentinel",otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} 1 # HELP redis_sentinel_masters Number of masters monitored by Sentinel. # TYPE redis_sentinel_masters gauge redis_sentinel_masters{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} 1 # HELP redis_sentinel_running_scripts Number of running Sentinel scripts. # TYPE redis_sentinel_running_scripts gauge redis_sentinel_running_scripts{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} 0 # HELP redis_sentinel_scripts_queue_length Length of Sentinel scripts queue. # TYPE redis_sentinel_scripts_queue_length gauge redis_sentinel_scripts_queue_length{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} 0 # HELP redis_sentinel_simulate_failure_flags Simulated failure flags bitmask. # TYPE redis_sentinel_simulate_failure_flags gauge redis_sentinel_simulate_failure_flags{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} 0 # HELP redis_sentinel_tilt Whether Sentinel is in TILT mode (1 = tilt, 0 = normal). # TYPE redis_sentinel_tilt gauge redis_sentinel_tilt{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} 0 # HELP redis_sentinel_tilt_since_seconds Duration in seconds of current TILT, or -1 if not in TILT mode. # TYPE redis_sentinel_tilt_since_seconds gauge redis_sentinel_tilt_since_seconds{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} -1 # HELP redis_sentinel_tilt_total Total TILT occurrences since start. # TYPE redis_sentinel_tilt_total counter redis_sentinel_tilt_total{otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} 0 ``` Redis mode (standalone): ```sh # HELP redis_mode Redis server mode # TYPE redis_mode gauge redis_mode{mode="standalone",otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} 1 ``` Redis mode (cluster): ```sh # HELP redis_mode Redis server mode # TYPE redis_mode gauge redis_mode{mode="cluster",otel_scope_name="github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver",otel_scope_schema_url="",otel_scope_version="0.134.0-dev"} 1 ``` <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42365 <!--Describe what testing was performed and which tests were added.--> #### Testing I tested this against all the possible modes (sentinel, standalone, and cluster). The sentinel metrics are only evaluated and exposed when `redis_mode:sentinel`. I also added integration tests `TestIntegrationV8Sentinel` for the `sentinel` mode. <!--Describe the documentation added.--> #### Documentation Updated the documentation using `mdatagen` <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Paulo Dias <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…etry#44100) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds the factory and configuration implementation for the macOS Unified Logging receiver. This PR follows the steps outlined in `CONTRIBUTING.md` to split up the PRs for a new component. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#44089 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests for the configuration and factory. <!--Describe the documentation added.--> #### Documentation The receiver is completely documented in `README.md`. <!--Please delete paragraphs that you did not use before submitting.-->
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…asticsearch fields (open-telemetry#44234) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Add missing fields to struct so that they are populated in the respective elasticsearch index. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Florian Lehner <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…etry#43836) <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#36463 Signed-off-by: Israel Blancas <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
…emetry#44297) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Fixes the OpAMP Supervisor configuration example of how to use `agent::args` for feature gates. Also updates the example to use the currently [only supported](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/64d44adae2ee4788237ba3743f7603b415ee69e0/cmd/opampsupervisor/supervisor/supervisor.go#L417-L419) feature gate `service.AllowNoPipelines`. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#44296 <!--Describe the documentation added.--> #### Documentation OpAMP Supervisor Configuration <!--Please delete paragraphs that you did not use before submitting.--> Co-authored-by: Alex Boten <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Follow up of open-telemetry#43898 This is the implementation of the new awslambdareceiver. For better PR readability, the new components functionality will be split in different PRs. Current PR adds support for receiving logs and metrics from S3 <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43504 <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Andrew Wilkins <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
<!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#44410
jackgopack4
pushed a commit
that referenced
this pull request
Nov 20, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This adds systemreceiver to builder config <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#44420 <!--Describe what testing was performed and which tests were added.--> #### Testing Start otel collector with following config ``` receivers: systemd: scope: system units: - sshd.service processors: batch: {} exporters: debug: verbosity: detailed extensions: health_check: service: pipelines: metrics: receivers: [systemd] processors: [batch] exporters: [debug] ```
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…emetry#44436) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR refactors the `pkg/translator/azurelogs/testdata` directory to improve organization and consistency, and corrects a category name to match actual Azure log data. Changes: - Combined all appservice*logs directories into a single appservicelog directory. - Combined corner case directories (badlevel, badtime, maximum, minimum, minimum2) into a single `cornercases` directory. - Renamed azurecdnaccesslog to cdnaccesslog. - Standardized filenames by removing `log-` prefix from JSON files and use `_expected.yaml` suffix instead of `-expected.yaml`. - Use `-log` instead of `-logs` <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue N/A <!--Describe what testing was performed and which tests were added.--> #### Testing Changed the existing `resourcelogs_to_logs_test.go`.
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> Promotes Christos Markou to opentelemetry-collector-contrib maintainer. Congratulations!!
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…telemetry#43871) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Upgrade cassandra library version <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> #### PR open-telemetry#43691 --------- Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: Paulo Dias <[email protected]> Signed-off-by: alex boten <[email protected]> Co-authored-by: Khushi Jain <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Yang Song <[email protected]> Co-authored-by: Paulo Dias <[email protected]> Co-authored-by: Alex Boten <[email protected]> Co-authored-by: Kaiyan White <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR adds the `ParseSeverity` function, as discussed in the linked ticket. I also had to make a minor change to the internal `mapGetter`, handling the map literals to return a raw `map[string]any`, instead of a `pcommon.Map`. This is because if there is a map literal within a slice, the `pcommon.Slice.FromRaw` cannot handle the `pcommon.Map`, as it only works with raw data types. This change is however transparent, and the behavior to the outside of this package does not change. EDIT: After merging main with the support for value expressions, introduced in open-telemetry#36883, this would affect the type of values returned by `ParseValueExpression` - previously this could potentially return `map[string]any`/`[]any`, but with the changes introduced in this PR, this would return a `pcommon.Map`/`pcommon.Slice`. Please let me know if I should do this change in a separate PR though. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#35079 <!--Describe what testing was performed and which tests were added.--> #### Testing Added unit and e2e tests <!--Describe the documentation added.--> #### Documentation Describe new function in the readme <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Florian Bacher <[email protected]> Co-authored-by: Tyler Helmuth <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…nector (open-telemetry#42052) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description First version of metricsaslogs connector. this connector connect metric pipeline to log pipeline what it do is create LogRecord per DataPoint attributes are mapped to Metric Resource -> Log Resource Metric Scope -> Log Scope datapoint -> logrecord <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#40938 <!--Describe what testing was performed and which tests were added.--> #### Testing unit test with over 90% coverage <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Antoine Toulme <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds additional mapping in Azure Monitor Exporter to the following Application Insights properties: | Application Insights property | OpenTelemetry attribute | ----------------------------- | ----------------------------------------------------- | application_Version | service.version | client_OS | os.name concatenated with os.version | client_Model | device.manufacturer | client_Type | device.model.identifier <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#40598 --------- Co-authored-by: Dmitry Anoshin <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…stead of VM Name for setting `host.name` in Azure (open-telemetry#43969) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR fixes the value being set for the `host.name` resource attribute in Azure environments using Virtual Machine Scale Sets (VMSS). Previously, the `compute.name` field was being used for both `host.name` and `azure.vm.name`. While this value is equal for traditional Azure VMs, for VMSS, it seems more accurate to use the value of `compute.osProfile.computerName`. To address this, the processor now retrieves the `host.name` value from the Instance Metadata Service (IMDS) field `compute.osProfile.computerName`. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43959 <!--Describe what testing was performed and which tests were added.--> #### Testing Updated tests accordingly. --------- Signed-off-by: Paulo Dias <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…o avoid buffer limits (open-telemetry#44310) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description When passthrough logging is enabled, the supervisor reads in collector output and then writes it to its own logger instead of a dedicated log file. An error can occur when a single collector log is too big (>64kb) and cause the scanner to fail. Instead we'll use a reader splitting logs based on newlines to avoid issues with logs being too large. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#44127 <!--Describe what testing was performed and which tests were added.--> #### Testing Hard to trigger with a unit test. Can verify using the hostmetrics receiver. I was able to trigger the bug when the hostmetrics receiver tried reading process metrics on my machine. This single log was greater than 64kb. On the previous version I saw the error `bufio.Scanner: token too long` but on this branch it prints the log no issue. <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…emetry#43402) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Add more types to severity map. k8s event api suggest more types can be added https://github.com/kubernetes/api/blob/release-1.34/events/v1/types_swagger_doc_generated.go#L42 To support additional types, set the event type as is and if it is a known type set the SeverityNumber other wise set SeverityNumberUnspecified <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43401 <!--Describe what testing was performed and which tests were added.--> #### Testing ``` ubuntu@W117ZS8FS3:/mnt/c/Users/gaddas3/workspace/opentelemetry-collector-contrib/receiver/k8seventsreceiver$ go test PASS ok github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8seventsreceiver 0.223s ``` <!--Describe the documentation added.--> #### Documentation Created change log with the following subtext: k8seventsreceiver allows event types Error and Critical in addition to current Normal and Warning event types. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Christos Markou <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…-telemetry#43927) <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43919 Signed-off-by: Israel Blancas <[email protected]> Co-authored-by: Christos Markou <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…-telemetry#44397) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Complementary change to open-telemetry/opentelemetry-collector#14188. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Florian Lehner <[email protected]> Co-authored-by: Vihas Makwana <[email protected]> Co-authored-by: Pablo Baeyens <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…n-telemetry#44118) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Add a new `exclude_topic` option to allow users to exclude topics when using the Kafka receiver with a regex on the topic consuming definition. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43782 <!--Describe what testing was performed and which tests were added.--> #### Testing Added tests to validate this functionality and the configuration itself. <!--Describe the documentation added.--> #### Documentation Updated documentation with the option and with an explicit example. <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Paulo Dias <[email protected]> Co-authored-by: Andrew Wilkins <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…try#44380) #### Description This PR adds parsing support for Google Cloud Proxy Network Load Balancer (TCP/SSL proxy) connection logs from the loadbalancing.googleapis.com/connections log stream. Test data for this was generated with https://github.com/elastic/infra-party , a tool I've made to create real GCP resources and easily export their logs. Features: - Parses connection details (client/server IPs and ports) - Translates IANA protocol numbers to human-readable names (tcp, udp, etc.) - Captures connection timing (start_time, end_time) - Tracks bytes transferred (server.bytes_received, server.bytes_sent) - Automatically surfaces all resource metadata fields via gcp.label.* pattern (backend_name, network_name, load_balancing_scheme, region, etc.) Implementation details: - Format identifier: gcp.proxy-nlb - Attribute namespace: gcp.load_balancing.proxy_nlb.* - Reuses existing vpcflowlog.ProtocolName() for IANA protocol translation The parser handles logs from the `l4_proxy_rule` resource type and preserves Google's field naming (e.g., serverBytesReceived/Sent) while mapping to appropriate OpenTelemetry attributes. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#44099 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests and golden tests added per conventions in this repo <!--Describe the documentation added.--> #### Documentation See the README changes, for more info on these log types see https://cloud.google.com/load-balancing/docs/tcp/tcp-ssl-proxy-logging-monitoring <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Christos Markou <[email protected]>
jackgopack4
pushed a commit
that referenced
this pull request
Nov 25, 2025
…resources into separate package (open-telemetry#43108) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR refactors the `k8sobjects` receiver by extracting the components responsible for receiving the K8s resources in the cluster into a separate package with an `Observer` interface, and the pull/watch based implementations thereof. This package can then also be used by the `k8sevents` receiver, which would then only need to format the received events to conform with the semantic conventions. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Part of open-telemetry#40825 - next steps as part of this issue would be to also make use of the observer components in the k8seventsreceiver <!--Describe what testing was performed and which tests were added.--> #### Testing Added tests for the new components. The tests for the receiver itself could be refactored to not use the concrete implementations of the Observer interface, but that should probably be done as a follow up to not make this PR too large --------- Signed-off-by: Florian Bacher <[email protected]>
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.
Bumps github.com/klauspost/compress from 1.11.1 to 1.14.2.
Release notes
Sourced from github.com/klauspost/compress's releases.
... (truncated)
Commits
7f260bezstd: improve header decoder (#476)1d64431zstd: Add noasm tag for xxhash (#475)505dc06flate: Increase level 7+8 speed and compression (#473)626787fflate: Improve level 7-9 (again) (#471)d7fe949fix logically dead code (#472)f877063zstd: Remove unused decompression buffer (#470)22de983zstd: Add bigger default blocks (#469)8eae845Update README.mdc2909d1Update README.md8f61aabUpdate README.mdDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)