Add section on how to build an otelcol dist #1234

jpkrohling · 2020-10-09T14:04:19Z

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

README.md

Signed-off-by: Juraci Paixão Kröhling <[email protected]>

owais · 2020-10-12T16:42:18Z

README.md

+## 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)


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

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.

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.

README.md

Updates #1234 Signed-off-by: Bogdan Drutu <[email protected]>

… 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

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

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

…atus (#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 #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]>

#### 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 (#35740)  #### Description Log metrics validation error instead of returning to avoid upstream retries  #### Link to tracking issue  #### Testing  #### Documentation

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

#### 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  #### Link to tracking issue #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 Follow [the contract](https://github.com/open-telemetry/opentelemetry-collector/blob/df3c9e38a80ccc3b14705462be2e2e51c628a3b3/receiver/doc.go#L10) for cloudflare receiver  #### Link to tracking issue Related #5909  #### Testing Added

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

… prefix conflict in OTel mapping mode (#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

#### 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 #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 #34375

) Reduces allocations as the collector doesn't need to clone the incoming data  #### Description  #### Link to tracking issue Fixes  #### Testing  #### Documentation

…g pod informer (open-telemetry#37138)  #### Description This PR is an alternative approach to the previous fix made for open-telemetry#37056, which did not fully solve the issue of the deployment name not being added to a pod after the initial informer sync  #### Link to tracking issue Fixes open-telemetry#37056  #### Testing Re-enabled the flaky E2E test --------- Signed-off-by: Florian Bacher <[email protected]>

…elemetry#37397)  #### Description Change the githubgen we use to the one defined in opentelemetry-go-build-tools  #### Link to tracking issue See open-telemetry#37294

#### Description make `check-collector-module-version.sh` worked on macos with gnu-sed.  #### Link to tracking issue Fixes open-telemetry#37304  #### Testing  #### Documentation  Co-authored-by: Sean Marciniak <[email protected]>

@Saumya40-codes

…in jaegerreceiver (open-telemetry#36961)  #### Description - This PR adds the logging related to the server starting under the [jaegerreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/jaegerreceiver) - Added logs when: GRPC, Thrift Http, Thrift Binary and Thrift compact server starts  #### Link to tracking issue Fixes jaegertracing/jaeger#6412 #### How was change tested? Running collector with `jaegerreceiver` enabled with its all transports #### Output ``` @Saumya40-codes ➜ /workspaces/opentelemetry-collector-contrib (log-endpoints) $ ./bin/otelcontribcol_linux_amd64 --config config.yaml 2024-12-27T15:37:23.428Z info [email protected]/service.go:164 Setting up own telemetry... 2024-12-27T15:37:23.428Z info telemetry/metrics.go:70 Serving metrics {"address": "localhost:8888", "metrics level": "Normal"} 2024-12-27T15:37:23.428Z info builders/builders.go:26 Development component. May change in the future. {"kind": "exporter", "data_type": "traces", "name": "debug"} 2024-12-27T15:37:23.436Z info [email protected]/service.go:230 Starting otelcontribcol... {"Version": "0.116.0-dev", "NumCPU": 2} 2024-12-27T15:37:23.436Z info extensions/extensions.go:39 Starting extensions... 2024-12-27T15:37:23.436Z info [email protected]/trace_receiver.go:252 Starting UDP server for Binary Thrift {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:6831"} 2024-12-27T15:37:23.436Z info [email protected]/trace_receiver.go:274 Starting UDP server for Compact Thrift {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:6832"} 2024-12-27T15:37:23.436Z info [email protected]/trace_receiver.go:398 Starting HTTP server for Jaeger Collector {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:14268"} 2024-12-27T15:37:23.436Z info [email protected]/trace_receiver.go:423 Starting gRPC server for Jaeger Collector {"kind": "receiver", "name": "jaeger", "data_type": "traces", "endpoint": "0.0.0.0:14250"} 2024-12-27T15:37:23.436Z info [email protected]/service.go:253 Everything is ready. Begin running and processing data. ``` #### config file used ``` receivers: jaeger: protocols: grpc: endpoint: "0.0.0.0:14250" thrift_http: endpoint: "0.0.0.0:14268" thrift_binary: endpoint: "0.0.0.0:6831" thrift_compact: endpoint: "0.0.0.0:6832" exporters: debug: {} service: pipelines: traces: receivers: [jaeger] exporters: [debug] ``` cc @fatsheep9146 --------- Signed-off-by: Saumyacodes-40 <[email protected]> Co-authored-by: Yuri Shkuro <[email protected]>

…histograms (open-telemetry#37432)  #### Description While addressing comments a bug was added to the logic of calculating of the desired scale and it slipped through tests. Fix the bug (use `min` instead of `max`) and update tests to avoid regressions in the future.  #### Link to tracking issue Fixes open-telemetry#37416  #### Testing Update tests to separately cover positive and negative buckets.  #### Documentation n/a

…7440)  #### Description Adds an extra `make gotidy` after `make generate` and `make crosslink`  See open-telemetry#37437 for example where it failed because of this.

#### Description - This PR - switches over all usages of the githubgen tool to the new tool location by adjusting make targets and the check-code-owners pipeline - introduces the new githubgen tool at its latest v0.17.0 version - adds `make gengithub` to the commands to run in the contribution guide - re-generates the codeowners and allowlist files using the new githubgen tool (only cosmetic changes)  #### Link to tracking issue Part of open-telemetry#37294  --------- Signed-off-by: Moritz Wiesinger <[email protected]>

#### Description This PR enhances the `httpcheckreceiver` by adding support for multiple endpoints (`endpoints`). Users can now specify a list of endpoints in addition to a single `endpoint` for each target. This improves flexibility and reduces redundancy when monitoring multiple similar endpoints. Additional changes include: - Updates to `config.go` to handle `endpoints`. - Updates to `scraper.go` to iterate over and scrape all specified endpoints. - Added unit tests for the new functionality in `config_test.go` and `scraper_test.go`. - Updated documentation (`README.md`) to reflect the changes.  #### Link to Tracking Issue Fixes open-telemetry#37121  #### Testing - All existing and new tests pass. - Tested the `httpcheckreceiver` manually using the following configuration: ```yaml receivers: httpcheck: collection_interval: 30s targets: - method: "GET" endpoints: - "https://opentelemetry.io" - method: "GET" endpoints: - "http://localhost:8080/hello" - "http://localhost:8080/hello" headers: Authorization: "Bearer eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJqYXZhaW51c2UiLCJleHAiOjE3MzcwMzMzMTcsImlhdCI6MTczNzAxNTMxN30.qNb_hckvlqfWmnnaw2xP9ie2AKGO6ljzGxcMotoFZg3CwcYSTGu7VE6ERsvX_nHlcZOYZHgPc7_9WSBlCZ9M_w" - method: "GET" endpoint: "http://localhost:8080/hello" headers: Authorization: "Bearer eyJhbGciOiJIUzUxMiJ9.eyJzdWIiOiJqYXZhaW51c2UiLCJleHAiOjE3MzcwMzMzMTcsImlhdCI6MTczNzAxNTMxN30.qNb_hckvlqfWmnnaw2xP9ie2AKGO6ljzGxcMotoFZg3CwcYSTGu7VE6ERsvX_nHlcZOYZHgPc7_9WSBlCZ9M_w" processors: batch: send_batch_max_size: 1000 send_batch_size: 100 timeout: 10s exporters: debug: verbosity: detailed service: pipelines: metrics: receivers: [httpcheck] processors: [batch] exporters: [debug] ``` #### **Documentation** Describe any documentation changes or additions: ```markdown  #### Documentation - Updated the `README.md` to include examples for `endpoints`. - Verified `documentation.md` for metric output consistency. --------- Co-authored-by: Antoine Toulme <[email protected]>

…lemetry#37424)  #### Description Update example in README to reflect map instead of bool that is expected. ``` $ otelcol --version otelcontribcol version 0.118.0-dev $ otelcol validate --config config.yaml Error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s): error decoding 'receivers': error reading configuration for "active_directory_ds": decoding failed due to the following error(s): 'metrics.active_directory.ds.replication.network.io' expected a map, got 'bool' 2025/01/22 18:33:20 collector server run finished with error: failed to get config: cannot unmarshal the configuration: decoding failed due to the following error(s): error decoding 'receivers': error reading configuration for "active_directory_ds": decoding failed due to the following error(s): 'metrics.active_directory.ds.replication.network.io' expected a map, got 'bool' ```  #### Link to tracking issue Fixes  #### Testing  #### Documentation Updated example used in README for this receiver to not throw errors.

…telemetry#37399)  #### Description * Change `exporter.prometheusremotewriteexporter.deprecateCreatedMetric`feature gate from Beta to Stable * Adapt some test cases that were considering this feature as disable  #### Link to tracking issue open-telemetry#35003

…w` feature gate to beta (open-telemetry#37452)  #### Description This feature gate, when enabled, allows some metric attributes received from Cloud Foundry to be properly moved to be resource attributes. This feature gate was introduced in `v0.117.0`, so it can now be moved to `beta` for `v0.119.0`.  #### Link to tracking issue Related to open-telemetry#34824

…f the signal (open-telemetry#36715)  #### Description It loops through token.Attributes and appends it to the scoped attribute of the signal  #### Link to tracking issue Fixes open-telemetry#36641  #### Testing Added UT  #### Documentation

…emetry#37457)  #### Description Support obfuscating SQL and Redis queries in APM stats in Datadog Connector. replace statement in otelcontribcol was necessary due to failing build in pipeline. It doesn't appear that any modules use any affected functions, but building otelcontribcol with ocb failed due to an API change. Also opened an issue to bump the `receiver/awscontainerinsight` dependency so that this replace can be removed in the future: open-telemetry#37486  #### Link to tracking issue Replaces open-telemetry#35401  #### Testing Added TestObfuscate in connector_native_test.go  #### Documentation added release note and link to semantics on Datadog vendor website

@ChrsMark

…elemetry#36454)  #### Description Adds boilerplate code for a new signal to metrics connector.  #### Link to tracking issue Part of open-telemetry#35930  #### Testing Unit tests provided as required.  #### Documentation Added basic README. Will add more details with future commits.  CC: @ChrsMark --------- Co-authored-by: Christos Markou <[email protected]>

…pen-telemetry#36145)  #### Description Fixed issue with `k8sattributesprocessor` where digest is not properly separated from tag if both are present. used official docker library to perform parsing.  #### Link to tracking issue Fixes open-telemetry#36131  #### Testing unit tests integration/e2e tests  #### Documentation N/A. Fields are already described correctly, this is simply fixing parsing logic

…ation (open-telemetry#36148)  #### Description The changes includes providing a custom `DecoderConfig` with `ErrorUnused` enabled instead of using the default `DecoderConfig` provided by `koanf`  #### Link to tracking issue Fixes: open-telemetry#35838    --------- Signed-off-by: Alok Kumar Singh <[email protected]> Co-authored-by: Evan Bradley <[email protected]>

…e update events (open-telemetry#36505)  #### Description The load balancing exporter's k8sresolver was not handling update events properly. The `callback` function was being executed after cleanup of old endpoints and also after adding new endpoints. This causes exporter churn in the case of an event in which the lists contain shared elements. See the [documentation](https://pkg.go.dev/k8s.io/client-go/tools/cache#ResourceEventHandler) for examples where the state might change but the IP Addresses would not, including the regular re-list events that might have zero changes.  #### Link to tracking issue Fixes open-telemetry#35658 May be related to open-telemetry#35810 as well.  #### Testing Added tests for no-change onChange call.

#### Description  Follows open-telemetry/opentelemetry-collector/pull/11412

…ent shutdown (open-telemetry#36296)  #### Description When using a storage extension, the component will call Close on the client during component shutdown. This fixes a bug that resulted in a file potentially remaining locked after component shutdown.  #### Link to tracking issue open-telemetry#36238  #### Testing Since reproducing this was described in the issue as "difficult without custom code", testing just involved ensuring that unit tests covered the added code and ran successfully, and manually ensuring that the collector could still receive events from AEH.

…sm (open-telemetry#36518)  #### Description - introduce active file grouping according to the description in ticket - unit tests  #### Link to tracking issue Fixes open-telemetry#23787 --------- Signed-off-by: odubajDT <[email protected]>

…open-telemetry#36451)  #### Description This pull request introduces a new configurable parameter `reporter_period` for the Datadog exporter’s host metadata configuration. This enhancement allows users to specify the frequency at which host metadata is sent to Datadog. The changes span multiple files and include updates to configuration, factory methods, and test cases. Enhancements to Datadog exporter: * [`.chloggen/add-configurable-reporter-period-for-host-metadata.yaml`](diffhunk://#diff-e3e3c57c49d2a921abc8470bccafabf4d632b0dc142eb3e95b3b6fac57107a11R1-R27): Added a changelog entry for the new `reporter_period` parameter. * [`exporter/datadogexporter/examples/collector.yaml`](diffhunk://#diff-766be9823b8ec8b8de17e2c6c785d9f93e13b5a7e84ff441040077ab5e726a79R452-R456): Added documentation for the new `reporter_period` parameter in the example configuration file. * [`exporter/datadogexporter/factory.go`](diffhunk://#diff-c9e9f39ffda08a2af74c0d54d37f21e14cdb95c4136cdbe238de6be2bfe31389L127-R125): Updated the factory to use the `reporter_period` from the configuration instead of a hardcoded value. Configuration updates: * [`exporter/datadogexporter/internal/hostmetadata/config.go`](diffhunk://#diff-0c9f0862d61390add366aca3e30834a1e01f16a3865ef9aca61831cad3459f53R31-R32): Added `ReporterPeriod` to the `PusherConfig` struct. * [`pkg/datadog/config/config.go`](diffhunk://#diff-747858d4c8fea28a92227df09f17ebee01df63dad04812ac5d30a392c9970b73R136-R139): Added validation for the `reporter_period` to ensure it is a positive duration and set a default value. [[1]](diffhunk://#diff-747858d4c8fea28a92227df09f17ebee01df63dad04812ac5d30a392c9970b73R136-R139) [[2]](diffhunk://#diff-747858d4c8fea28a92227df09f17ebee01df63dad04812ac5d30a392c9970b73R347) Test case updates: * `exporter/datadogexporter/factory_test.go`, `exporter/datadogexporter/logs_exporter_test.go`, `exporter/datadogexporter/metrics_exporter_test.go`, `exporter/datadogexporter/traces_exporter_test.go`: Updated test cases to include the new `reporter_period` parameter. [[1]](diffhunk://#diff-c50b6d1f06d62a58b6422f3218526437c16554faa2b7fc8eee1d32c021f00ca4R311) [[2]](diffhunk://#diff-94f5b0119d06dbcfee20cd9b99a104ef208e027c166c463321670a5197e83714R233-R235) [[3]](diffhunk://#diff-005adb1774d2a402bdd7adf3b6aa150117bf6b3c0bb634bf2c68c6b33f0ce1b5L61-R63) [[4]](diffhunk://#diff-c19daad040b7310787c0012e5c660dc18a07ba16036d0eaa31a0e18c551d0ef3R148-R150) * [`pkg/datadog/config/config_test.go`](diffhunk://#diff-d3a3c19e78bbac07597c6210b4d051f4678df2752e06c82d0f040c52207c5970R97-R105): Added test cases to validate the `reporter_period` configuration. [[1]](diffhunk://#diff-d3a3c19e78bbac07597c6210b4d051f4678df2752e06c82d0f040c52207c5970R97-R105) [[2]](diffhunk://#diff-d3a3c19e78bbac07597c6210b4d051f4678df2752e06c82d0f040c52207c5970R186-R197)  #### Link to tracking issue Fixes open-telemetry#36450  #### Testing  #### Documentation

…35898)  #### Description Update the prerequisites requirements for using this receiver (+ integration tests) to the latest officially supported PostgreSQL version  #### Link to tracking issue Fixes open-telemetry#30923  #### Testing Unit & integration tests  #### Documentation Updated README

…ent call (open-telemetry#36482)  #### Description The `govmomi` client used in the receiver attempts to validate the connection to vcenter before the existing code sets the TLS options (other than insecure) in the client. This is a limitation of the `govmomi` wrapper, as discussed on this issue: vmware/govmomi#1200 .  #### Link to tracking issue Related issue in Grafana Alloy: grafana/alloy#193  #### Testing ~~This has not been tested, I would appreciate the assistance of any codeowner that could test.~~ See comments on the PR for test.  --------- Co-authored-by: Daniel Jaglowski <[email protected]>

…metry#36510)  #### Description adds basic hexadecimal character validation to Datadog API key on startup  #### Link to tracking issue Fixes open-telemetry#36509  #### Testing new "invalid API Key" test  #### Documentation changelog file  --------- Co-authored-by: Pablo Baeyens <[email protected]>

…tion in OTel mode (open-telemetry#36594)  #### Description In OTel mapping mode, merge *.geo.location.{lat,lon} to *.geo.location such that they are stored as [geo_point](https://www.elastic.co/guide/en/elasticsearch/reference/current/geo-point.html) in Elasticsearch.  #### Link to tracking issue Fixes open-telemetry#36565  #### Testing  #### Documentation  --------- Co-authored-by: Vishal Raj <[email protected]>

…name is available (open-telemetry#36530)  #### Description Generate url section in X-Ray segment when net.peer.name is available  #### Link to tracking issue Fixes open-telemetry#35375.  #### Testing Unit test

…nitialisation (open-telemetry#36385)  #### Description This PR adds more log output to the k8s attributes receiver to log any errors that are encountered during the kube client initialisation, to make troubleshooting and identifying this issue easier.  #### Link to tracking issue Fixes open-telemetry#35879 --------- Signed-off-by: Florian Bacher <[email protected]>

…open-telemetry#36451)  #### Description This pull request introduces a new configurable parameter `reporter_period` for the Datadog exporter’s host metadata configuration. This enhancement allows users to specify the frequency at which host metadata is sent to Datadog. The changes span multiple files and include updates to configuration, factory methods, and test cases. Enhancements to Datadog exporter: * [`.chloggen/add-configurable-reporter-period-for-host-metadata.yaml`](diffhunk://#diff-e3e3c57c49d2a921abc8470bccafabf4d632b0dc142eb3e95b3b6fac57107a11R1-R27): Added a changelog entry for the new `reporter_period` parameter. * [`exporter/datadogexporter/examples/collector.yaml`](diffhunk://#diff-766be9823b8ec8b8de17e2c6c785d9f93e13b5a7e84ff441040077ab5e726a79R452-R456): Added documentation for the new `reporter_period` parameter in the example configuration file. * [`exporter/datadogexporter/factory.go`](diffhunk://#diff-c9e9f39ffda08a2af74c0d54d37f21e14cdb95c4136cdbe238de6be2bfe31389L127-R125): Updated the factory to use the `reporter_period` from the configuration instead of a hardcoded value. Configuration updates: * [`exporter/datadogexporter/internal/hostmetadata/config.go`](diffhunk://#diff-0c9f0862d61390add366aca3e30834a1e01f16a3865ef9aca61831cad3459f53R31-R32): Added `ReporterPeriod` to the `PusherConfig` struct. * [`pkg/datadog/config/config.go`](diffhunk://#diff-747858d4c8fea28a92227df09f17ebee01df63dad04812ac5d30a392c9970b73R136-R139): Added validation for the `reporter_period` to ensure it is a positive duration and set a default value. [[1]](diffhunk://#diff-747858d4c8fea28a92227df09f17ebee01df63dad04812ac5d30a392c9970b73R136-R139) [[2]](diffhunk://#diff-747858d4c8fea28a92227df09f17ebee01df63dad04812ac5d30a392c9970b73R347) Test case updates: * `exporter/datadogexporter/factory_test.go`, `exporter/datadogexporter/logs_exporter_test.go`, `exporter/datadogexporter/metrics_exporter_test.go`, `exporter/datadogexporter/traces_exporter_test.go`: Updated test cases to include the new `reporter_period` parameter. [[1]](diffhunk://#diff-c50b6d1f06d62a58b6422f3218526437c16554faa2b7fc8eee1d32c021f00ca4R311) [[2]](diffhunk://#diff-94f5b0119d06dbcfee20cd9b99a104ef208e027c166c463321670a5197e83714R233-R235) [[3]](diffhunk://#diff-005adb1774d2a402bdd7adf3b6aa150117bf6b3c0bb634bf2c68c6b33f0ce1b5L61-R63) [[4]](diffhunk://#diff-c19daad040b7310787c0012e5c660dc18a07ba16036d0eaa31a0e18c551d0ef3R148-R150) * [`pkg/datadog/config/config_test.go`](diffhunk://#diff-d3a3c19e78bbac07597c6210b4d051f4678df2752e06c82d0f040c52207c5970R97-R105): Added test cases to validate the `reporter_period` configuration. [[1]](diffhunk://#diff-d3a3c19e78bbac07597c6210b4d051f4678df2752e06c82d0f040c52207c5970R97-R105) [[2]](diffhunk://#diff-d3a3c19e78bbac07597c6210b4d051f4678df2752e06c82d0f040c52207c5970R186-R197)  #### Link to tracking issue Fixes open-telemetry#36450  #### Testing  #### Documentation

#### Description Bump `github.com/google/cadvisor` to `v0.51.1-0.20250126012415-5b649021c2da` and `github.com/opencontainers/runc` to `v1.2.4` Removes replace in `otelcontribcol` builder-config.yaml  #### Link to tracking issue Fixes #37486  #### Testing built-in gotest and make otelcontribcol  #### Documentation none, dependency bump

jpkrohling requested a review from a team October 9, 2020 14:04

bogdandrutu reviewed Oct 12, 2020

View reviewed changes

README.md Outdated Show resolved Hide resolved

bogdandrutu changed the title ~~Added section on how to build an otelcol dist~~ Add section on how to build an otelcol dist Oct 12, 2020

jpkrohling added 2 commits October 12, 2020 17:31

Added section on how to build an otelcol dist

3166666

Signed-off-by: Juraci Paixão Kröhling <[email protected]>

s/OpenTracing/OpenTelemetry

acf4d51

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 October 12, 2020 15:31

owais reviewed Oct 12, 2020

View reviewed changes

anuraaga reviewed Oct 13, 2020

View reviewed changes

README.md Show resolved Hide resolved

owais approved these changes Oct 13, 2020

View reviewed changes

anuraaga approved these changes Oct 14, 2020

View reviewed changes

bogdandrutu merged commit a987792 into open-telemetry:master Oct 14, 2020

kisieland referenced this pull request in kisieland/opentelemetry-collector-contrib Mar 16, 2021

Use cached tools instead of uploading to the artifacts (#2475)

9b2660f

Updates #1234 Signed-off-by: Bogdan Drutu <[email protected]>

ljmsc referenced this pull request in ljmsc/opentelemetry-collector-contrib Feb 21, 2022

Move asyncronous metrics state helper out of apimetric/metrictes (#1234)

f60f51d

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Add section on how to build an otelcol dist #1234

Add section on how to build an otelcol dist #1234

jpkrohling commented Oct 9, 2020

owais Oct 12, 2020 •

edited

Loading

owais Oct 12, 2020

jpkrohling Oct 12, 2020 •

edited

Loading

Add section on how to build an otelcol dist #1234

Add section on how to build an otelcol dist #1234

Conversation

jpkrohling commented Oct 9, 2020

owais Oct 12, 2020 • edited Loading

Choose a reason for hiding this comment

owais Oct 12, 2020

Choose a reason for hiding this comment

jpkrohling Oct 12, 2020 • edited Loading

Choose a reason for hiding this comment

owais Oct 12, 2020 •

edited

Loading

jpkrohling Oct 12, 2020 •

edited

Loading