Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[pull] main from open-telemetry:main #18

Merged
merged 109 commits into from
Jun 27, 2023
Merged

Conversation

pull[bot]
Copy link

@pull pull bot commented Jun 13, 2023

See Commits and Changes for more details.


Created by pull[bot]

Can you help keep this open source service alive? 💖 Please sponsor : )

Alex Boten and others added 2 commits June 12, 2023 15:01
this was causing check-collector-module-version to not check that this module was up to the same version as the others consistently

Signed-off-by: Alex Boten <aboten@lightstep.com>
Update carbonreceiver and wavefrontreceiver to use pdata directly instead of OpenCensus
@pull pull bot added the ⤵️ pull label Jun 13, 2023
ZenoCC-Peng and others added 27 commits June 12, 2023 22:36
…23332)

Update `kafka.brokers` metric to be non-monothonic sum instead of gauge
Only store Pod data we actually use for attributes in the informer store. By default, informers store all data about K8s objects, as they're primarily intended to act as a local cache for the API Server. For our use case, most of that data is unnecessary, and it eats a significant amount of memory in larger clusters. This PR uses a transform function to remove the unnecessary data from the informer store.

I've measured the gains synthetically, and we use nearly 70% less memory per stored Pod. I haven't included the benchmark function in this PR, as it's a bit complicated and hacky, and I'm not convinced there's value in adding it to the codebase permanently.
* Start adding the status information to the metadata schema documentation

* Remove cmd from the list of possible classes

* Fix spelling mistake

Co-authored-by: Antoine Toulme <antoine@toulme.name>

* Update the value used for the development stability status

Co-authored-by: Antoine Toulme <antoine@toulme.name>

* Fix the tests after updating the example metadata file

* Document how to use mdatagen and the schema of metadata.yaml

* Add the stability levels for connectors

* Change the receiver type so the tests pass

* Update the generated documentation

* Change the syntax used for string array types so that it is valid YAML

---------

Co-authored-by: Antoine Toulme <antoine@toulme.name>
* [chore] Deprecate unnecessary fileconsumer API

* Add deprecation version and tentative removal version
---------

Signed-off-by: Alex Boten <aboten@lightstep.com>
Fixes: #20908.

---------

Co-authored-by: Yang Song <songy23@users.noreply.github.com>
Bump github.com/Azure/go-amqp from 0.19.1 to 1.0.1 in /receiver/solacereceiver
Bump github.com/ClickHouse/clickhouse-go/v2 from 2.10.0 to 2.10.1 in /exporter/clickhouseexporter
Bump github.com/DataDog/agent-payload/v5 from 5.0.84 to 5.0.88 in /exporter/datadogexporter
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /exporter/awscloudwatchlogsexporter
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /exporter/awsemfexporter
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /exporter/awsxrayexporter
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /exporter/datadogexporter
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /exporter/kafkaexporter
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /extension/observer/ecsobserver
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /internal/aws/awsutil
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /internal/aws/cwlogs
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /internal/aws/k8s
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /internal/aws/proxy
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /internal/aws/xray
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /internal/aws/xray/testdata/sampleapp
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /internal/metadataproviders
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /processor/resourcedetectionprocessor
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /receiver/awscontainerinsightreceiver
Bump github.com/aws/aws-sdk-go from 1.44.277 to 1.44.281 in /receiver/awsxrayreceiver
Bump github.com/influxdata/influxdb-observability/common from 0.5.0 to 0.5.2 in /exporter/influxdbexporter
Bump github.com/influxdata/influxdb-observability/common from 0.5.0 to 0.5.2 in /receiver/influxdbreceiver
Bump github.com/influxdata/influxdb-observability/influx2otel from 0.5.0 to 0.5.2 in /receiver/influxdbreceiver
Bump github.com/influxdata/influxdb-observability/otel2influx from 0.5.0 to 0.5.2 in /exporter/influxdbexporter
Bump github.com/leoluk/perflib_exporter from 0.2.0 to 0.2.1 in /receiver/hostmetricsreceiver
Bump github.com/signalfx/sapm-proto from 0.12.0 to 0.13.0 in /exporter/sapmexporter
Bump github.com/signalfx/sapm-proto from 0.12.0 to 0.13.0 in /receiver/sapmreceiver
Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common from 1.0.673 to 1.0.678 in /exporter/tencentcloudlogserviceexporter
Bump go.mongodb.org/atlas from 0.28.0 to 0.29.0 in /receiver/mongodbatlasreceiver
Bump go.mongodb.org/mongo-driver from 1.11.4 to 1.11.7 in /receiver/mongodbreceiver
Bump go.opentelemetry.io/build-tools/crosslink from 0.7.0 to 0.8.0 in /internal/tools
Bump go.opentelemetry.io/collector/cmd/builder from 0.78.2 to 0.79.0 in /internal/tools
Bump golang.org/x/sys from 0.8.0 to 0.9.0 in /exporter/signalfxexporter
Bump golang.org/x/sys from 0.8.0 to 0.9.0 in /pkg/stanza
Bump golang.org/x/sys from 0.8.0 to 0.9.0 in /pkg/winperfcounters
Bump golang.org/x/sys from 0.8.0 to 0.9.0 in /receiver/hostmetricsreceiver
Bump golang.org/x/sys from 0.8.0 to 0.9.0 in /receiver/windowseventlogreceiver
Bump golang.org/x/text from 0.9.0 to 0.10.0 in /cmd/configschema
Bump golang.org/x/text from 0.9.0 to 0.10.0 in /cmd/mdatagen
Bump golang.org/x/text from 0.9.0 to 0.10.0 in /internal/coreinternal
Bump golang.org/x/text from 0.9.0 to 0.10.0 in /pkg/stanza
Bump golang.org/x/text from 0.9.0 to 0.10.0 in /testbed
Bump google.golang.org/api from 0.125.0 to 0.127.0 in /exporter/f5cloudexporter
Bump google.golang.org/api from 0.125.0 to 0.127.0 in /exporter/googlecloudpubsubexporter
Bump google.golang.org/api from 0.125.0 to 0.127.0 in /receiver/googlecloudpubsubreceiver
Bump google.golang.org/api from 0.125.0 to 0.127.0 in /receiver/googlecloudspannerreceiver
* Use random address

* Bind to localhost interface
…ch (#23366)

Apply multi-metric merge at the level of the whole batch rather than within events emitted for one metric.
…fo_on_event configuration (#23250)

* DSET-3998 - export Logs resource info based on     export_resource_info_on_event configuration

* DSET-3998 - simplify

* DSET-3998 - improve docs

* Fix log exporter to set AddEvents Event timestamp (ts) field to event
observed timetamp in case LogRecord doesn't contain timestamp.

Even though ObservedTimestamp should always be present, we fall back to
current time in case it's not.

In addition to that, remove duplicate and redundant "timestamp"
attribute from the AddEvents event.

* Add additional assertions.

* Remove dummy debug logs.

* Create export-logs-resource-info-based-configuration

* address PR notes - fix changelog gen

* fix docs typo

* fix changelog file suffix

---------

Co-authored-by: Tomaz Muraus <tomazm@sentinelone.com>
Co-authored-by: Tomaz Muraus <126863902+tomaz-s1@users.noreply.github.com>
As a result of issue #23246, a few components are now unmaintained.
These need to be documented in the ALLOWLIST file.
After digging into what was causing linting time outs, it looks like golangci-lint was using up a significant amount of memory to run lint against otelcontribcol. After digging I came across this issue that mentions memory usage: golangci/golangci-lint#3565 (comment)

I've tested bumping the linters to go 1.20 and so far it looks like the avg memory is lower than it was w/ go 1.19. I've also enabled verbose logging for linting to give us a bit more info when there are issues.

---------

Signed-off-by: Alex Boten <aboten@lightstep.com>
This is a direct copy of the [supervisor example implementation](https://github.com/open-telemetry/opamp-go/tree/main/internal/examples/supervisor) in the opamp-go repository. I've made some minor changes that are largely centered around linting and making it a little less of an example. Any existing or new TODOs have a linked issue that gives some context.

**Link to tracking Issue:**

Implements #18461
Co-authored-by: Matej Gera <38492574+matej-g@users.noreply.github.com>

---------

Co-authored-by: Evan Bradley <evan-bradley@users.noreply.github.com>
Co-authored-by: Matej Gera <38492574+matej-g@users.noreply.github.com>
Updates #23266

- receiver/nsxt
- receiver/snmp
- connector/count
- extension/storage
- pkg/stanza
These components no longer have an active code owner as a result of
#23246, they're actively looking for new code owners.

Signed-off-by: Alex Boten <aboten@lightstep.com>
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/exporter/awscloudwatchlogsexporter
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/exporter/awsemfexporter
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/exporter/awsxrayexporter
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/exporter/datadogexporter
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/exporter/kafkaexporter
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/extension/observer/ecsobserver
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/internal/aws/awsutil
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/internal/aws/cwlogs
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/internal/aws/k8s
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/internal/aws/proxy
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/internal/aws/xray
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/internal/aws/xray/testdata/sampleapp
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/internal/metadataproviders
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/processor/resourcedetectionprocessor
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/receiver/awscontainerinsightreceiver
Bump github.com/aws/aws-sdk-go from 1.44.281 to 1.44.282 in
/receiver/awsxrayreceiver
…#23337)

Deprecate options which are going to be removed

**Link to tracking Issue:** #23059

---------

Signed-off-by: Dominik Rosiek <drosiek@sumologic.com>
Co-authored-by: Mikołaj Świątek <mswiatek@sumologic.com>
Co-authored-by: Alex Boten <aboten@lightstep.com>
…22739)

Closes #22737

---------

Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
**Description:**

This PR adds [exponential
histogram](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram)
support in `awsemfexporter`. The exponential histogram metrics are
exported in Embedded Metric Format (EMF) log. The Count, Sum, Max and
Min are set as Statistical Set. The mid-point values and counts of
exponential histogram buckets are translated into Values/Counts array of
EMF log entry as well.

**Testing:**

The unit test is added and covers positive, zero and negative values. 

The integration test is performed with following OTEL collector
configuration.
```
extensions:
  health_check:
receivers:
  otlp:
    protocols:
      grpc:
        endpoint: 0.0.0.0:4317
      http:
        endpoint: 0.0.0.0:4318

processors:
  batch/metrics:
    timeout: 60s

exporters:
  logging:
    verbosity: detailed
  awsemf:
    region: 'us-east-1'
    namespace: "Test"
    dimension_rollup_option: "NoDimensionRollup"

service:
  pipelines:
    metrics:
      receivers: [otlp]
      processors: [batch/metrics]
      exporters: [awsemf, logging]
  extensions: [health_check]
  telemetry:
    logs:
      level: "debug"
```
It generated EMF log for histogram metrics in following JSON format.
Notes: It doesn't cover negative values since histograms can [only
record non-negative
values](https://opentelemetry.io/docs/specs/otel/metrics/api/#histogram)
and will [drop negative
values](https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk/metrics/src/main/java/io/opentelemetry/sdk/metrics/SdkDoubleHistogram.java#L38C7-L44).

```
    "latency": {
        "Values": [
            309.4277237034415,
            323.12725941969757,
            326.64588457862067,
            344.8221530867399,
            520.3933272846809,
            531.7884573308439,
            537.579253961712,
            543.4331082335607,
            549.3507067990806,
            555.3327437881196,
            561.3799208891041,
            567.4929474313465,
            720.1774681373079,
            0
        ],
        "Counts": [
            1,
            1,
            1,
            1,
            1,
            3,
            4,
            2,
            2,
            3,
            1,
            1,
            1,
            22
        ],
        "Max": 720,
        "Min": 0,
        "Count": 44,
        "Sum": 11265
    }
```
cc @jpkrohling @pavankrish123

Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
**Description:** 
There is currently no way to get the
[Flags](https://github.com/open-telemetry/opentelemetry-collector/blob/main/pdata/internal/data/protogen/logs/v1/logs.pb.go#L396)
field from plog.LogRecord into Loki.
Added Flags field to lokiEntry in this PR

**Link to tracking Issue:**
#21650

**Testing:** Added unit tests
Fixes #20284 

This introduces initial support for retrieving rows from SQL databases
into logs.

This PR aims to provide an initial, not feature rich, but production
ready implementation. The following features are available:

- Use `body_column` to select the column to use to fill the Body field
of the created log
- Use `tracking_start_value` and `tracking_column` properties to track
rows that were already ingested
- Use `storage` property to persist the tracking value across collector
restarts

In this state and marked as "development" stability, the component can
be used for experimentation and to guide future development.

There are definitely more things that need to be implemented for this
component to be considered "alpha" quality - like filling in other [log
fields](https://github.com/open-telemetry/opentelemetry-specification/blob/v1.21.0/specification/logs/data-model.md#log-and-event-record-definition)
like Timestamp, ObservedTimestamp and others. I would like to add them
in subsequent pull requests, as this pull request is already way too
big.

---------

Co-authored-by: Dominika Molenda <dmolenda@sumologic.com>
Co-authored-by: Dominika Molenda <73838995+dmolenda-sumo@users.noreply.github.com>
Co-authored-by: Katarzyna Kujawa <73836361+kkujawa-sumo@users.noreply.github.com>
Co-authored-by: Katarzyna Kujawa <kkujawa@sumologic.com>
Adds an e2e test for k8sclusterreceiver with a golden metrics file.
Updating CODEOWNERS entries for GCP exporters
- Updated github.com/signalfx/sapm-proto to v0.13.0
- Added "compression" config setting to sapm exporter
- Added tests to verify various compression settings for sapm receiver
and exporter.
opentelemetrybot and others added 29 commits June 22, 2023 15:26
…nt (#23640)

**Description:** updated dataset-go library, send more details in
user-agent
For more details see
https://github.com/scalyr/dataset-go/releases/tag/v0.0.9

**Link to tracking Issue:**
#20660
/ DSET-3468

**Testing:** verified via unit tests and also e2e with DataSet
environment

**Documentation:** see
https://github.com/scalyr/dataset-go/blob/fbaead7856a9c5669262564dfa4a13aa14a0775d/examples/readme/main.go#L81
Following the same approach of
#20903

I am adding the scope whenever the metric is copied. We could also add
the _scope_ at creation time, however, it would change the signature of
several functions having already too many parameters.

**Link to tracking Issue:** <Issue number if applicable>
Fix #23563

**Testing:** 
Added a test to cover the new use case
…de-references (#23644)

Fixes possible panics from unchecked de-references in
metrics helper in `awsecscontainermetrics` receiver.

**Link to tracking Issue:**
aws-observability/aws-otel-collector#2110

**Testing:** Added unit tests for these de-references

**Documentation:** n//a
**Description:** 
Fixed a bug in which the Vcenter receiver was incorrectly emmiting the
disk_state: used datapoint twice under the vcenter.datastore.disk.usage
metric instead of a
disk_state: used
disk_state: available

**Documentation:** <Describe the documentation added.>
**Description:** <Describe what has changed.>
fixed an issue where postgresql receiver was emitting the same attribute
value "toast_hit" twice under postgresql.blocks_read metric.

**Link to tracking Issue:** <Issue number if applicable>

**Testing:** <Describe what testing was performed and which tests were
added.>

**Documentation:** <Describe the documentation added.>
… hosts that use cgroups v2 (#22706)

**Description:**
This PR updates the documentation of all the metrics that are available
only on cgroups v1 or cgroups v2.

It PR also adds two metrics that are only available when the host is
using cgroups v2:
 * `container.memory.anon`
 * `container.memory.file`

Both are documented here:
https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files

I enabled the metric `container.memory.file` by default (causing a
breaking change) because it is a metric that was already scraped for
cgroups v1, contained in the metric `container.memory.total_cache`.

```yaml
  container.memory.total_cache:
    enabled: true
    description: "Total amount of memory used by the processes of this cgroup (and descendants) that can be associated with a block on a block device. Also accounts for memory used by tmpfs (Only available with cgroups v1)."

  container.memory.file:
    enabled: true
    description: "Amount of memory used to cache filesystem data, including tmpfs and shared memory (Only available with cgroups v2)."
```

Let me know your thoughts about this breaking change.

**Link to tracking Issue:** #21097

**Testing:**
The refactor done during PR #21110 had mocks ready to test these new
metrics. There is no need to add more tests.

**Documentation:**
To see which metrics are available in Docker:
* v1:
https://github.com/moby/moby/blob/7103efac9d737e8b202126e8c8e2227805e70771/daemon/stats_unix.go#L86
* v2:
https://github.com/moby/moby/blob/7103efac9d737e8b202126e8c8e2227805e70771/daemon/stats_unix.go#L195

Kernel cgroup documentation:
 * v1: https://docs.kernel.org/admin-guide/cgroup-v1/memory.html
* v2:
https://docs.kernel.org/admin-guide/cgroup-v2.html#memory-interface-files
Temporarily disable the integration test to unblock the CI.

Updates
#23670
…or in resource processor (#23253)

**Description:** Adding resource_attributes option to every detector in
resource detection processor
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->

**Link to tracking Issue:**
[21482](#21482)

**Testing:** Unit test for `resource_attribute` config, adjusting
current unit tests to the new implementation

**Documentation:** Updated README.md

---------

Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
…orrect fingerprint update (#23183)

The logic for determining when to update a fingerprint previously failed
to account for the case where the buffer size is smaller than the
fingerprint. This allows the fingerprint to be truncated in some cases.

This PR rewrites the logic to explicitly handle each expected case, with
optimization for handling the most common cases first.
**Description:** Updates GCP libraries to v0.39.2 and 1.15.2

**Documentation:** updated readmes for new experimental WAL fields
Metric unit is required, see:
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/cmd/mdatagen/metadata-schema.yaml#L72-L73.

This PR adds the unit to metrics where this is missing:
- postgresql.bgwriter.maxwritten
- postgresql.table.count
…ts (#23636)

This PR adds a `parent` field to the `metadata.yaml`. This is used in
subcomponents, and the field contains the type of their parent
component.

---------

Co-authored-by: Dmitrii Anoshin <anoshindx@gmail.com>
**Description:** <Describe what has changed.>
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
Add `container.image.id` and `container.command_line` as optional
resource attributes, disabled by default.



**Link to tracking Issue:** <Issue number if applicable>

Tracking issue
#21092

**Testing:** <Describe what testing was performed and which tests were
added.>

Until this point, all resource attributes have been enabled by default,
resulting in the coupling of the
[test](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/7bf5d66fae6c1c5360ec2875948f2c2adab6c44f/receiver/dockerstatsreceiver/receiver_test.go#L191)
to the default configuration. In order to test the current
implementation with the new resource attributes enabled & disabled, a
minor refactoring was required in the `TestScrapeV2` test, allowing to
pass different configurations for each test.

Refer to the following commit 508dbee
to check the refactor in the test.

**Documentation:** <Describe the documentation added.>

New resource attributes documentation was generated by `mdatagen`.
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Update | Change |
|---|---|---|
|
[otel/opentelemetry-collector-contrib](https://togithub.com/open-telemetry/opentelemetry-collector-releases)
| minor | `0.79.0` -> `0.80.0` |
| prom/prometheus | minor | `v2.44.0` -> `v2.45.0` |

---

### Release Notes

<details>
<summary>open-telemetry/opentelemetry-collector-releases
(otel/opentelemetry-collector-contrib)</summary>

###
[`v0.80.0`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.80.0)

[Compare
Source](https://togithub.com/open-telemetry/opentelemetry-collector-releases/compare/v0.79.0...v0.80.0)

#### Changelog

-
[`3fe11dc`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/3fe11dc)
Update versions to v0.80.0
([#&#8203;362](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/362))
-
[`f82587a`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/f82587a)
Add warning about git tags
([#&#8203;359](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/359))
-
[`3af8267`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/3af8267)
Bump github.com/goreleaser/nfpm/v2 from 2.29.0 to 2.30.1
([#&#8203;358](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/358))
-
[`cb3c890`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/cb3c890)
Add all missing components to contrib distribution manifest
([#&#8203;356](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/356))
-
[`60a7e46`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/60a7e46)
Add missing components to contrib distribution
([#&#8203;354](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/354))
-
[`73fd3ae`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/73fd3ae)
Add haproxyreceiver to the contrib distribution
([#&#8203;355](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/355))
-
[`98597be`](https://togithub.com/open-telemetry/opentelemetry-collector-releases/commit/98597be)
\[chore] bump go version
([#&#8203;352](https://togithub.com/open-telemetry/opentelemetry-collector-releases/issues/352))

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any
time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

👻 **Immortal**: This PR will be recreated if closed unmerged. Get
[config help](https://togithub.com/renovatebot/renovate/discussions) if
that's undesired.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS4xNDEuMyIsInVwZGF0ZWRJblZlciI6IjM1LjE0MS4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
#23779)

We've documented the intended approach to our default targets
[here](https://github.com/open-telemetry/opentelemetry-collector/blob/5852d09fb7b519e18610b99fc5a9da8cddbbf790/CONTRIBUTING.md?plain=1#L589-L591).
In `Makefile.Common`, the default target is `common`.

This adds the `test` target as a prerequisite.
…ause incorrect fingerprint update" (#23781)

Reverts #23183

Several rotation test failures have been observed since this was merged.
([example](https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/5391301380/jobs/9787962306?pr=23780#step:8:75))

I do not immediately see the problem so I think this needs to be
reverted for now.
**Description:**
This PR adds validation to mdatagen. It ensures that all required fields
are present, and validates their content.

The validation lies mostly in `validate.go` (and for tests
`validate_test.go`), however validation that needs to be done via
decoding lies in `loader.go` + `metricdata.go` (and for tests
`loader_test.go`).

**Link to tracking Issue:**
#23424.
… on log rotation (#23609)

Added example on how to use filelog receiver with log files. Also, added
some details to the configuration descriptions and added anchor to some
sections in the document. Additionally, added information on log
rotation.

- Added example on how to use filelog receiver with log files
- Also, added some details to the configuration descriptions
- Added information on log rotation
- Added anchors to some sections
Bump Wandalen/wretry.action from 1.0.36 to 1.3.0
Bump
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp
from 1.15.0 to 1.15.2 in /exporter/datadogexporter
Bump
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp
from 1.15.0 to 1.15.2 in /processor/resourcedetectionprocessor
Bump github.com/SAP/go-hdb from 1.3.8 to 1.3.9 in
/receiver/saphanareceiver
Bump github.com/SAP/go-hdb from 1.3.8 to 1.3.9 in
/receiver/sqlqueryreceiver
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/exporter/awscloudwatchlogsexporter
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/exporter/awsemfexporter
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/exporter/awsxrayexporter
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/exporter/datadogexporter
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/exporter/kafkaexporter
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/extension/observer/ecsobserver
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/internal/aws/awsutil
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/internal/aws/cwlogs
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/internal/aws/k8s
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/internal/aws/proxy
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/internal/aws/xray
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/internal/aws/xray/testdata/sampleapp
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/internal/metadataproviders
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/processor/resourcedetectionprocessor
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/receiver/awscontainerinsightreceiver
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/receiver/awsecscontainermetricsreceiver
Bump github.com/aws/aws-sdk-go from 1.44.287 to 1.44.290 in
/receiver/awsxrayreceiver
Bump github.com/golangci/golangci-lint from 1.53.2 to 1.53.3 in
/internal/tools
Bump github.com/google/cadvisor from 0.47.1 to 0.47.2 in
/receiver/awscontainerinsightreceiver
Bump github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common
from 1.0.685 to 1.0.687 in /exporter/tencentcloudlogserviceexporter
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /extension/observer/dockerobserver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /internal/coreinternal
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/aerospikereceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/apachereceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/dockerstatsreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/elasticsearchreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/flinkmetricsreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/jmxreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/kafkametricsreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/memcachedreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/mongodbreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/mysqlreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/nginxreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/postgresqlreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/rabbitmqreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/redisreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/riakreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/sqlqueryreceiver
Bump github.com/testcontainers/testcontainers-go from 0.20.1 to 0.21.0
in /receiver/zookeeperreceiver
Bump go.mongodb.org/mongo-driver from 1.11.7 to 1.12.0 in
/receiver/mongodbreceiver
Bump go.opentelemetry.io/collector/cmd/builder from 0.79.0 to 0.80.0 in
/internal/tools
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in /cmd/telemetrygen
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/examples/demo/client
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/examples/demo/server
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/exporter/coralogixexporter
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/exporter/googlecloudpubsubexporter
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/exporter/jaegerexporter
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/exporter/opencensusexporter
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/exporter/skywalkingexporter
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/extension/asapauthextension
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/extension/basicauthextension
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/extension/bearertokenauthextension
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/extension/headerssetterextension
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/extension/jaegerremotesampling
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/extension/oauth2clientauthextension
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/extension/sigv4authextension
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/processor/routingprocessor
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/processor/spanmetricsprocessor
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/receiver/googlecloudpubsubreceiver
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/receiver/googlecloudspannerreceiver
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/receiver/jaegerreceiver
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/receiver/opencensusreceiver
Bump google.golang.org/grpc from 1.56.0 to 1.56.1 in
/receiver/skywalkingreceiver
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/exporter/datadogexporter
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/exporter/logzioexporter
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/exporter/tencentcloudlogserviceexporter
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/pkg/translator/opencensus
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/receiver/collectdreceiver
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/receiver/opencensusreceiver
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/receiver/prometheusreceiver
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/receiver/skywalkingreceiver
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/receiver/solacereceiver
Bump google.golang.org/protobuf from 1.30.0 to 1.31.0 in
/receiver/zipkinreceiver

---------

Signed-off-by: Alex Boten <aboten@lightstep.com>
Co-authored-by: Alex Boten <aboten@lightstep.com>
[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Type | Update | Change |
|---|---|---|---|
| [Wandalen/wretry.action](https://togithub.com/Wandalen/wretry.action)
| action | minor | `v1.0.36` -> `v1.3.0` |

---

### Release Notes

<details>
<summary>Wandalen/wretry.action (Wandalen/wretry.action)</summary>

###
[`v1.3.0`](https://togithub.com/Wandalen/wretry.action/compare/v1.2.0...v1.3.0)

[Compare
Source](https://togithub.com/Wandalen/wretry.action/compare/v1.2.0...v1.3.0)

###
[`v1.2.0`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.42...v1.2.0)

[Compare
Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.42...v1.2.0)

###
[`v1.0.42`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.41...v1.0.42)

[Compare
Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.41...v1.0.42)

###
[`v1.0.41`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.40...v1.0.41)

[Compare
Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.40...v1.0.41)

###
[`v1.0.40`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.39...v1.0.40)

[Compare
Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.39...v1.0.40)

###
[`v1.0.39`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.38...v1.0.39)

[Compare
Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.38...v1.0.39)

###
[`v1.0.38`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.37...v1.0.38)

[Compare
Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.37...v1.0.38)

###
[`v1.0.37`](https://togithub.com/Wandalen/wretry.action/compare/v1.0.36...v1.0.37)

[Compare
Source](https://togithub.com/Wandalen/wretry.action/compare/v1.0.36...v1.0.37)

</details>

---

### Configuration

📅 **Schedule**: Branch creation - "on tuesday" (UTC), Automerge - At any
time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/open-telemetry/opentelemetry-collector-contrib).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS4xNDEuMyIsInVwZGF0ZWRJblZlciI6IjM1LjE0MS4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiJ9-->
It took me several readings of the docs to understand what is happening
in the config. I tried to clarify what an association is and how they
are specified.

I've removed the line "All rules are going to be executed, and
combination of result is going to be a pod metadata cache key." because
it actually doesn't matter from a user perspective. It looks like an
internal detail and is confusing in this section of the docs.

Signed-off-by: Gotham <gouthamve@gmail.com>
…19160)

In this PR, support for Start and Stop Timestamp to be picked up from
the metrics stored in the rows is added. This will allow SQL queries to
be more expressive and allows users to define the period of aggregation
which is not only dependent on the default system time set upon
processing.

**Link to tracking Issue:** 
#18925 
#14146

---------

Co-authored-by: Juraci Paixão Kröhling <juraci.github@kroehling.de>
…23795)

**Description:**
Add parent information to pod and container metadata.

**Link to tracking Issue:**
Fixes #23793
@cparkins cparkins merged commit 7a1061d into AmadeusITGroup:main Jun 27, 2023
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet