Bump github.com/klauspost/compress from 1.11.1 to 1.14.2 in /exporter/honeycombexporter #1234

dependabot · 2022-01-31T16:03:03Z

Bumps github.com/klauspost/compress from 1.11.1 to 1.14.2.

Release notes

Sourced from github.com/klauspost/compress's releases.

v1.14.2

What's Changed

zstd: Add bigger default blocks by @klauspost in klauspost/compress#469

zstd: Remove unused decompression buffer by @klauspost in klauspost/compress#470

fix logically dead code by @ningmingxiao in klauspost/compress#472

flate: Improve level 7-9 (again) by @klauspost in klauspost/compress#471

flate: Increase level 7+8 speed and compression by @klauspost in klauspost/compress#473

zstd: Add noasm tag for xxhash by @klauspost in klauspost/compress#475

zstd: improve header decoder by @dsnet in klauspost/compress#476

New Contributors

@ningmingxiao made their first contribution in klauspost/compress#472

Full Changelog: klauspost/compress@v1.14.1...v1.14.2

v1.14.1

What's Changed

s2: Add stream index in klauspost/compress#462

flate: Speed and efficiency improvements in klauspost/compress#439 klauspost/compress#461 klauspost/compress#455 klauspost/compress#452 klauspost/compress#458

zstd: Performance improvement in klauspost/compress#420 klauspost/compress#456 klauspost/compress#437 klauspost/compress#467 klauspost/compress#468

zstd: add arm64 xxhash assembly by @lizthegrey in klauspost/compress#464

Add garbled for binaries for s2 in klauspost/compress#445

New Contributors

@lizthegrey made their first contribution in klauspost/compress#464

Full Changelog: klauspost/compress@v1.13.6...v1.14.1

v1.14.0

What's Changed

s2: Add stream index in klauspost/compress#462

flate: Speed and efficiency improvements in klauspost/compress#439 klauspost/compress#461 klauspost/compress#455 klauspost/compress#452 klauspost/compress#458

zstd: Performance improvement in klauspost/compress#420 klauspost/compress#456 klauspost/compress#437 klauspost/compress#467 klauspost/compress#468

zstd: add arm64 xxhash assembly by @lizthegrey in klauspost/compress#464

Add garbled for binaries for s2 in klauspost/compress#445

New Contributors

@lizthegrey made their first contribution in klauspost/compress#464

Full Changelog: klauspost/compress@v1.13.6...v1.14.0

v1.13.6

Changelog

c608412 Add performance baseline (#434) dac4d4c Bump to build 00a2d6d Remove 4 length match check. (#433)

... (truncated)

Commits

7f260be zstd: improve header decoder (#476)
1d64431 zstd: Add noasm tag for xxhash (#475)
505dc06 flate: Increase level 7+8 speed and compression (#473)
626787f flate: Improve level 7-9 (again) (#471)
d7fe949 fix logically dead code (#472)
f877063 zstd: Remove unused decompression buffer (#470)
22de983 zstd: Add bigger default blocks (#469)
8eae845 Update README.md
c2909d1 Update README.md
8f61aab Update README.md
Additional commits viewable in compare view

Dependabot 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 rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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 · 2022-02-21T16:02:57Z

Superseded by #1295.

)  #### Description Removes `cmd/oteltestbedcol` from list since it has no Makefile  #### Link to tracking issue Fixes open-telemetry#35606

…atus (open-telemetry#35648)  #### 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`.  #### Link to tracking issue Closes open-telemetry#34692  #### Testing Being it was a refactor and all the same tests provided coverage, no additional testing was 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]>

…elemetry#35771)  #### Description Update OTel mode to implementation to serialize log body into body.* fields  #### Link to tracking issue  #### Testing  #### Documentation

…rning error to avoid upstream retries (open-telemetry#35740)  #### Description Log metrics validation error instead of returning to avoid upstream retries  #### Link to tracking issue  #### Testing  #### Documentation

)  #### Description  #### Link to tracking issue open-telemetry#35741 Fixes Wrong comparison func implement in translator/prometheusremotewrite.  #### Testing  #### Documentation  Signed-off-by: Juraj Michalek <[email protected]>

#### 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  #### Link to tracking issue open-telemetry#33661 Fixes  #### Testing  #### Documentation  --------- Signed-off-by: Juraj Michalek <[email protected]> Co-authored-by: Arthur Silva Sens <[email protected]> Co-authored-by: David Ashpole <[email protected]>

…telemetry#35642) #### Description Follow [the contract](https://github.com/open-telemetry/opentelemetry-collector/blob/df3c9e38a80ccc3b14705462be2e2e51c628a3b3/receiver/doc.go#L10) for cloudflare receiver  #### Link to tracking issue Related open-telemetry#5909  #### Testing Added

#### Description Add a new receiver to handle systemd service state reporting as metrics.  #### Link to tracking issue open-telemetry#33532

… prefix conflict in OTel mapping mode (open-telemetry#35651)  #### 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.  #### Link to tracking issue  #### Testing  #### Documentation

…-telemetry#35776)  #### 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`).  #### Link to tracking issue Fixes open-telemetry#35217  #### Testing Manual testing against MySQL versions 8.0, 8.0.37, & MariaDB Ver 15.1 Distrib 10.5.26-MariaDB  #### Documentation None needed

#### Description Adds initial implementation of ntpreceiver.  #### Link to tracking issue open-telemetry#34375

…only (open-telemetry#35839)  #### 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.  #### Link to tracking issue  #### Testing  #### Documentation

…emetry#35865)  #### Description Enable gzip compression by default, at hardcoded level BestSpeed. To disable compression, set `compression` to `none`.  #### Link to tracking issue  #### Testing  #### Documentation

…telemetry#35767)  #### 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()`.  #### Link to tracking issue Fixes open-telemetry#30789  #### 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.

…llback (open-telemetry#35769)  #### 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.  #### Link to tracking issue Fixes  #### Testing  #### Documentation  --------- Signed-off-by: ChrsMark <[email protected]>

#### Description Adding full support for handling labels.  #### Link to tracking issue open-telemetry#33661 Fixes  #### Testing  #### Documentation  --------- Signed-off-by: Juraj Michalek <[email protected]> Co-authored-by: Arthur Silva Sens <[email protected]> Co-authored-by: David Ashpole <[email protected]>

#### 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)  #### Link to tracking issue Part of open-telemetry#35453  #### Testing Added additional benchmark tests --------- Signed-off-by: Florian Bacher <[email protected]>

…-telemetry#35750)  #### 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 ```  --------- Co-authored-by: Matthew Wear <[email protected]>

open-telemetry#35834)  #### 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.  #### Link to tracking issue Fixes 35010  #### Testing Added UT

#### Description Add new uptime scraper to emit the `system.uptime` metric  #### Link to tracking issue Fixes open-telemetry#31627  #### 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>  #### Documentation Updated readme & generated scraper docs

…SON status: ok (open-telemetry#36029)  #### 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  #### Link to tracking issue Fixes open-telemetry#36027  #### Testing Unit tests updated and are passing  #### Documentation Changelog updated

…#35985)  #### Description - This PR changes stability to `alpha` - Updates README.md for more clarity and detailed config  #### Link to tracking issue [open-telemetry#32669]  #### Testing No additional testing needed  #### Documentation Adds clarification of config, additional detail to detailed config, and notes about when and how to use which telemetry type.  --------- Co-authored-by: jeremyh <[email protected]>

…ce detector (open-telemetry#35737)  #### 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.  #### Link to tracking issue Fixes open-telemetry#34210  #### Testing ~  #### Documentation Added  Signed-off-by: ChrsMark <[email protected]>

…e system is mounted (open-telemetry#36000)  #### Description Do not set the default value of HOST_PROC_MOUNTINFO to respect root_path  #### Link to tracking issue Fixes open-telemetry#35990

following up open-telemetry#34908 open-telemetry#34627  #### Description  #### Link to tracking issue Fixes  #### Testing  #### Documentation  Signed-off-by: Jared Tan <[email protected]>

…n-telemetry#42942)  #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809  #### Link to tracking issue Fixes ~  #### Testing ~  #### Documentation Updated  Signed-off-by: ChrsMark <[email protected]>

… dataset routing (open-telemetry#42844)  #### Description Adds an additional way to set dataset based on scope attributes set by econding extensions. The main use case we are supporting with this right now is awslogsencodingextension which sets `encoding.format` like `aws.cloudtrail`, `aws.vpcflow`, `aws.elbaccess`. See open-telemetry#42899 for more detail.  #### Link to tracking issue Fixes  #### Testing Unit test added.  #### Documentation README updated.  --------- Co-authored-by: Carson Ip <[email protected]>

…ry#43419)  #### Description  Updates defaults for batching in Datadog exporter to match those that we recommend for the batch processor #### Link to tracking issue Updates open-telemetry#43082

…ic (open-telemetry#43095)  #### Description added prometheus NHCB (native histogram with custom buckets) to otel explicit histogram conversion.  #### Link to tracking issue Fixes open-telemetry#41131  #### Testing Added `TestMetricGroupData_toNHCBDistributionUnitTest` test function to test the conversion. --------- Co-authored-by: David Ashpole <[email protected]>

…lemetry#43384)  #### Description Add SSH connection implementation for the Cisco OS receiver to collect metrics from Cisco devices via SSH. This PR enhances the receiver with: - **SSH client infrastructure** with password/key authentication - **Semantic configuration** using `device.host.*` and `auth.*` conventions - **Modular scrapers** for system and interface metrics - **Complete metadata definitions** with generated code - **Proper validation** and error handling  #### Link to tracking issue open-telemetry#42647  #### Testing - Unit tests for config validation, factory, and SSH connections - All repository checks passing: make generate, make checkdoc, make checkmetadata - Generated lifecycle tests via mdatagen  #### Documentation - Complete README with configuration examples and metrics documentation - metadata.yaml - with interface and system metric definitions - Changelog entry added

… datapoint (open-telemetry#42203)  #### Description Update the timeseries info structs so we also store the int values for sums. And make sure we update and use this appropriately in the strategies.  #### Link to tracking issue Fixes open-telemetry#42202  #### Testing Added unit tests to the datapointstorage module, as well as to each strategy.  #### Documentation N/A  Signed-off-by: Ridwan Sharif <[email protected]> Co-authored-by: David Ashpole <[email protected]> Co-authored-by: Yang Song <[email protected]>

…erverreceiver (open-telemetry#43559)  #### Description The value passed from config for "sqlserver.instance.name", in case present, is currently used in the SQL's WHERE clause for top-query collection, which is not really required. It also makes unnecessary complications if the user provides an invalid/wrong instance name. We need to remove this usage from the top-query collection SQL.  #### Link to tracking issue Fixes open-telemetry#43558  #### Testing Unit tests updated.

#### Description This PR is to add a redfish receiver. Redfish is an open standard API that is commonly implemented on enterprise grade servers with BMCs (baseboard management controller) used for both in-band and out-of-band server management. This receiver provides a way for engineers to monitor their servers and server components such as fans and temperature sensors.  #### Link to tracking issue open-telemetry#33724  #### Testing Testing has been done on HPE iLO machines and logic similar to the [Telegraf redfish input receiver](https://github.com/influxdata/telegraf/tree/master/plugins/inputs/redfish) has been used (which I have contributed to in the past).  --------- Signed-off-by: Steve Freed <[email protected]> Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Antoine Toulme <[email protected]>

#### Description  #### Link to tracking issue Fixes open-telemetry#43216  #### Testing Tested with: ```yaml receivers: otlp: protocols: grpc: endpoint: 0.0.0.0:4317 http: endpoint: 0.0.0.0:4318 exporters: debug: coralogix: protocol: http application_name: otel application_name_attributes: - service.name - k8s.namespace.name - service.namespace domain: eu2.coralogix.com subsystem_name: k8s-saas subsystem_name_attributes: - subsystem.name private_key: ${env:CORALOGIX_PRIVATE_KEY} service: pipelines: traces: receivers: [otlp] exporters: [coralogix, debug] metrics: receivers: [otlp] exporters: [coralogix, debug] logs: receivers: [otlp] exporters: [coralogix, debug] ``` And ```yaml receivers: otlp: protocols: grpc: endpoint: 0.0.0.0:4317 http: endpoint: 0.0.0.0:4318 exporters: debug: coralogix: application_name: otel application_name_attributes: - service.name - k8s.namespace.name - service.namespace domain: eu2.coralogix.com subsystem_name: k8s-saas subsystem_name_attributes: - subsystem.name private_key: ${env:CORALOGIX_PRIVATE_KEY} service: pipelines: traces: receivers: [otlp] exporters: [coralogix, debug] metrics: receivers: [otlp] exporters: [coralogix, debug] logs: receivers: [otlp] exporters: [coralogix, debug] ``` Also did some tests with proxy.  #### Documentation - Changes done in `README.md`. Signed-off-by: Israel Blancas <[email protected]>

…etry#43595)  #### Description  #### Link to tracking issue Fixes the `data_type` field not being properly formatted ```json { "level": "error", "ts": "2025-10-16T10:26:48.992Z", "caller": "[email protected]/accumulator.go:97", "msg": "failed to translate metric", "resource": { "service.instance.id": "c2ca81b8-ce73-473d-b897-6b946935260f", "service.name": "otelcol-contrib", "service.version": "0.137.0" }, "otelcol.component.id": "prometheus", "otelcol.component.kind": "exporter", "otelcol.signal": "metrics", "data_type": "\u0004", "metric_name": "prometheus_http_request_duration_seconds", "stacktrace": "github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter.(*lastValueAccumulator).addMetric\n\tgithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/[email protected]/accumulator.go:97\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter.(*lastValueAccumulator).Accumulate\n\tgithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/[email protected]/accumulator.go:74\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter.(*collector).processMetrics\n\tgithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/[email protected]/collector.go:171\ngithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter.(*prometheusExporter).ConsumeMetrics\n\tgithub.com/open-telemetry/opentelemetry-collector-contrib/exporter/[email protected]/prometheus.go:93\ngo.opentelemetry.io/collector/consumer.ConsumeMetricsFunc.ConsumeMetrics\n\tgo.opentelemetry.io/collector/[email protected]/metrics.go:27\ngo.opentelemetry.io/collector/exporter/exporterhelper.NewMetrics.RequestConsumeFromMetrics.func2\n\tgo.opentelemetry.io/collector/exporter/[email protected]/internal/queuebatch/metrics.go:134\ngo.opentelemetry.io/collector/exporter/exporterhelper/internal/sender.(*sender[...]).Send\n\tgo.opentelemetry.io/collector/exporter/[email protected]/internal/sender/sender.go:31\ngo.opentelemetry.io/collector/exporter/exporterhelper/internal.(*timeoutSender[...]).Send\n\tgo.opentelemetry.io/collector/exporter/[email protected]/internal/timeout_sender.go:54\ngo.opentelemetry.io/collector/exporter/exporterhelper/internal.(*obsReportSender[...]).Send\n\tgo.opentelemetry.io/collector/exporter/[email protected]/internal/obs_report_sender.go:92\ngo.opentelemetry.io/collector/exporter/exporterhelper/internal.(*BaseExporter).Send\n\tgo.opentelemetry.io/collector/exporter/[email protected]/internal/base_exporter.go:112\ngo.opentelemetry.io/collector/exporter/exporterhelper/internal.NewMetricsRequest.newConsumeMetrics.func1\n\tgo.opentelemetry.io/collector/exporter/[email protected]/internal/new_request.go:176\ngo.opentelemetry.io/collector/consumer.ConsumeMetricsFunc.ConsumeMetrics\n\tgo.opentelemetry.io/collector/[email protected]/metrics.go:27\ngo.opentelemetry.io/collector/service/internal/refconsumer.refMetrics.ConsumeMetrics\n\tgo.opentelemetry.io/collector/[email protected]/internal/refconsumer/metrics.go:29\ngo.opentelemetry.io/collector/internal/fanoutconsumer.(*metricsConsumer).ConsumeMetrics\n\tgo.opentelemetry.io/collector/internal/[email protected]/metrics.go:62\ngo.opentelemetry.io/collector/processor/processorhelper.NewMetrics.func1\n\tgo.opentelemetry.io/collector/processor/[email protected]/metrics.go:71\ngo.opentelemetry.io/collector/consumer.ConsumeMetricsFunc.ConsumeMetrics\n\tgo.opentelemetry.io/collector/[email protected]/metrics.go:27\ngo.opentelemetry.io/collector/service/internal/refconsumer.refMetrics.ConsumeMetrics\n\tgo.opentelemetry.io/collector/[email protected]/internal/refconsumer/metrics.go:29\ngo.opentelemetry.io/collector/consumer.ConsumeMetricsFunc.ConsumeMetrics\n\tgo.opentelemetry.io/collector/[email protected]/metrics.go:27\ngithub.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusremotewritereceiver.(*prometheusRemoteWriteReceiver).handlePRW\n\tgithub.com/open-telemetry/opentelemetry-collector-contrib/receiver/[email protected]/receiver.go:198\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2322\nnet/http.(*ServeMux).ServeHTTP\n\tnet/http/server.go:2861\ngo.opentelemetry.io/collector/config/confighttp.(*decompressor).ServeHTTP\n\tgo.opentelemetry.io/collector/config/[email protected]/compression.go:272\ngo.opentelemetry.io/collector/config/confighttp.(*ServerConfig).ToServer.maxRequestBodySizeInterceptor.func2\n\tgo.opentelemetry.io/collector/config/[email protected]/server.go:350\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2322\ngo.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*middleware).serveHTTP\n\tgo.opentelemetry.io/contrib/instrumentation/net/http/[email protected]/handler.go:180\ngo.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.NewMiddleware.func1.1\n\tgo.opentelemetry.io/contrib/instrumentation/net/http/[email protected]/handler.go:67\nnet/http.HandlerFunc.ServeHTTP\n\tnet/http/server.go:2322\ngo.opentelemetry.io/collector/config/confighttp.(*clientInfoHandler).ServeHTTP\n\tgo.opentelemetry.io/collector/config/[email protected]/clientinfohandler.go:26\nnet/http.serverHandler.ServeHTTP\n\tnet/http/server.go:3340\nnet/http.(*conn).serve\n\tnet/http/server.go:2109" } ```  #### Testing  #### Documentation  --------- Signed-off-by: Pavol Loffay <[email protected]>

…st (open-telemetry#43032)  #### Description  #### Link to tracking issue Fixes open-telemetry#42792  #### Testing  #### Documentation  --------- Co-authored-by: Edmo Vamerlatti Costa <[email protected]>

…ry#43149)  #### Description This PR fixes an issue where the receiver was ignoring non-ready containers with an empty ContainerID, resulting in incomplete data collection for the newly introduced metrics `k8s.container.status.state` and `k8s.container.status.reason`.  #### Link to tracking issue Fixes open-telemetry#43147  #### Testing Updated `TestTransform`  #### Documentation

…-telemetry#43567)  #### Description - Implemented scraper that uses ICMP pinger - ICMP metrics: RTT (min, max, avg), packet loss ratio - Per-metric enable/disable configuration  #### Link to tracking issue [open-telemetry#29009](open-telemetry#29009)  #### Testing - Factory creation and scraper initialization - ICMP pinger functionality - Metrics scraper  #### Documentation - README with configuration examples - Metadata definitions for all metrics and resource attributes

…agated (open-telemetry#43575)  #### Description Use the `MergeCtx` function exposed in queue batch settings to configure a merge function for context when merging batches in the exporterhelper. This will allow propagting the metadata keys across the batches.  #### Link to tracking issue Fixes open-telemetry#41937  #### Testing Unit tests added.  #### Documentation Updated.  --------- Co-authored-by: Andrew Wilkins <[email protected]>

)  Hello! It looks like open-telemetry#41865 introduced a new feature flag and associated docs. The docs list it as `connector.spanmetrics.includeServiceInstanceID`, but I believe it's actually `connector.spanmetrics.includeCollectorInstanceID`. Looks like it might've changed due to feedback in the PR Passing `connector.spanmetrics.includeServiceInstanceID` resulted in the following error for me: > "Error: invalid argument "connector.spanmetrics.includeServiceInstanceID" for "--feature-gates" flag: no such feature gate "connector.spanmetrics.includeServiceInstanceID". valid gates: [awsemf.nodimrollupdefault clickhouse.json cloudfoundry.resourceAttributes.allow confighttp.framedSnappy confmap.enableMergeAppendOption connector.datadogconnector.NativeIngest connector.servicegraph.legacyLatencyMetricNames connector.servicegraph.legacyLatencyUnitMs connector.servicegraph.virtualNode connector.spanmetrics.excludeResourceMetrics connector.spanmetrics.includeCollectorInstanceID connector.spanmetrics.legacyMetricNames connector.spanmetrics.useSecondAsDefaultMetricsUnit datadog.EnableOperationAndResourceNameV2 datadog.EnableReceiveResourceSpansV2 exporter.PersistRequestContext exporter.awsxray.skiptimestampvalidation exporter.datadogexporter.DisableAPMStats exporter.datadogexporter.InferIntervalForDeltaMetrics exporter.datadogexporter.TraceExportUseCustomHTTPClient exporter.datadogexporter.UseLogsAgentExporter exporter.datadogexporter.metricexportnativeclient exporter.datadogexporter.metricexportserializerclient exporter.datadogexporter.metricremappingdisabled exporter.googlecloud.CustomMonitoredResources exporter.googlemanagedprometheus.intToDouble exporter.kafkaexporter.UseFranzGo exporter.prometheusexporter.DisableAddMetricSuffixes exporter.prometheusremotewritexporter.EnableMultipleWorkers exporter.prometheusremotewritexporter.RetryOn429 exporter.prometheusremotewritexporter.enableSendingRW2 exporter.xray.allowDot extension.jaegerremotesampling.replaceThriftWithProto extension.sumologic.updateCollectorMetadata filelog.allowFileDeletion filelog.allowHeaderMetadataParsing filelog.decompressFingerprint filelog.mtimeSortType filter.filterlog.useOTTLBridge filter.filtermetric.useOTTLBridge filter.filterspan.useOTTLBridge hostmetrics.process.bootTimeCache k8sattr.fieldExtractConfigRegex.disallow k8sattr.labelsAnnotationsSingular.allow logs.assignKeys logs.jsonParserArray metricsgeneration.MatchAttributes otelcol.printInitialConfig parser.uri.ecscompliant pdata.enableRefCounting pdata.useCustomProtoEncoding pdata.useProtoPooling pkg.translator.prometheus.NormalizeName pkg.translator.prometheus.PermissiveLabelSanitization postgresqlreceiver.preciselagmetrics processor.resourcedetection.propagateerrors processor.resourcedetection.removeGCPFaasID processor.tailsamplingprocessor.disableinvertdecisions processor.tailsamplingprocessor.metricstatcountspanssampled processor.tailsamplingprocessor.recordpolicy processor.transform.ConvertBetweenSumAndGaugeMetricContext receiver.azureeventhubreceiver.UseAzeventhubs receiver.datadogreceiver.Enable128BitTraceID receiver.hostmetricsreceiver.UseLinuxMemAvailable receiver.jaeger.DisableRemoteSampling receiver.kafkametricsreceiver.UseFranzGo receiver.kafkareceiver.UseFranzGo receiver.mongodb.removeDatabaseAttr receiver.postgresql.connectionPool receiver.postgresql.separateSchemaAttr receiver.prometheusreceiver.EnableCreatedTimestampZeroIngestion receiver.prometheusreceiver.EnableNativeHistograms receiver.prometheusreceiver.RemoveLegacyResourceAttributes receiver.prometheusreceiver.RemoveStartTimeAdjustment receiver.prometheusreceiver.UseCollectorStartTimeFallback receiver.prometheusreceiver.UseCreatedMetric receiver.sqlserver.RemoveServerResourceAttribute receiver.vcenter.resourcePoolMemoryUsageAttribute receiverhelper.newReceiverMetrics service.AllowNoPipelines service.noopTracerProvider service.profilesSupport stanza.synchronousLogEmitter telemetry.UseLocalHostAsDefaultMetricsAddress telemetry.disableHighCardinalityMetrics telemetry.newPipelineTelemetry transform.flatten.logs]" So here I just fix the name in the docs. #### Description  n/a #### Link to tracking issue n/a  #### Testing I copy pasted the flag name string from the doc change into my dockerfile and made sure it ran (no typos).  #### Documentation  Just updating `connector/spanmetricsconnector/README.md` as described above. ---- Thanks for the feature! Co-authored-by: Alex Boten <[email protected]>

…lemetry#43056) WIP  #### Description This PR parses VPC flow logs into log record attributes. Please see the updated README file for details.  #### Link to tracking issue Fixes open-telemetry#43017  #### Testing Unit tests added and updated.  #### Documentation README updated. --------- Co-authored-by: Constança Manteigas <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>

open-telemetry#43622)  #### Description Currently in top-query collection, the time from host is passed into the query parameter as a reference to calculate the collection window. This logic does not work when the clocks of collector instance and the database are in different timezones, and it leads to an inaccurate collection window. _`WHERE` clause in current implementation:_ ```SQL WHERE LAST_ACTIVE_TIME >= TO_DATE(:1, 'yyyy-mm-dd hh24:mi:ss') - NUMTODSINTERVAL(:2, 'SECOND') ``` _Proposed fix:_ ```SQL WHERE LAST_ACTIVE_TIME >= SYSDATE - NUMTODSINTERVAL(:1, 'SECOND') ```  #### Link to tracking issue Fixes open-telemetry#43621

…ery_collection (open-telemetry#43618)  #### Description As a standard, all type of interval values in collector config currently requires an 's' suffix to interpret the unit. But the recently introduced lookback_time in top_query_collection does not follow this pattern. This needs to be fixed to maintain consistency and avoid ambiguity in unit interpretation.  #### Link to tracking issue Fixes open-telemetry#43573  #### Testing Unit tests updated

…st without cgroups (open-telemetry#43641)  #### Description Fixing a bug where host does not have a /proc/<process id>/cgroup file because the device does not use cgroups. This causes the process scraper to skip the publishing the metric. I basically made the failure to retrieve a cgroup non-fatal to the process scraper.  #### Link to tracking issue Fixes open-telemetry#43640  #### Testing Updated Unit tests  #### Documentation  Co-authored-by: Braydon Kains <[email protected]>

…telemetry#43653) #### Description Similarly done in the past, see open-telemetry#38337 Ref: https://github.blog/changelog/2025-09-19-github-actions-macos-13-runner-image-is-closing-down/  #### Link to tracking issue n/a  #### Testing n/a  #### Documentation n/a  --------- Co-authored-by: Alex Boten <[email protected]>

…pen-telemetry#41107)  #### Description Add support for authenticator extensions in Azure Monitor exporter.  #### Link to tracking issue Fixes open-telemetry#41004  #### Documentation Updated `Authentication.md` with an example. Signed-off-by: Christian Artin <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>

…tes in generated metrics (open-telemetry#43395) #### Description Added a new configuration field to keep the resource attributes.  #### Link to tracking issue Fixes open-telemetry#43394 Signed-off-by: Israel Blancas <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>

…#43681)  #### Description Without a valid `runCtx`, anything that attempts to use the context segfaults. In open-telemetry/opentelemetry-collector#14058 I am using the context, so this test borks. This adds the runCtx to fix it.  #### Link to tracking issue open-telemetry/opentelemetry-collector#14058  #### Testing  #### Documentation  Signed-off-by: sinkingpoint <[email protected]>

…ng_keys() functions (open-telemetry#43539)  #### Description Support dynamic keys in the `delete_key` and `delete_matching_keys` functions, allowing the key to be specified at runtime  #### Link to tracking issue Fixes open-telemetry#43081 --------- Signed-off-by: odubajDT <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>

…elemetry#42934)  #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809  #### Link to tracking issue Fixes ~  #### Testing ~  #### Documentation Updated  --------- Signed-off-by: ChrsMark <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>

…pen-telemetry#43272) Updating the unit of the metric `postgresql.table.vacuum.count` in `postgresqlreceiver` to be `vacuum` instead of `vacuums`, to comply with the semantic conventions.  #### Link to tracking issue Fixes: [open-telemetry#43207](open-telemetry#43207)  #### Testing  #### Documentation

…en-telemetry#42983)  #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809  #### Link to tracking issue Fixes ~  #### Testing ~  #### Documentation Updated  Signed-off-by: ChrsMark <[email protected]>

…ry#42948)  #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809  #### Link to tracking issue Fixes ~  #### Testing ~  #### Documentation Updated  Signed-off-by: ChrsMark <[email protected]>

…elemetry#42960)  #### Description open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation. This PR makes use of this functionality. We start by setting the stability of all metrics to `development`. More info about levels can be found at https://github.com/open-telemetry/opentelemetry-specification/blob/v1.49.0/oteps/0232-maturity-of-otel.md#maturity-levels. Related to: - open-telemetry/opentelemetry-collector#11878 - open-telemetry/opentelemetry-collector#13297 - open-telemetry#35325 - open-telemetry#42809  #### Link to tracking issue Fixes ~  #### Testing ~  #### Documentation Updated  Signed-off-by: ChrsMark <[email protected]>

dependabot bot added the dependencies Pull requests that update a dependency file label Jan 31, 2022

dependabot bot mentioned this pull request Jan 31, 2022

Bump github.com/klauspost/compress from 1.11.1 to 1.14.1 in /exporter/honeycombexporter #1197

Closed

dependabot bot closed this Feb 21, 2022

dependabot bot deleted the dependabot/go_modules/exporter/honeycombexporter/github.com/klauspost/compress-1.14.2 branch February 21, 2022 16:03

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Bump github.com/klauspost/compress from 1.11.1 to 1.14.2 in /exporter/honeycombexporter #1234

Bump github.com/klauspost/compress from 1.11.1 to 1.14.2 in /exporter/honeycombexporter #1234

Uh oh!

dependabot bot commented on behalf of github Jan 31, 2022

Uh oh!

dependabot bot commented on behalf of github Feb 21, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Bump github.com/klauspost/compress from 1.11.1 to 1.14.2 in /exporter/honeycombexporter #1234

Bump github.com/klauspost/compress from 1.11.1 to 1.14.2 in /exporter/honeycombexporter #1234

Uh oh!

Conversation

dependabot bot commented on behalf of github Jan 31, 2022

v1.14.2

What's Changed

New Contributors

v1.14.1

What's Changed

New Contributors

v1.14.0

What's Changed

New Contributors

v1.13.6

Changelog

Uh oh!

dependabot bot commented on behalf of github Feb 21, 2022

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant