Add section on how to build an otelcol dist #1234
Merged
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
bogdandrutu
reviewed
Oct 12, 2020
bogdandrutu
changed the title
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
Signed-off-by: Juraci Paixão Kröhling <[email protected]>
jpkrohling
force-pushed
the
jpkrohling/add-link-to-blog-post-on-building-custom-otelcol
branch
from
73f9801 to
acf4d51
Compare
owais
reviewed
Oct 12, 2020
| ## Creating your own OpenTelemetry Collector distribution | ||
|
|
||
| A guide on how to create your own distribution is available in this blog post: | ||
| ["Building your own OpenTelemetry Collector distribution"](https://medium.com/p/42337e994b63) |
There was a problem hiding this comment.
I may be wrong but isn't medium content sometimes locked behind a paywall now? Not sure if a freely available project both as in beer and speech should rely on extended documentation that might not be accessible to everyone.
Nothing against medium or content they host. Just not sure if OpenTelemetry as a product should direct users to content/documentation/guides that they might not be able to read.
Great article BTW @jpkrohling
There was a problem hiding this comment.
Oh, I see this is the official OpenTelemetry blog on medium. I suppose this decision has already been taken then by the maintainers and we are fine with publishin there? Please disregard if that's the case.
There was a problem hiding this comment.
sometimes locked behind a paywall now
Each author/publication can choose to make money on Medium and have a paywall in front of individual posts, or to allow all users to have free access to the content, without any paywalls. I always publish articles without opting-in for the paywall, and I believe the OpenTelemetry publication also doesn't.
anuraaga
reviewed
Oct 13, 2020
owais
approved these changes
Oct 13, 2020
anuraaga
approved these changes
Oct 14, 2020
kisieland
referenced
this pull request
in kisieland/opentelemetry-collector-contrib
Mar 16, 2021
Updates #1234 Signed-off-by: Bogdan Drutu <[email protected]>
ljmsc
referenced
this pull request
in ljmsc/opentelemetry-collector-contrib
Feb 21, 2022
codeboten
pushed a commit
that referenced
this pull request
Nov 23, 2022
… add 'messaging.url' span attribute (#1234) * boto3sqs: Fix various issues * do not use 'otel' prefix for propagation keys to make propagation compatible with other SQS instrumentations like Node.Js Inject propergator.fields keys into the MessageAttributeNames argument for 'receive_message' calls to retreive the corresponding message attributes * add 'messaging.url' span attribute to SQS spans * add boto3sqs instrumentation to tox.ini to run tests in CI * add some basic unit tests * changelog * fix linting issues * unset instrumented flag on uninstrument
mx-psi
added a commit
that referenced
this pull request
Oct 4, 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 #35606
jriguera
pushed a commit
to springernature/opentelemetry-collector-contrib
that referenced
this pull request
Oct 4, 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. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#35606
ghost
pushed a commit
to sematext/opentelemetry-collector-contrib
that referenced
this pull request
Oct 9, 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. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#35606
evan-bradley
pushed a commit
that referenced
this pull request
Oct 10, 2024
…atus (#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 #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]>
andrzej-stencel
pushed a commit
that referenced
this pull request
Oct 15, 2024
<!--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.-->
andrzej-stencel
pushed a commit
that referenced
this pull request
Oct 15, 2024
…rning error to avoid upstream retries (#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.-->
andrzej-stencel
pushed a commit
that referenced
this pull request
Oct 16, 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 #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]>
andrzej-stencel
pushed a commit
that referenced
this pull request
Oct 16, 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 #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 #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]>
djaglowski
pushed a commit
that referenced
this pull request
Oct 16, 2024
#### 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 #5909 <!--Describe what testing was performed and which tests were added.--> #### Testing Added
MovieStoreGuy
pushed a commit
that referenced
this pull request
Oct 17, 2024
andrzej-stencel
pushed a commit
that referenced
this pull request
Oct 17, 2024
… prefix conflict in OTel mapping mode (#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.-->
djaglowski
pushed a commit
that referenced
this pull request
Oct 17, 2024
<!--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 #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.-->
MovieStoreGuy
pushed a commit
that referenced
this pull request
Oct 18, 2024
andrzej-stencel
pushed a commit
that referenced
this pull request
Oct 18, 2024
…only (#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.-->
andrzej-stencel
pushed a commit
that referenced
this pull request
Oct 21, 2024
<!--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.-->
djaglowski
pushed a commit
that referenced
this pull request
Oct 22, 2024
<!--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](#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 #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.
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
… dataset routing (open-telemetry#42844) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes <!--Describe what testing was performed and which tests were added.--> #### Testing Unit test added. <!--Describe the documentation added.--> #### Documentation README updated. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Carson Ip <[email protected]>
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
…ry#43419) <!--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. open-telemetry#1234) or full URL to issue, if applicable. --> 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
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
…ic (open-telemetry#43095) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description added prometheus NHCB (native histogram with custom buckets) to otel explicit histogram conversion. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#41131 <!--Describe what testing was performed and which tests were added.--> #### Testing Added `TestMetricGroupData_toNHCBDistributionUnitTest` test function to test the conversion. --------- Co-authored-by: David Ashpole <[email protected]>
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
…lemetry#43384) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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 <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#42647 <!--Describe what testing was performed and which tests were added.--> #### 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 <!--Describe the documentation added.--> #### Documentation - Complete README with configuration examples and metrics documentation - metadata.yaml - with interface and system metric definitions - Changelog entry added
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
… datapoint (open-telemetry#42203) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42202 <!--Describe what testing was performed and which tests were added.--> #### Testing Added unit tests to the datapointstorage module, as well as to each strategy. <!--Describe the documentation added.--> #### Documentation N/A <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: Ridwan Sharif <[email protected]> Co-authored-by: David Ashpole <[email protected]> Co-authored-by: Yang Song <[email protected]>
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
…erverreceiver (open-telemetry#43559) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43558 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests updated.
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 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 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. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry#33724 <!--Describe what testing was performed and which tests were added.--> #### 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). <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: Steve Freed <[email protected]> Co-authored-by: Antoine Toulme <[email protected]> Co-authored-by: Antoine Toulme <[email protected]>
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 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. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43216 <!--Describe what testing was performed and which tests were added.--> #### 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. <!--Describe the documentation added.--> #### Documentation - Changes done in `README.md`. Signed-off-by: Israel Blancas <[email protected]>
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
…etry#43595) <!--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. open-telemetry#1234) or full URL to issue, if applicable. --> #### 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" } ``` <!--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: Pavol Loffay <[email protected]>
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
…st (open-telemetry#43032) <!--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. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#42792 <!--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: Edmo Vamerlatti Costa <[email protected]>
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
…ry#43149) <!--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 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`. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#43147 <!--Describe what testing was performed and which tests were added.--> #### Testing Updated `TestTransform` <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.-->
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
…-telemetry#43567) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description - Implemented scraper that uses ICMP pinger - ICMP metrics: RTT (min, max, avg), packet loss ratio - Per-metric enable/disable configuration <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue [open-telemetry#29009](open-telemetry#29009) <!--Describe what testing was performed and which tests were added.--> #### Testing - Factory creation and scraper initialization - ICMP pinger functionality - Metrics scraper <!--Describe the documentation added.--> #### Documentation - README with configuration examples - Metadata definitions for all metrics and resource attributes <!--Please delete paragraphs that you did not use before submitting.-->
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
…agated (open-telemetry#43575) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes open-telemetry#41937 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests added. <!--Describe the documentation added.--> #### Documentation Updated. <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Andrew Wilkins <[email protected]>
ChrsMark
pushed a commit
to ChrsMark/opentelemetry-collector-contrib
that referenced
this pull request
Oct 20, 2025
) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> 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 <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> n/a #### Link to tracking issue n/a <!--Describe what testing was performed and which tests were added.--> #### Testing I copy pasted the flag name string from the doc change into my dockerfile and made sure it ran (no typos). <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> Just updating `connector/spanmetricsconnector/README.md` as described above. ---- Thanks for the feature! Co-authored-by: Alex Boten <[email protected]>
edmocosta
added a commit
that referenced
this pull request
Oct 20, 2025
WIP <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description This PR parses VPC flow logs into log record attributes. Please see the updated README file for details. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #43017 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests added and updated. <!--Describe the documentation added.--> #### Documentation README updated. --------- Co-authored-by: Constança Manteigas <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>
atoulme
pushed a commit
that referenced
this pull request
Oct 20, 2025
#43622) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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') ``` <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #43621
dmitryax
pushed a commit
that referenced
this pull request
Oct 20, 2025
…ery_collection (#43618) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #43573 <!--Describe what testing was performed and which tests were added.--> #### Testing Unit tests updated
songy23
pushed a commit
that referenced
this pull request
Oct 20, 2025
…st without cgroups (#43641) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #43640 <!--Describe what testing was performed and which tests were added.--> #### Testing Updated Unit tests <!--Describe the documentation added.--> #### Documentation <!--Please delete paragraphs that you did not use before submitting.--> Co-authored-by: Braydon Kains <[email protected]>
codeboten
added a commit
that referenced
this pull request
Oct 20, 2025
#### Description Similarly done in the past, see #38337 Ref: https://github.blog/changelog/2025-09-19-github-actions-macos-13-runner-image-is-closing-down/ <!-- 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 n/a <!--Describe the documentation added.--> #### Documentation n/a <!--Please delete paragraphs that you did not use before submitting.--> --------- Co-authored-by: Alex Boten <[email protected]>
edmocosta
added a commit
that referenced
this pull request
Oct 21, 2025
…41107) <!--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 authenticator extensions in Azure Monitor exporter. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #41004 <!--Describe the documentation added.--> #### Documentation Updated `Authentication.md` with an example. Signed-off-by: Christian Artin <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>
edmocosta
added a commit
that referenced
this pull request
Oct 21, 2025
…tes in generated metrics (#43395) #### Description Added a new configuration field to keep the resource attributes. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #43394 Signed-off-by: Israel Blancas <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>
songy23
pushed a commit
that referenced
this pull request
Oct 21, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue open-telemetry/opentelemetry-collector#14058 <!--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: sinkingpoint <[email protected]>
songy23
pushed a commit
that referenced
this pull request
Oct 21, 2025
…ng_keys() functions (#43539) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Support dynamic keys in the `delete_key` and `delete_matching_keys` functions, allowing the key to be specified at runtime <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #43081 --------- Signed-off-by: odubajDT <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>
songy23
pushed a commit
that referenced
this pull request
Oct 21, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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 - #35325 - #42809 <!-- 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 Updated <!--Please delete paragraphs that you did not use before submitting.--> --------- Signed-off-by: ChrsMark <[email protected]> Co-authored-by: Edmo Vamerlatti Costa <[email protected]>
jefferbrecht
pushed a commit
to jefferbrecht/opentelemetry-collector-contrib
that referenced
this pull request
Oct 22, 2025
…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. <!-- Issue number (e.g. open-telemetry#1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes: [open-telemetry#43207](open-telemetry#43207) <!--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.-->
codeboten
pushed a commit
that referenced
this pull request
Oct 22, 2025
…2983) <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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 - #35325 - #42809 <!-- 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 Updated <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: ChrsMark <[email protected]>
codeboten
pushed a commit
that referenced
this pull request
Oct 22, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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 - #35325 - #42809 <!-- 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 Updated <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: ChrsMark <[email protected]>
codeboten
pushed a commit
that referenced
this pull request
Oct 22, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### 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 - #35325 - #42809 <!-- 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 Updated <!--Please delete paragraphs that you did not use before submitting.--> Signed-off-by: ChrsMark <[email protected]>
songy23
pushed a commit
that referenced
this pull request
Oct 22, 2025
<!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue Fixes #43719 Signed-off-by: Israel Blancas <[email protected]>
atoulme
pushed a commit
that referenced
this pull request
Oct 23, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> #### Description Adds integration test for ICMP Check Receiver that pings container host and collects metrics. Test setup lets any group open the socket so the integration test can send real ICMP probes. If the `sysctl` can’t be applied, the test skips to avoid CI failures. <!-- Issue number (e.g. #1234) or full URL to issue, if applicable. --> #### Link to tracking issue [#29009](#29009) <!--Describe what testing was performed and which tests were added.--> #### Testing - New integration test for ICMP Check Receiver <!--Please delete paragraphs that you did not use before submitting.-->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Signed-off-by: Juraci Paixão Kröhling [email protected]
Description: Added readme section with links to resources on how to create custom OpenTelemetry Collector distributions.
Link to tracking Issue: open-telemetry/opentelemetry-collector#213
Testing: n/a
Documentation: n/a