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

Add Function to convert Exponential Histograms #23659

Closed
wants to merge 3,520 commits into from
Closed

Add Function to convert Exponential Histograms #23659

wants to merge 3,520 commits into from

Conversation

daidokoro
Copy link

Add convert_exponential_hist_to_bucketed_hist to transform processor.

Requires feature gate flag when running otel

--feature-gates processor.transform.ConvertExponentialHistogramToBucketedHistogram

For eg.

processors:
  transform:
    error_mode: propagate
    metric_statements:
    - context: metric
      statements:
        - convert_exponential_hist_to_bucketed_hist([0.0, 10.0, 100.0, 1000.0])

atoulme and others added 30 commits May 30, 2024 08:02
…umn (open-telemetry#33283)

**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.-->

Remove the unnecessary order by clause causing undefined reference
error.
This order by clause was introduced in [this
commit](open-telemetry@bbcb16c).
In [the next
commit](open-telemetry@5437618),
the author made a change to the metrics model, but I think he forgot to
remove the order by clause at that time.

I think it could be changed to order by another column, but I didn't
really feel the need to keep it sorted, so I removed it.


**Link to tracking Issue:**
open-telemetry#33271

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

Tested working as expected with [email protected] which is reported version
in the issue.

Also it can be tested as sql.
```sql
-- before
mysql> SELECT TABLE_SCHEMA, TABLE_NAME, TABLE_ROWS, AVG_ROW_LENGTH, DATA_LENGTH, INDEX_LENGTH FROM information_schema.TABLES WHERE TABLE_SCHEMA NOT in ('information_schema', 'sys') ORDER BY TABLE_LENGTH DESC;
ERROR 1054 (42S22): Unknown column 'TABLE_LENGTH' in 'order clause'

-- after
mysql> SELECT TABLE_SCHEMA, TABLE_NAME, TABLE_ROWS, AVG_ROW_LENGTH, DATA_LENGTH, INDEX_LENGTH FROM information_schema.TABLES WHERE TABLE_SCHEMA NOT in ('information_schema', 'sys');
+--------------------+------------------------------------------------------+------------+----------------+-------------+--------------+
| TABLE_SCHEMA       | TABLE_NAME                                           | TABLE_ROWS | AVG_ROW_LENGTH | DATA_LENGTH | INDEX_LENGTH |
+--------------------+------------------------------------------------------+------------+----------------+-------------+--------------+
| mysql              | innodb_table_stats                                   |          2 |           8192 |       16384 |            0 |
| mysql              | innodb_index_stats                                   |          6 |           2730 |       16384 |            0 |
| performance_schema | cond_instances                                       |        256 |              0 |           0 |            0 |
| performance_schema | error_log                                            |          9 |              0 |           0 |            0 |
| performance_schema | events_waits_current                                 |       1536 |              0 |           0 |            0 |
(snip)
```

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

---------

Co-authored-by: Daniel Jaglowski <[email protected]>
Co-authored-by: Curtis Robert <[email protected]>
- **[chore] multimod update stable modules**
- **[chore] multimod update beta modules**
- **[chore] update core**

Ran "make generate" as well.

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

---------

Signed-off-by: Juraci Paixão Kröhling <[email protected]>
…try#33225)

**Description:** <Describe what has changed.>
Using the DB span example below, X-Ray exporter failed to generate the
expected DB call subsegment names because it could not parse JDBC
connection strings that start with the `jdbc:` prefix.
```
Span #1
    Trace ID       : 663a0b68a5e3849c09c07f914b3df738
    Parent ID      : 1052e2a4a2516884
    ID             : 374de78b552e23c2
    Name           : orders@no-appsignals-mysql-1.cnkqok6c8mo1.eu-west-1.rds.amazonaws.com
    Kind           : Client
    Start time     : 2024-05-07 11:07:20.62 +0000 UTC
    End time       : 2024-05-07 11:07:20.624 +0000 UTC
    Status code    : Unset
    Status message :
Attributes:
     -> db.connection_string: Str(jdbc:mysql://no-appsignals-mysql-1.cnkqok6c8mo1.eu-west-1.rds.amazonaws.com:3306)
     -> db.name: Str(orders)
     -> db.system: Str(MySQL)
     -> db.user: Str([email protected])
```

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

**Testing:** <Describe what testing was performed and which tests were
added.>
local tests
…open-telemetry#33313)

**Description:**
Several users have tried to use this extension as the README makes it
appear as though it's ready for use. I've updated
the README to include a warning and a note that the README is forward
looking. I think it's useful to describe the functionality that the
extension will provide when open-telemetry#30673 has been fully decomposed and
integrated.

cc: @diranged @twistypigeon

Let me know if stronger wording is needed.

**Link to tracking Issue:** open-telemetry#33301 

**Documentation:** README update
… and metrics exporter (open-telemetry#33291)

`TraceAgent` is only called in the traces exporter and
`consumeStatsPayload` is only called in the metrics exporter, so I think
using the same `wg` field was causing conflicts with both exporters in
use at the same time. This PR splits `wg` into separate fields for each
use case.

This PR also removes `wg.Wait` on the logs exporter since that wasn't
applicable in the first place.
**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.-->

- Adds the shutdown scraper method. The implementation cancels the
`containerEventLoop` go routine. Similar to the dockerstats:
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/dockerstatsreceiver/receiver.go#L76
- Moves the configuration validation to the start method, in alignment
with the dockerstats receiver:
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/dockerstatsreceiver/receiver.go#L55

**Link to tracking Issue:** Related issue
open-telemetry#29994

**Testing:** <Describe what testing was performed and which tests were
added.>
Use scraper instead of metrics receiver interface.

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

---------

Co-authored-by: Curtis Robert <[email protected]>
…ic (open-telemetry#32295)

**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.-->

At the moment. We calculate the `k8s.container.cpu_limit_utilization` as
[a ratio of the container's
limits](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/kubeletstatsreceiver/documentation.md#k8scontainercpu_limit_utilization)
at
https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/867d6700c31446172e6998e602c55fbf7351831f/receiver/kubeletstatsreceiver/internal/kubelet/cpu.go#L30.

Similarly we can calculate the cpu utilization as ratio of the whole
node's allocatable cpu, if we divide by the total number of node's
cores.

We can retrieve this information from the Node's `Status.Capacity`, for
example:

```console
$ k get nodes kind-control-plane -ojsonpath='{.status.capacity}'
{"cpu":"8","ephemeral-storage":"485961008Ki","hugepages-1Gi":"0","hugepages-2Mi":"0","memory":"32564732Ki","pods":"110"}
```




## Performance concerns

In order to get the Node's capacity we need an API call to the k8s API
in order to get the Node object.
Something to consider here is the performance impact that this extra API
call would bring. We can always choose to have this metric as disabled
by default and clearly specify in the docs that this metric comes with
an extra API call to get the Node of the Pods.

The good thing is that `kubeletstats` receiver target's only one node so
I believe it's a safe assumption to only fetch the current node because
all the observed Pods will belong to the one single local node. Correct
me if I miss anything here.

In addition, instead of performing the API call explicitly on every
single `scrape` we can use an informer instead and leverage its cache. I
can change this patch to this direction if we agree on this.

Would love to hear other's opinions on this. 

## Todos

✅ 1) Apply this change behind a feature gate as it was indicated at
open-telemetry#27885 (comment)
✅  2) Use an Informer instead of direct API calls.

**Link to tracking Issue:** <Issue number if applicable>
ref:
open-telemetry#27885

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

I experimented with this approach and the results look correct. In order
to verify this I deployed a stress Pod on my machine to consume a target
cpu of 4 cores:

```yaml
apiVersion: v1
kind: Pod
metadata:
  name: cpu-stress
spec:
  containers:
  - name: cpu-stress
    image: polinux/stress
    command: ["stress"]
    args: ["-c", "4"]
```

And then the collected `container.cpu.utilization` for that Pod's
container was at `0,5` as exepcted, based that my machine-node comes
with 8 cores in total:


![cpu-stress](https://github.com/open-telemetry/opentelemetry-collector-contrib/assets/11754898/3abe4a0d-6c99-4b4e-a704-da5789dde01b)

Unit test is also included.

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

Added:
https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/32295/files#diff-8ad3b506fb1132c961e8da99b677abd31f0108e3f9ed6999dd96ad3297b51e08

---------

Signed-off-by: ChrsMark <[email protected]>
…placeUnsafeCharacters` (open-telemetry#33236)

**Description:**

Removes the feature flag according to schedule.

**Link to tracking Issue:**

-
open-telemetry#3148

**Testing:**

No changes.

**Documentation:**

Replaced the description of the feature gate with the description of the
feature.
…metry#33273)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[google.golang.org/api](https://togithub.com/googleapis/google-api-go-client)
| `v0.181.0` -> `v0.182.0` |
[![age](https://developer.mend.io/api/mc/badges/age/go/google.golang.org%2fapi/v0.182.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/google.golang.org%2fapi/v0.182.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/google.golang.org%2fapi/v0.181.0/v0.182.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/google.golang.org%2fapi/v0.181.0/v0.182.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>googleapis/google-api-go-client
(google.golang.org/api)</summary>

###
[`v0.182.0`](https://togithub.com/googleapis/google-api-go-client/releases/tag/v0.182.0)

[Compare
Source](https://togithub.com/googleapis/google-api-go-client/compare/v0.181.0...v0.182.0)

##### Features

- **all:** Auto-regenerate discovery clients
([#&#8203;2590](https://togithub.com/googleapis/google-api-go-client/issues/2590))
([e95bd57](https://togithub.com/googleapis/google-api-go-client/commit/e95bd57350fd494a12fe94b167ab27365ef81593))
- **all:** Auto-regenerate discovery clients
([#&#8203;2594](https://togithub.com/googleapis/google-api-go-client/issues/2594))
([21295a5](https://togithub.com/googleapis/google-api-go-client/commit/21295a5acbbea62c8f1efe8c785161b965b4c95d))
- **all:** Auto-regenerate discovery clients
([#&#8203;2595](https://togithub.com/googleapis/google-api-go-client/issues/2595))
([07e7104](https://togithub.com/googleapis/google-api-go-client/commit/07e71041f297a16404eb756ca8397ab1a7681236))
- **all:** Auto-regenerate discovery clients
([#&#8203;2597](https://togithub.com/googleapis/google-api-go-client/issues/2597))
([7d46b4d](https://togithub.com/googleapis/google-api-go-client/commit/7d46b4d9f1654a792272ad67647c598ee46f4a77))
- **all:** Auto-regenerate discovery clients
([#&#8203;2599](https://togithub.com/googleapis/google-api-go-client/issues/2599))
([677f53d](https://togithub.com/googleapis/google-api-go-client/commit/677f53d0fc95f93b6586eb828c8ebd902d8a8b52))
- **all:** Auto-regenerate discovery clients
([#&#8203;2600](https://togithub.com/googleapis/google-api-go-client/issues/2600))
([2e7cc39](https://togithub.com/googleapis/google-api-go-client/commit/2e7cc399531ce02210c3cd68748035a1aef59be0))
- **all:** Auto-regenerate discovery clients
([#&#8203;2602](https://togithub.com/googleapis/google-api-go-client/issues/2602))
([a86c4b6](https://togithub.com/googleapis/google-api-go-client/commit/a86c4b6bbded4c73369be9d6af5716f87d064448))
- **all:** Auto-regenerate discovery clients
([#&#8203;2603](https://togithub.com/googleapis/google-api-go-client/issues/2603))
([ece7727](https://togithub.com/googleapis/google-api-go-client/commit/ece77271d2e524bcbcd194046094f3940320a51e))
- **all:** Auto-regenerate discovery clients
([#&#8203;2604](https://togithub.com/googleapis/google-api-go-client/issues/2604))
([f474c8f](https://togithub.com/googleapis/google-api-go-client/commit/f474c8ff7d640ca05bf7b72e4d4572990085aa3c))
- **all:** Auto-regenerate discovery clients
([#&#8203;2606](https://togithub.com/googleapis/google-api-go-client/issues/2606))
([ceaeabf](https://togithub.com/googleapis/google-api-go-client/commit/ceaeabf4cecd0f714fd21d9898a78cf16870050a))
- **all:** Auto-regenerate discovery clients
([#&#8203;2608](https://togithub.com/googleapis/google-api-go-client/issues/2608))
([0e58f74](https://togithub.com/googleapis/google-api-go-client/commit/0e58f747c6eabcdfceee43492e42a5030667de1c))
- **all:** Auto-regenerate discovery clients
([#&#8203;2609](https://togithub.com/googleapis/google-api-go-client/issues/2609))
([c4c51ce](https://togithub.com/googleapis/google-api-go-client/commit/c4c51ce9c298333e39e60aa1258aa7933659b52b))

</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:eyJjcmVhdGVkSW5WZXIiOiIzNy4zNzcuOCIsInVwZGF0ZWRJblZlciI6IjM3LjM3Ny44IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: opentelemetrybot <[email protected]>
Co-authored-by: Alex Boten <[email protected]>
**Description:** Documentation only change

**Documentation:** Small change to fix bad reference docs for splunk
due to undefined map iteration order, this test was flaky

Fixes open-telemetry#33094

Co-authored-by: Juraci Paixão Kröhling <[email protected]>
Co-authored-by: Alex Boten <[email protected]>
)

This is a first step towards a [Flatten/Unflatten
workaround](open-telemetry#32080)
for OTTL's data corruption issue, specifically this would support
Unflatten. The workaround was discussed in a recent collector SIG and it
sounded like it would be acceptable if available behind a feature gate
and only for the transform processor. If this is accepted I'll work on a
Flatten utility next, then integrate them into the tranform processor to
prove end-to-end. Finally, I'll implement similar features for metrics
and traces.

This PR adds an internal utility package which simplifies grouping logs
by resource and scope. I'm proposing this initially in
`internal/pdatautil` but the functionality could eventually be merged
into `pkg/pdatautil` if we find it useful elsewhere.
…pen-telemetry#33240)

This PR configures internal metrics for the prometheus remote write
exporter to use mdatagen. It additionally uses the utility functions to
test emitted internal telemetry instead of using mock telemetry

Follows
open-telemetry#33239

---------

Signed-off-by: Alex Boten <[email protected]>
…ry#33237)

**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.-->
This PR adds the logging part from
open-telemetry#31256.
With this addition every time that is identified that file is rotated
either by move/create or copy/truncate, proper logging takes place. 

**Link to tracking Issue:** <Issue number if applicable>
open-telemetry#31256

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


### How to test this manually

Using the following config:

```yaml
receivers:
  filelog:
    start_at: beginning
    poll_interval: 5s
    include:
    - /var/log/busybox/monitoring/stable*.log

exporters:
  debug:
    verbosity: detailed

service:
  telemetry:
    logs:
      level: info
  pipelines:
    logs:
      receivers: [filelog]
      exporters: [debug]
      processors: []
```

#### Testing truncate (out of pattern)

```console
echo "$(date '+%FT%H:%M:%S.%NZ') some line1" >> /var/log/busybox/monitoring/stable_trunc.log && 
echo "$(date '+%FT%H:%M:%S.%NZ') some line2" >> /var/log/busybox/monitoring/stable_trunc.log &&  
echo "$(date '+%FT%H:%M:%S.%NZ') some line3" >> /var/log/busybox/monitoring/stable_trunc.log && 
sleep 6 && 
cp /var/log/busybox/monitoring/stable_trunc.log /var/log/busybox/monitoring/stable_trunc.log.1 && 
: > /var/log/busybox/monitoring/stable_trunc.log && 
echo "$(date '+%FT%H:%M:%S.%NZ') some line new0" >> /var/log/busybox/monitoring/stable_trunc.log
```

#### Testing truncate (in pattern)

```console
echo "$(date '+%FT%H:%M:%S.%NZ') some line1" >> /var/log/busybox/monitoring/stable_trunc.log &&
echo "$(date '+%FT%H:%M:%S.%NZ') some line2" >> /var/log/busybox/monitoring/stable_trunc.log && 
echo "$(date '+%FT%H:%M:%S.%NZ') some line3" >> /var/log/busybox/monitoring/stable_trunc.log &&
sleep 6 &&
cp /var/log/busybox/monitoring/stable_trunc.log /var/log/busybox/monitoring/stable_trunc_1.log &&
: > /var/log/busybox/monitoring/stable_trunc.log &&
echo "$(date '+%FT%H:%M:%S.%NZ') some line new1" >> /var/log/busybox/monitoring/stable_trunc.log
```

#### Testing move/create  (out of pattern)

```console
echo "$(date '+%FT%H:%M:%S.%NZ') some line1" >> /var/log/busybox/monitoring/stable_trunc.log &&
echo "$(date '+%FT%H:%M:%S.%NZ') some line2" >> /var/log/busybox/monitoring/stable_trunc.log && 
echo "$(date '+%FT%H:%M:%S.%NZ') some line3" >> /var/log/busybox/monitoring/stable_trunc.log &&
sleep 6 &&
mv /var/log/busybox/monitoring/stable_trunc.log /var/log/busybox/monitoring/stable_trunc.log.1 &&
echo "$(date '+%FT%H:%M:%S.%NZ') some line new0" >> /var/log/busybox/monitoring/stable_trunc.log
```

#### Testing move/create (in pattern)

```console
echo "$(date '+%FT%H:%M:%S.%NZ') some line1" >> /var/log/busybox/monitoring/stable_trunc.log &&
echo "$(date '+%FT%H:%M:%S.%NZ') some line2" >> /var/log/busybox/monitoring/stable_trunc.log && 
echo "$(date '+%FT%H:%M:%S.%NZ') some line3" >> /var/log/busybox/monitoring/stable_trunc.log &&
sleep 6 &&
mv /var/log/busybox/monitoring/stable_trunc.log /var/log/busybox/monitoring/stable_trunc_1.log &&
echo "$(date '+%FT%H:%M:%S.%NZ') some line new0" >> /var/log/busybox/monitoring/stable_trunc.log
```

**Documentation:** <Describe the documentation added.>
Add some extra notes in the `design.md`

---------

Signed-off-by: ChrsMark <[email protected]>
…etry#33320)

This PR adds support for passing a traceID and spanID to be used as
exemplars on the generated data points. This was verified with an e2e
test using OTel Collector and the debug exporter in detailed verbosity,
resulting in this:

```
2024-05-31T11:41:51.378+0200    info    ResourceMetrics #0
Resource SchemaURL: https://opentelemetry.io/schemas/1.13.0
ScopeMetrics #0
ScopeMetrics SchemaURL: 
InstrumentationScope  
Metric #0
Descriptor:
     -> Name: gen
     -> Description: 
     -> Unit: 
     -> DataType: Gauge
NumberDataPoints #0
StartTimestamp: 1970-01-01 00:00:00 +0000 UTC
Timestamp: 2024-05-31 09:41:51.374564535 +0000 UTC
Value: 0
Exemplars:
Exemplar #0
     -> Trace ID: ae87dadd90e9935a4bc9660628efd569
     -> Span ID: 5828fa4960140870
     -> Timestamp: 2024-05-31 09:41:51.374432029 +0000 UTC
     -> Value: 1
```

Given that I needed to do the validation of the traceID/spanID on the
metrics config as well, I refactored the current validation done in the
logging part of the command so that it's now part of the common package.

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

---------

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

---------

Signed-off-by: Alex Boten <[email protected]>
Co-authored-by: Dan Jaglowski <[email protected]>
**Description:**
Adds integration test for the rabbitmq exporter. It tests the happy path
and the logic for creating a new connection when the current one becomes
unhealthy
…metry#32282)

**Description:**

Adds `create_schema` boolean to config. This flag will disable the
automatic creation of the database and tables so that this can be
manually managed by the user.

**Link to tracking Issue:**

open-telemetry#29443
(related)

**Testing:**
Ran integration tests, and added test for verifying undefined + true +
false in for the value in the config.

**Documentation:**

Added config option to README along with new "schema management" section
that contains some recommendations for production deployments as well as
requirements for maintaining compatibility.

Also added `examples/default_ddl/` which contains all of the default DDL
that the exporter runs. These are to be used as a starting point for
users managing their own schema.

---------

Co-authored-by: Pablo Baeyens <[email protected]>
…telemetry#33321)

**Description:** <Describe what has changed.>

Fixing a bug - the calculation when converting pdata timestamps to
`time` is off in both the `syslog` and `tcpudp` datasenders.
Seconds are calculated correctly by dividing the timestamp by `10^9`,
but in nanosecond calculation the remainder of `timestamp/10^8` is used,
effectively always setting the first decimal in the resulting timestamp
to `0`.

Discovered this while writing some tests against the syslog receiver and
receiving unexpected data in the log body, after identifying the issue a
quick search revealed that the same thing was happening in the tcp/upd
datasender.

**Example:**

`2024-05-31T11:53:54.612287004+02:00` becomes
`2024-05-31T11:53:54.012287004+02:00`

**Link to tracking Issue:** no issue as it's a fairly minor thing that
only affects tests, but can open if required

**Testing:** 
- manual tests
- existing tests

**Documentation:** no additional documentation added.
…3267)

**Description:** <Describe what has changed.>

Redacts primitive values in the effective config reported by the
extension.

Necessary for
open-telemetry#31641
until
open-telemetry/opentelemetry-collector#10139 is
resolved.

Relates to
open-telemetry#32983
…-telemetry#33318)

**Description:**

Replace the `elasticsearchTracesExporter` and
`elasticsearchLogsExporter` with a single `elasticsearchExporter` that
handles both.

Tests have been cleaned up to reduce repetition between traces and logs
exporters, e.g. config validation tests have been moved to more specific
`TestConfig*` tests. To enable this, some further validation has been
added to `Config.Validate`, which was previously done only when reaching
the go-elasticsearch code when constructing exporters.

Various tests have been updated to use the public APIs rather than
internal functions, so we're testing behaviour rather than the
implementation; this will enable further refactoring without breaking
tests.

**Link to tracking Issue:**

None

**Testing:**

Ran the unit tests. This is a non-functional change.

**Documentation:** 

N/A, non-functional change.

---------

Co-authored-by: Carson Ip <[email protected]>
renovate bot and others added 26 commits June 25, 2024 11:45
…7.0 (open-telemetry#33749)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[github.com/Azure/azure-sdk-for-go/sdk/azidentity](https://togithub.com/Azure/azure-sdk-for-go)
| `v1.6.0` -> `v1.7.0` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fAzure%2fazure-sdk-for-go%2fsdk%2fazidentity/v1.7.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fAzure%2fazure-sdk-for-go%2fsdk%2fazidentity/v1.7.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fAzure%2fazure-sdk-for-go%2fsdk%2fazidentity/v1.6.0/v1.7.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fAzure%2fazure-sdk-for-go%2fsdk%2fazidentity/v1.6.0/v1.7.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### 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:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: opentelemetrybot <[email protected]>
…try#33513)

**Description:**

Adds initial support for metrics. Currently only Sum ang Gauge metric
types are supported, other metric types are ignored.

**Testing:**

Added unit tests.

**Documentation:**

Added docs in component README.

---------

Co-authored-by: Carson Ip <[email protected]>
…ib/cmd/telemetrygen to v0.103.0 (open-telemetry#33752)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen](https://togithub.com/open-telemetry/opentelemetry-collector-contrib)
| `v0.102.0` -> `v0.103.0` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2fcmd%2ftelemetrygen/v0.103.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2fcmd%2ftelemetrygen/v0.103.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2fcmd%2ftelemetrygen/v0.102.0/v0.103.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2fcmd%2ftelemetrygen/v0.102.0/v0.103.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>open-telemetry/opentelemetry-collector-contrib
(github.com/open-telemetry/opentelemetry-collector-contrib/cmd/telemetrygen)</summary>

###
[`v0.103.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01030)

[Compare
Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.102.0...v0.103.0)

##### 🛑 Breaking changes 🛑

- `cmd/opampsupervisor,extension/opamp`: Upgrade the opamp-go library to
v0.15.0
([#&#8203;33416](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33416))
With this change, UUIDv7 is recommended for the OpAMP extension's
instance_uid field instead of ULID. ULIDs will continue to work, but may
be displayed as UUIDs.
The supervisor's persistent state (${storage_dir}/persistent_state.yaml)
will need to be cleared to generate a new UUIDv7 instead of a ULID.
This change may be incompatible with management servers using v0.14.0 of
opamp-go.

- `mongodbreceiver`: Now only supports `TCP` connections
([#&#8203;32199](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32199))
This fixes a bug where hosts had to explicitly set `tcp` as the
transport type. The `transport` option has been removed.

- `cmd/configschema`: Removes the deprecated `configschema` command.
This command will no longer be released or supported.
([#&#8203;33384](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33384))

- `sqlserverreceiver`: sqlserver.database.io.read_latency has been
renamed to sqlserver.database.latency with a `direction` attribute.
([#&#8203;29865](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29865))

##### 🚩 Deprecations 🚩

- `healthcheckextension`: Remove incorrect logic behind
`check_collector_pipeline` config
([#&#8203;33469](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33469))
This logic incorrectly set the pipeline to OK after waiting for enough
callbacks from the
opencensus library to be called. As this was broken, I'm removing it to
remove the dependency
on opencensus as well. Improvements will be available via healthcheckv2
extension.

- `googlecloudspannerreceiver`: Mark the component as unmaintained. If
we don't find new maintainers, it will be deprecated and removed.
([#&#8203;32651](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32651))

##### 💡 Enhancements 💡

- `filelogreceiver`: If include_file_record_number is true, it will add
the file record number as the attribute `log.file.record_number`
([#&#8203;33530](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33530))

- `kubeletstats`: Add k8s.pod.cpu.node.utilization metric
([#&#8203;33390](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33390))

- `awss3exporter`: endpoint should contain the S3 bucket
([#&#8203;32774](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32774))

- `awss3receiver`: Add support for encoding extensions to be used in the
AWS S3 Receiver.
([#&#8203;30750](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30750))

- `gitproviderreceiver`: Adds branch commit and line based metrics
([#&#8203;22028](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/22028))
    Adds the following branch based metrics.
    -   git.repository.branch.time
    -   git.repository.branch.commit.aheadby.count
    -   git.repository.branch.commit.behindby.count
    -   git.repository.branch.line.deletion.count
    -   git.repository.branch.line.addition.count

- `statsdreceiver`: update statsd receiver to use mdatagen
([#&#8203;33524](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33524))

- `coralogixexporter`: Allow setting application name from
`cx.application.name` and `cx.subsystem.name` resource attributes
([#&#8203;33217](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33217))

- `metricstransformprocessor`: Adds the 'count' aggregation type to the
Metrics Transform Processor.
([#&#8203;24978](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24978))

- `elasticsearchexporter`: Add support for confighttp options, notably
"auth".
([#&#8203;33367](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33367))
Add support for confighttp and related configuration settings, such as
"auth".
This change also means that the Elasticsearch URL may be specified as
"endpoint",
    like the otlphttp exporter.

- `elasticsearchexporter`: Check that endpoints are valid URLs during
config validation.
([#&#8203;33350](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33350))
    Check that endpoints are valid URLs during config validation so that
    an invalid endpoint causes a fatal error during startup, rather than
    leading to a persistent runtime error.

- `opampsupervisor`: Add config validation for the supervisor config
([#&#8203;32843](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32843))

- `statsdreceiver`: Added received/accepted/refused metrics
([#&#8203;24278](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24278))

- `filelogreceiver`: Add support for gzip compressed log files
([#&#8203;2328](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/2328))

- `confmap/provider/secretsmanagerprovider`: Add support for JSON
formatted secrets in secretsmanagerprovider confmap
([#&#8203;32143](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32143))
The `secretsmanagerprovider` confmap will now allow to get secret by a
json key if the secret value is json.
To specify key separate key from secret name/arn by `#` e.g.
`mySecret#mySecretKey`.

- `geoipprocessor`: Add initial processing based on source.address
resource attribute
([#&#8203;32663](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32663))

- `healthcheckv2extension`: Add shared aggregation logic for status
events.
([#&#8203;26661](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26661))

- `tailsamplingprocessor`: Simple LRU Decision Cache for "keep"
decisions
([#&#8203;31583](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31583))

- `processor/tailsampling`: Migrates internal telemetry to OpenTelemetry
SDK via mdatagen
([#&#8203;31581](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31581))
The metric names and their properties, such as bucket boundaries for
histograms, were kept like before, to keep backwards compatibility.

- `kafka`: Added `disable_fast_negotiation` configuration option for
Kafka Kerberos authentication, allowing the disabling of PA-FX-FAST
negotiation.
([#&#8203;26345](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26345))

- `pkg/ottl`: Added `keep_matching_keys` function to allow dropping all
keys from a map that don't match the pattern.
([#&#8203;32989](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32989))

- `OTel-Arrow`: Update to OTel-Arrow v0.24.0
([#&#8203;26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491))

- `pkg/ottl`: Add debug logs to help troubleshoot OTTL
statements/conditions
([#&#8203;33274](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33274))

- `pkg/ottl`: Introducing `append` function for appending items into an
existing array
([#&#8203;32141](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32141))

- `pkg/ottl`: Introducing `Uri` converter parsing URI string into
SemConv
([#&#8203;32433](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32433))

- `probabilisticsamplerprocessor`: Add Proportional and Equalizing
sampling modes
([#&#8203;31918](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31918))
Both the existing hash_seed mode and the two new modes use OTEP 235
semantic conventions to encode sampling probability.

- `prometheusreceiver`: Resource attributes produced by the prometheus
receiver now include stable semantic conventions for `server` and `url`.
([#&#8203;32814](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32814))
To migrate from the legacy net.host.name, net.host.port, and http.scheme
resource attributes, |
    migrate to server.address, server.port, and url.scheme, and then |
set the receiver.prometheus.removeLegacyResourceAttributes feature gate.

- `datadogexporter`: The Datadog Exporter now supports the `proxy_url`
parameter to configure an HTTP proxy to use when sending telemetry to
Datadog.
([#&#8203;33316](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33316))

- `spanmetrics`: Produce delta temporality span metrics with
StartTimeUnixNano and TimeUnixNano values representing an uninterrupted
series
([#&#8203;31671](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31671),
[#&#8203;30688](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30688))
This allows producing delta span metrics instead of the more
memory-intensive cumulative metrics, specifically when a downstream
component can convert the delta metrics to cumulative.

- `sqlserverreceiver`: Add support for more Database IO metrics
([#&#8203;29865](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29865))
    The following metrics have been added:
    -   sqlserver.database.latency
    -   sqlserver.database.io
    -   sqlserver.database.operations

- `cmd/opampsupervisor`: Receive and report effective config to the
OpAMP server
([#&#8203;30622](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30622))

- `processor/transform`: Add `transform.flatten.logs` featuregate to
give each log record a distinct resource and scope.
([#&#8203;32080](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32080))
This option is useful when applying transformations which alter the
resource or scope. e.g. `set(resource.attributes["to"],
attributes["from"])`, which may otherwise result in unexpected behavior.
Using this option typically incurs a performance penalty as the
processor must compute many hashes and create copies of resource and
scope information for every log record.

- `receiver/windowsperfcounters`: Counter configuration now supports
recreating the underlying performance query at scrape time.
([#&#8203;32798](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32798))

##### 🧰 Bug fixes 🧰

- `filelogreceiver`: Container parser should add k8s metadata as
resource attributes and not as log record attributes
([#&#8203;33341](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33341))
- `deltatocumulative`: properly drop samples when at limit
([#&#8203;33285](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33285))
fixes a segfault in the limiting behavior, where streams exceeding the
limit still had their samples processed. due to not being tracked, this
led to a nil-pointer deref
- `postgresqlreceiver`: Fix bug where `postgresql.rows` always returning
0 for `state="dead"`
([#&#8203;33489](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33489))
- `prometheusreceiver`: Fall back to scrape config job/instance labels
for aggregated metrics without instance/job labels
([#&#8203;32555](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32555))
- `elasticsearchexporter`: Duplicate Key in JSON
([#&#8203;33454](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33454))
- `logzioexporter`: Fix issue where log attributes were not correctly
exported
([#&#8203;33231](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33231))
- `exporter/datadog`: Prevents collector shut down when Datadog logs
pipeline fails to validate API key
([#&#8203;33195](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33195))

</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:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…ib/internal/common to v0.103.0 (open-telemetry#33753)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[github.com/open-telemetry/opentelemetry-collector-contrib/internal/common](https://togithub.com/open-telemetry/opentelemetry-collector-contrib)
| `v0.102.0` -> `v0.103.0` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2finternal%2fcommon/v0.103.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2finternal%2fcommon/v0.103.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2finternal%2fcommon/v0.102.0/v0.103.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fopen-telemetry%2fopentelemetry-collector-contrib%2finternal%2fcommon/v0.102.0/v0.103.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>open-telemetry/opentelemetry-collector-contrib
(github.com/open-telemetry/opentelemetry-collector-contrib/internal/common)</summary>

###
[`v0.103.0`](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/blob/HEAD/CHANGELOG.md#v01030)

[Compare
Source](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/compare/v0.102.0...v0.103.0)

##### 🛑 Breaking changes 🛑

- `cmd/opampsupervisor,extension/opamp`: Upgrade the opamp-go library to
v0.15.0
([#&#8203;33416](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33416))
With this change, UUIDv7 is recommended for the OpAMP extension's
instance_uid field instead of ULID. ULIDs will continue to work, but may
be displayed as UUIDs.
The supervisor's persistent state (${storage_dir}/persistent_state.yaml)
will need to be cleared to generate a new UUIDv7 instead of a ULID.
This change may be incompatible with management servers using v0.14.0 of
opamp-go.

- `mongodbreceiver`: Now only supports `TCP` connections
([#&#8203;32199](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32199))
This fixes a bug where hosts had to explicitly set `tcp` as the
transport type. The `transport` option has been removed.

- `cmd/configschema`: Removes the deprecated `configschema` command.
This command will no longer be released or supported.
([#&#8203;33384](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33384))

- `sqlserverreceiver`: sqlserver.database.io.read_latency has been
renamed to sqlserver.database.latency with a `direction` attribute.
([#&#8203;29865](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29865))

##### 🚩 Deprecations 🚩

- `healthcheckextension`: Remove incorrect logic behind
`check_collector_pipeline` config
([#&#8203;33469](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33469))
This logic incorrectly set the pipeline to OK after waiting for enough
callbacks from the
opencensus library to be called. As this was broken, I'm removing it to
remove the dependency
on opencensus as well. Improvements will be available via healthcheckv2
extension.

- `googlecloudspannerreceiver`: Mark the component as unmaintained. If
we don't find new maintainers, it will be deprecated and removed.
([#&#8203;32651](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32651))

##### 💡 Enhancements 💡

- `filelogreceiver`: If include_file_record_number is true, it will add
the file record number as the attribute `log.file.record_number`
([#&#8203;33530](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33530))

- `kubeletstats`: Add k8s.pod.cpu.node.utilization metric
([#&#8203;33390](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33390))

- `awss3exporter`: endpoint should contain the S3 bucket
([#&#8203;32774](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32774))

- `awss3receiver`: Add support for encoding extensions to be used in the
AWS S3 Receiver.
([#&#8203;30750](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30750))

- `gitproviderreceiver`: Adds branch commit and line based metrics
([#&#8203;22028](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/22028))
    Adds the following branch based metrics.
    -   git.repository.branch.time
    -   git.repository.branch.commit.aheadby.count
    -   git.repository.branch.commit.behindby.count
    -   git.repository.branch.line.deletion.count
    -   git.repository.branch.line.addition.count

- `statsdreceiver`: update statsd receiver to use mdatagen
([#&#8203;33524](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33524))

- `coralogixexporter`: Allow setting application name from
`cx.application.name` and `cx.subsystem.name` resource attributes
([#&#8203;33217](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33217))

- `metricstransformprocessor`: Adds the 'count' aggregation type to the
Metrics Transform Processor.
([#&#8203;24978](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24978))

- `elasticsearchexporter`: Add support for confighttp options, notably
"auth".
([#&#8203;33367](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33367))
Add support for confighttp and related configuration settings, such as
"auth".
This change also means that the Elasticsearch URL may be specified as
"endpoint",
    like the otlphttp exporter.

- `elasticsearchexporter`: Check that endpoints are valid URLs during
config validation.
([#&#8203;33350](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33350))
    Check that endpoints are valid URLs during config validation so that
    an invalid endpoint causes a fatal error during startup, rather than
    leading to a persistent runtime error.

- `opampsupervisor`: Add config validation for the supervisor config
([#&#8203;32843](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32843))

- `statsdreceiver`: Added received/accepted/refused metrics
([#&#8203;24278](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/24278))

- `filelogreceiver`: Add support for gzip compressed log files
([#&#8203;2328](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/2328))

- `confmap/provider/secretsmanagerprovider`: Add support for JSON
formatted secrets in secretsmanagerprovider confmap
([#&#8203;32143](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32143))
The `secretsmanagerprovider` confmap will now allow to get secret by a
json key if the secret value is json.
To specify key separate key from secret name/arn by `#` e.g.
`mySecret#mySecretKey`.

- `geoipprocessor`: Add initial processing based on source.address
resource attribute
([#&#8203;32663](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32663))

- `healthcheckv2extension`: Add shared aggregation logic for status
events.
([#&#8203;26661](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26661))

- `tailsamplingprocessor`: Simple LRU Decision Cache for "keep"
decisions
([#&#8203;31583](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31583))

- `processor/tailsampling`: Migrates internal telemetry to OpenTelemetry
SDK via mdatagen
([#&#8203;31581](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31581))
The metric names and their properties, such as bucket boundaries for
histograms, were kept like before, to keep backwards compatibility.

- `kafka`: Added `disable_fast_negotiation` configuration option for
Kafka Kerberos authentication, allowing the disabling of PA-FX-FAST
negotiation.
([#&#8203;26345](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26345))

- `pkg/ottl`: Added `keep_matching_keys` function to allow dropping all
keys from a map that don't match the pattern.
([#&#8203;32989](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32989))

- `OTel-Arrow`: Update to OTel-Arrow v0.24.0
([#&#8203;26491](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/26491))

- `pkg/ottl`: Add debug logs to help troubleshoot OTTL
statements/conditions
([#&#8203;33274](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33274))

- `pkg/ottl`: Introducing `append` function for appending items into an
existing array
([#&#8203;32141](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32141))

- `pkg/ottl`: Introducing `Uri` converter parsing URI string into
SemConv
([#&#8203;32433](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32433))

- `probabilisticsamplerprocessor`: Add Proportional and Equalizing
sampling modes
([#&#8203;31918](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31918))
Both the existing hash_seed mode and the two new modes use OTEP 235
semantic conventions to encode sampling probability.

- `prometheusreceiver`: Resource attributes produced by the prometheus
receiver now include stable semantic conventions for `server` and `url`.
([#&#8203;32814](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32814))
To migrate from the legacy net.host.name, net.host.port, and http.scheme
resource attributes, |
    migrate to server.address, server.port, and url.scheme, and then |
set the receiver.prometheus.removeLegacyResourceAttributes feature gate.

- `datadogexporter`: The Datadog Exporter now supports the `proxy_url`
parameter to configure an HTTP proxy to use when sending telemetry to
Datadog.
([#&#8203;33316](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33316))

- `spanmetrics`: Produce delta temporality span metrics with
StartTimeUnixNano and TimeUnixNano values representing an uninterrupted
series
([#&#8203;31671](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/31671),
[#&#8203;30688](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30688))
This allows producing delta span metrics instead of the more
memory-intensive cumulative metrics, specifically when a downstream
component can convert the delta metrics to cumulative.

- `sqlserverreceiver`: Add support for more Database IO metrics
([#&#8203;29865](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/29865))
    The following metrics have been added:
    -   sqlserver.database.latency
    -   sqlserver.database.io
    -   sqlserver.database.operations

- `cmd/opampsupervisor`: Receive and report effective config to the
OpAMP server
([#&#8203;30622](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/30622))

- `processor/transform`: Add `transform.flatten.logs` featuregate to
give each log record a distinct resource and scope.
([#&#8203;32080](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32080))
This option is useful when applying transformations which alter the
resource or scope. e.g. `set(resource.attributes["to"],
attributes["from"])`, which may otherwise result in unexpected behavior.
Using this option typically incurs a performance penalty as the
processor must compute many hashes and create copies of resource and
scope information for every log record.

- `receiver/windowsperfcounters`: Counter configuration now supports
recreating the underlying performance query at scrape time.
([#&#8203;32798](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32798))

##### 🧰 Bug fixes 🧰

- `filelogreceiver`: Container parser should add k8s metadata as
resource attributes and not as log record attributes
([#&#8203;33341](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33341))
- `deltatocumulative`: properly drop samples when at limit
([#&#8203;33285](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33285))
fixes a segfault in the limiting behavior, where streams exceeding the
limit still had their samples processed. due to not being tracked, this
led to a nil-pointer deref
- `postgresqlreceiver`: Fix bug where `postgresql.rows` always returning
0 for `state="dead"`
([#&#8203;33489](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33489))
- `prometheusreceiver`: Fall back to scrape config job/instance labels
for aggregated metrics without instance/job labels
([#&#8203;32555](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/32555))
- `elasticsearchexporter`: Duplicate Key in JSON
([#&#8203;33454](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33454))
- `logzioexporter`: Fix issue where log attributes were not correctly
exported
([#&#8203;33231](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33231))
- `exporter/datadog`: Prevents collector shut down when Datadog logs
pipeline fails to validate API key
([#&#8203;33195](https://togithub.com/open-telemetry/opentelemetry-collector-contrib/issues/33195))

</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:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
…elemetry#33739)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[github.com/DataDog/agent-payload/v5](https://togithub.com/DataDog/agent-payload)
| `v5.0.122` -> `v5.0.123` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fagent-payload%2fv5/v5.0.123?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fagent-payload%2fv5/v5.0.123?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fagent-payload%2fv5/v5.0.122/v5.0.123?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fagent-payload%2fv5/v5.0.122/v5.0.123?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>DataDog/agent-payload
(github.com/DataDog/agent-payload/v5)</summary>

###
[`v5.0.123`](https://togithub.com/DataDog/agent-payload/releases/tag/v5.0.123)

[Compare
Source](https://togithub.com/DataDog/agent-payload/compare/v5.0.122...v5.0.123)

#### What's Changed

- Rename `statsByStatusCode` to statsByErrorCode by
[@&#8203;DanielLavie](https://togithub.com/DanielLavie) in
[https://github.com/DataDog/agent-payload/pull/320](https://togithub.com/DataDog/agent-payload/pull/320)

**Full Changelog**:
DataDog/agent-payload@v5.0.122...v5.0.123

</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:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: opentelemetrybot <[email protected]>
…try#33740)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[github.com/jaegertracing/jaeger](https://togithub.com/jaegertracing/jaeger)
| `v1.58.0` -> `v1.58.1` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fjaegertracing%2fjaeger/v1.58.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fjaegertracing%2fjaeger/v1.58.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fjaegertracing%2fjaeger/v1.58.0/v1.58.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fjaegertracing%2fjaeger/v1.58.0/v1.58.1?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>jaegertracing/jaeger
(github.com/jaegertracing/jaeger)</summary>

###
[`v1.58.1`](https://togithub.com/jaegertracing/jaeger/releases/tag/v1.58.1)

[Compare
Source](https://togithub.com/jaegertracing/jaeger/compare/v1.58.0...v1.58.1)

##### Backend Changes

##### 🐞 Bug fixes, Minor Improvements

- SPM: Restore "operation" name in the metrics response
([@&#8203;yurishkuro](https://togithub.com/yurishkuro) in
[#&#8203;5673](https://togithub.com/jaegertracing/jaeger/pull/5673))

</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:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: opentelemetrybot <[email protected]>
Co-authored-by: Yang Song <[email protected]>
…ry#33714)

The new attribute are added to the MongoDB receiver to distinguish
metrics coming from different MongoDB instances.
- `server.address`: The address of the MongoDB host, enabled by default.
  - `server.port`: The port of the MongoDB host, disabled by default.

Resolves
open-telemetry#32350
and
open-telemetry#32810

Co-authored-by: Curtis Robert <[email protected]>
…metry#33746)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[bitbucket.org/atlassian/go-asap/v2](https://bitbucket.org/atlassian/go-asap)
| `v2.8.0` -> `v2.9.0` |
[![age](https://developer.mend.io/api/mc/badges/age/go/bitbucket.org%2fatlassian%2fgo-asap%2fv2/v2.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/bitbucket.org%2fatlassian%2fgo-asap%2fv2/v2.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/bitbucket.org%2fatlassian%2fgo-asap%2fv2/v2.8.0/v2.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/bitbucket.org%2fatlassian%2fgo-asap%2fv2/v2.8.0/v2.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>atlassian/go-asap
(bitbucket.org/atlassian/go-asap/v2)</summary>

###
[`v2.9.0`](https://bitbucket.org/atlassian/go-asap/branches/compare/v2.9.0%0Dv2.8.0)

[Compare
Source](https://bitbucket.org/atlassian/go-asap/branches/compare/v2.9.0%0Dv2.8.0)

</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:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: opentelemetrybot <[email protected]>
Co-authored-by: Yang Song <[email protected]>
…al` instance (open-telemetry#33692)

**Description:**
Clarifies the current treatment of the `_Total` instances. 

**Link to tracking Issue:**
Fix open-telemetry#29054

**Testing:**
Manually validated the configuration added to the README.md

**Documentation:**
Described the behavior of the `_Total` instance as currently
implemented.

---------

Co-authored-by: Curtis Robert <[email protected]>
…y#33763)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[github.com/DataDog/sketches-go](https://togithub.com/DataDog/sketches-go)
| `v1.4.5` -> `v1.4.6` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2fDataDog%2fsketches-go/v1.4.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2fDataDog%2fsketches-go/v1.4.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2fDataDog%2fsketches-go/v1.4.5/v1.4.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2fDataDog%2fsketches-go/v1.4.5/v1.4.6?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>DataDog/sketches-go (github.com/DataDog/sketches-go)</summary>

###
[`v1.4.6`](https://togithub.com/DataDog/sketches-go/releases/tag/v1.4.6)

[Compare
Source](https://togithub.com/DataDog/sketches-go/compare/v1.4.5...v1.4.6)

#### What's Changed

- Avoid inconsistent quantile computation between architectures by
[@&#8203;gduranceau](https://togithub.com/gduranceau) in
[https://github.com/DataDog/sketches-go/pull/80](https://togithub.com/DataDog/sketches-go/pull/80)

#### New Contributors

- [@&#8203;gduranceau](https://togithub.com/gduranceau) made their first
contribution in
[https://github.com/DataDog/sketches-go/pull/80](https://togithub.com/DataDog/sketches-go/pull/80)

**Full Changelog**:
DataDog/sketches-go@v1.4.5...v1.4.6

</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:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: opentelemetrybot <[email protected]>
…d/common to v1.0.949 (open-telemetry#33743)

[![Mend
Renovate](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
|
[github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common](https://togithub.com/tencentcloud/tencentcloud-sdk-go)
| `v1.0.944` -> `v1.0.949` |
[![age](https://developer.mend.io/api/mc/badges/age/go/github.com%2ftencentcloud%2ftencentcloud-sdk-go%2ftencentcloud%2fcommon/v1.0.949?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/go/github.com%2ftencentcloud%2ftencentcloud-sdk-go%2ftencentcloud%2fcommon/v1.0.949?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/go/github.com%2ftencentcloud%2ftencentcloud-sdk-go%2ftencentcloud%2fcommon/v1.0.944/v1.0.949?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/go/github.com%2ftencentcloud%2ftencentcloud-sdk-go%2ftencentcloud%2fcommon/v1.0.944/v1.0.949?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

> [!WARNING]
> Some dependencies could not be looked up. Check the Dependency
Dashboard for more information.

---

### Release Notes

<details>
<summary>tencentcloud/tencentcloud-sdk-go
(github.com/tencentcloud/tencentcloud-sdk-go/tencentcloud/common)</summary>

###
[`v1.0.949`](https://togithub.com/tencentcloud/tencentcloud-sdk-go/blob/HEAD/CHANGELOG.md#Release-v10949)

[Compare
Source](https://togithub.com/tencentcloud/tencentcloud-sdk-go/compare/v1.0.948...v1.0.949)

#### 语音识别(asr) 版本:2019-06-14

##### 第 36 次发布

发布时间:2024-06-25 01:07:52

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[VoicePrintGroupVerify](https://cloud.tencent.com/document/api/1093/107668)

修改接口:

-   [VoicePrintCount](https://cloud.tencent.com/document/api/1093/96061)

    -   新增入参:GroupId, CountMod

- [VoicePrintDelete](https://cloud.tencent.com/document/api/1093/94484)

    -   新增入参:GroupId, DelMod

- [VoicePrintEnroll](https://cloud.tencent.com/document/api/1093/94483)

    -   新增入参:GroupId

新增数据结构:

-
[VerifyTop](https://cloud.tencent.com/document/api/1093/37824#VerifyTop)
-
[VerifyTopResult](https://cloud.tencent.com/document/api/1093/37824#VerifyTopResult)

修改数据结构:

-
[VoicePrintCountData](https://cloud.tencent.com/document/api/1093/37824#VoicePrintCountData)

    -   新增成员:VoicePrintList

#### 数据湖计算 DLC(dlc) 版本:2021-01-25

##### 第 95 次发布

发布时间:2024-06-25 01:13:07

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[DescribeDataEnginesScaleDetail](https://cloud.tencent.com/document/api/1342/107670)

新增数据结构:

-
[DataEngineScaleInfo](https://cloud.tencent.com/document/api/1342/53778#DataEngineScaleInfo)
-
[DataEngineScaleInfoDetail](https://cloud.tencent.com/document/api/1342/53778#DataEngineScaleInfoDetail)

#### 数据安全治理中心(dsgc) 版本:2019-07-23

##### 第 15 次发布

发布时间:2024-06-25 01:13:45

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[CosTaskResult](https://cloud.tencent.com/document/api/1087/96844#CosTaskResult)

- <font color="#dd0000">**修改成员**:</font>Result, ResultDescription,
ErrDescription, ResourceId

#### 腾讯电子签企业版(ess) 版本:2020-11-11

##### 第 176 次发布

发布时间:2024-06-25 01:14:54

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-
[CreateLegalSealQrCode](https://cloud.tencent.com/document/api/1323/107551)

#### 腾讯电子签(基础版)(essbasic) 版本:2021-05-26

##### 第 172 次发布

发布时间:2024-06-25 01:15:10

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-
[CreateLegalSealQrCode](https://cloud.tencent.com/document/api/1420/107552)

#### 腾讯电子签(基础版)(essbasic) 版本:2020-12-22

#### 物联网开发平台(iotexplorer) 版本:2019-04-23

##### 第 68 次发布

发布时间:2024-06-25 01:16:25

本次发布包含了以下内容:

改善已有的文档。

新增接口:

- [DescribeFirmware](https://cloud.tencent.com/document/api/1081/107671)

#### 大模型知识引擎(lke) 版本:2023-11-30

##### 第 9 次发布

发布时间:2024-06-25 01:18:18

本次发布包含了以下内容:

改善已有的文档。

新增接口:

- [ConvertDocument](https://cloud.tencent.com/document/api/1759/107672)
-
[GetAnswerTypeDataCount](https://cloud.tencent.com/document/api/1759/107674)
- [GetLikeDataCount](https://cloud.tencent.com/document/api/1759/107673)

新增数据结构:

-
[WordRecognizeInfo](https://cloud.tencent.com/document/api/1759/105104#WordRecognizeInfo)

#### 消息队列 TDMQ(tdmq) 版本:2020-02-17

##### 第 116 次发布

发布时间:2024-06-25 01:23:14

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[DescribeRabbitMQExchanges](https://cloud.tencent.com/document/api/1179/107675)

新增数据结构:

-
[RabbitMQExchangeListInfo](https://cloud.tencent.com/document/api/1179/46089#RabbitMQExchangeListInfo)

#### 弹性微服务(tem) 版本:2021-07-01

##### 第 42 次发布

发布时间:2024-06-25 01:23:38

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[UseDefaultRepoParameters](https://cloud.tencent.com/document/api/1371/60171#UseDefaultRepoParameters)

- <font color="#dd0000">**修改成员**:</font>EnterpriseInstanceName,
EnterpriseInstanceChargeType, EnterpriseInstanceType

#### 弹性微服务(tem) 版本:2020-12-21

#### 消息队列 RocketMQ 版(trocket) 版本:2023-03-08

##### 第 16 次发布

发布时间:2024-06-25 01:24:46

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[DescribeProductSKUs](https://cloud.tencent.com/document/api/1493/107676)

新增数据结构:

- [PriceTag](https://cloud.tencent.com/document/api/1493/96031#PriceTag)
-
[ProductSKU](https://cloud.tencent.com/document/api/1493/96031#ProductSKU)

#### 实时音视频(trtc) 版本:2019-07-22

##### 第 79 次发布

发布时间:2024-06-25 01:25:02

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[McuLayout](https://cloud.tencent.com/document/api/647/44055#McuLayout)

    -   新增成员:BackGroundColorMode

#### 腾讯同传系统(tsi) 版本:2021-03-25

##### 第 1 次发布

发布时间:2024-06-24 10:37:18

本次发布包含了以下内容:

改善已有的文档。

新增接口:

- [TongChuanDisplay](https://cloud.tencent.com/document/api/1399/107636)
-
[TongChuanRecognize](https://cloud.tencent.com/document/api/1399/107635)
-   [TongChuanSync](https://cloud.tencent.com/document/api/1399/107634)

新增数据结构:

-
[DisplayInfo](https://cloud.tencent.com/document/api/1399/107637#DisplayInfo)

#### 私有网络(vpc) 版本:2017-03-12

##### 第 190 次发布

发布时间:2024-06-25 01:26:23

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[GatewayFlowMonitorDetail](https://cloud.tencent.com/document/api/215/15824#GatewayFlowMonitorDetail)

    -   新增成员:ConcurrentConnectionCount, NewConnectionRate

#### Web 应用防火墙(waf) 版本:2018-01-25

##### 第 90 次发布

发布时间:2024-06-25 01:27:00

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-   [AddAreaBanAreas](https://cloud.tencent.com/document/api/627/107677)

###
[`v1.0.948`](https://togithub.com/tencentcloud/tencentcloud-sdk-go/blob/HEAD/CHANGELOG.md#Release-v10948)

[Compare
Source](https://togithub.com/tencentcloud/tencentcloud-sdk-go/compare/v1.0.947...v1.0.948)

#### 云数据库 MySQL(cdb) 版本:2017-03-20

##### 第 159 次发布

发布时间:2024-06-24 01:09:17

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[DescribeInstanceUpgradeType](https://cloud.tencent.com/document/api/236/107630)

新增数据结构:

-
[ClusterTopology](https://cloud.tencent.com/document/api/236/15878#ClusterTopology)
-
[NodeDistribution](https://cloud.tencent.com/document/api/236/15878#NodeDistribution)
-
[ReadWriteNode](https://cloud.tencent.com/document/api/236/15878#ReadWriteNode)
-
[ReadonlyNode](https://cloud.tencent.com/document/api/236/15878#ReadonlyNode)

#### 大模型知识引擎(lke) 版本:2023-11-30

##### 第 8 次发布

发布时间:2024-06-21 21:11:25

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-
[DescribeStorageCredential](https://cloud.tencent.com/document/api/1759/105050)

    -   新增入参:TypeKey

    -   <font color="#dd0000">**修改入参**:</font>BotBizId

-   [GetDocPreview](https://cloud.tencent.com/document/api/1759/105067)

    -   新增入参:TypeKey

-   [GetWsToken](https://cloud.tencent.com/document/api/1759/105089)

    -   新增出参:Balance, InputLenLimit

新增数据结构:

-
[FileInfo](https://cloud.tencent.com/document/api/1759/105104#FileInfo)
-
[MsgFileInfo](https://cloud.tencent.com/document/api/1759/105104#MsgFileInfo)

修改数据结构:

-
[AppModel](https://cloud.tencent.com/document/api/1759/105104#AppModel)

    -   新增成员:TokenBalance

- [Context](https://cloud.tencent.com/document/api/1759/105104#Context)

    -   新增成员:FileInfos

-
[KnowledgeQaSearch](https://cloud.tencent.com/document/api/1759/105104#KnowledgeQaSearch)

    -   新增成员:Confidence

-
[MsgRecord](https://cloud.tencent.com/document/api/1759/105104#MsgRecord)

    -   新增成员:FileInfos

#### 邮件推送(ses) 版本:2020-10-02

##### 第 21 次发布

发布时间:2024-06-21 16:22:39

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-   [SendEmail](https://cloud.tencent.com/document/api/1288/51034)

    -   新增入参:SmtpMessageId, SmtpHeaders

#### 消息队列 TDMQ(tdmq) 版本:2020-02-17

##### 第 115 次发布

发布时间:2024-06-24 01:23:04

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[RocketMQClusterInfo](https://cloud.tencent.com/document/api/1179/46089#RocketMQClusterInfo)

    -   新增成员:ZoneId, ZoneIds

#### 实时音视频(trtc) 版本:2019-07-22

##### 第 78 次发布

发布时间:2024-06-24 01:24:46

本次发布包含了以下内容:

改善已有的文档。

修改接口:

- [StartStreamIngest](https://cloud.tencent.com/document/api/647/101872)

###
[`v1.0.947`](https://togithub.com/tencentcloud/tencentcloud-sdk-go/blob/HEAD/CHANGELOG.md#Release-v10947)

[Compare
Source](https://togithub.com/tencentcloud/tencentcloud-sdk-go/compare/v1.0.946...v1.0.947)

#### 语音识别(asr) 版本:2019-06-14

##### 第 35 次发布

发布时间:2024-06-21 01:10:11

本次发布包含了以下内容:

改善已有的文档。

修改接口:

- [VoicePrintDelete](https://cloud.tencent.com/document/api/1093/94484)

    -   <font color="#dd0000">**修改入参**:</font>VoicePrintId

#### 费用中心(billing) 版本:2018-07-09

##### 第 60 次发布

发布时间:2024-06-21 01:11:19

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[ConsumptionResourceSummaryDataItem](https://cloud.tencent.com/document/api/555/19183#ConsumptionResourceSummaryDataItem)

    -   新增成员:Tags

#### 访问管理(cam) 版本:2019-01-16

##### 第 59 次发布

发布时间:2024-06-21 01:14:07

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-   [CreateAccessKey](https://cloud.tencent.com/document/api/598/82370)

    -   新增入参:Description

修改数据结构:

-
[AccessKey](https://cloud.tencent.com/document/api/598/33167#AccessKey)

    -   新增成员:Description

-
[AccessKeyDetail](https://cloud.tencent.com/document/api/598/33167#AccessKeyDetail)

    -   新增成员:Description

#### TDSQL-C MySQL 版(cynosdb) 版本:2019-01-07

##### 第 94 次发布

发布时间:2024-06-21 01:30:05

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-   [RenewClusters](https://cloud.tencent.com/document/api/1003/107548)

#### 数据湖计算 DLC(dlc) 版本:2021-01-25

##### 第 94 次发布

发布时间:2024-06-21 01:33:48

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[DescribeSparkSessionBatchSQLCost](https://cloud.tencent.com/document/api/1342/107549)

修改接口:

-
[DescribeTasksOverview](https://cloud.tencent.com/document/api/1342/107503)

    -   新增入参:StartTime, EndTime, Filters, DataEngineName

新增数据结构:

-
[BatchSQLCostInfo](https://cloud.tencent.com/document/api/1342/53778#BatchSQLCostInfo)

#### 数据传输服务(dts) 版本:2021-12-06

#### 数据传输服务(dts) 版本:2018-03-30

##### 第 22 次发布

发布时间:2024-06-21 01:37:37

本次发布包含了以下内容:

改善已有的文档。

<font color="#dd0000">**删除接口**:</font>

-   DescribeRegionConf

<font color="#dd0000">**删除数据结构**:</font>

-   SubscribeRegionConf

#### 腾讯电子签企业版(ess) 版本:2020-11-11

##### 第 175 次发布

发布时间:2024-06-21 01:41:37

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[CreateFlowBlockchainEvidenceUrl](https://cloud.tencent.com/document/api/1323/107550)
-
[CreateLegalSealQrCode](https://cloud.tencent.com/document/api/1323/107551)

#### 腾讯电子签(基础版)(essbasic) 版本:2021-05-26

##### 第 171 次发布

发布时间:2024-06-21 01:42:38

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[CreateFlowBlockchainEvidenceUrl](https://cloud.tencent.com/document/api/1420/107553)
-
[CreateLegalSealQrCode](https://cloud.tencent.com/document/api/1420/107552)

#### 腾讯电子签(基础版)(essbasic) 版本:2020-12-22

#### 云数据库 MongoDB(mongodb) 版本:2019-07-25

##### 第 41 次发布

发布时间:2024-06-21 01:58:00

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[ModifyInstanceParams](https://cloud.tencent.com/document/api/240/107557)

新增数据结构:

-
[ModifyMongoDBParamType](https://cloud.tencent.com/document/api/240/38576#ModifyMongoDBParamType)

#### 云数据库 MongoDB(mongodb) 版本:2018-04-08

#### 媒体处理(mps) 版本:2019-06-12

##### 第 86 次发布

发布时间:2024-06-21 01:59:51

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-
[CreateAdaptiveDynamicStreamingTemplate](https://cloud.tencent.com/document/api/862/45749)

    -   新增入参:SegmentType

-
[ModifyAdaptiveDynamicStreamingTemplate](https://cloud.tencent.com/document/api/862/45746)

    -   新增入参:SegmentType

修改数据结构:

-
[AdaptiveDynamicStreamingTemplate](https://cloud.tencent.com/document/api/862/37615#AdaptiveDynamicStreamingTemplate)

    -   新增成员:SegmentType

-
[VideoTemplateInfo](https://cloud.tencent.com/document/api/862/37615#VideoTemplateInfo)

    -   新增成员:SegmentType

-
[VideoTemplateInfoForUpdate](https://cloud.tencent.com/document/api/862/37615#VideoTemplateInfoForUpdate)

    -   新增成员:SegmentType

#### 文字识别(ocr) 版本:2018-11-19

##### 第 138 次发布

发布时间:2024-06-21 02:02:31

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-
[VatInvoiceVerifyNew](https://cloud.tencent.com/document/api/866/73674)

    -   新增出参:FinancialBill

新增数据结构:

-
[FinancialBill](https://cloud.tencent.com/document/api/866/33527#FinancialBill)
-
[FinancialBillItem](https://cloud.tencent.com/document/api/866/33527#FinancialBillItem)
-
[FinancialBillItemDetails](https://cloud.tencent.com/document/api/866/33527#FinancialBillItemDetails)

#### 集团账号管理(organization) 版本:2021-03-31

##### 第 33 次发布

发布时间:2024-06-21 02:03:56

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[AcceptJoinShareUnitInvitation](https://cloud.tencent.com/document/api/850/107559)
-
[RejectJoinShareUnitInvitation](https://cloud.tencent.com/document/api/850/107558)

#### 集团账号管理(organization) 版本:2018-12-25

#### 远程实时操控(trro) 版本:2022-03-25

##### 第 5 次发布

发布时间:2024-06-21 02:25:01

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-
[DescribeProjectInfo](https://cloud.tencent.com/document/api/1584/89810)

    -   <font color="#dd0000">**修改入参**:</font>ProjectId

#### 微服务平台 TSF(tsf) 版本:2018-03-26

##### 第 110 次发布

发布时间:2024-06-21 02:26:46

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[MsInstance](https://cloud.tencent.com/document/api/649/36099#MsInstance)

    -   新增成员:MetaJson

###
[`v1.0.946`](https://togithub.com/tencentcloud/tencentcloud-sdk-go/blob/HEAD/CHANGELOG.md#Release-v10946)

[Compare
Source](https://togithub.com/tencentcloud/tencentcloud-sdk-go/compare/v1.0.945...v1.0.946)

#### 腾讯云数据仓库 TCHouse-D(cdwdoris) 版本:2021-12-28

##### 第 13 次发布

发布时间:2024-06-20 01:19:00

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-
[DescribeSlowQueryRecordsDownload](https://cloud.tencent.com/document/api/1387/102613)

    -   新增入参:DbName, CatalogName

#### 消息队列 CKafka 版(ckafka) 版本:2019-08-19

##### 第 105 次发布

发布时间:2024-06-20 01:21:11

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[ZoneResponse](https://cloud.tencent.com/document/api/597/40861#ZoneResponse)

    -   新增成员:RequestId, Version, Offset, Limit, ForceCheckTag

#### 云安全一体化平台(csip) 版本:2022-11-21

##### 第 40 次发布

发布时间:2024-06-20 01:24:58

本次发布包含了以下内容:

改善已有的文档。

修改接口:

- [CreateDomainAndIp](https://cloud.tencent.com/document/api/664/93274)

    -   新增入参:MemberId

-
[CreateRiskCenterScanTask](https://cloud.tencent.com/document/api/664/94177)

    -   新增入参:FinishWebHook

- [DeleteDomainAndIp](https://cloud.tencent.com/document/api/664/98743)

    -   新增入参:MemberId

-
[ModifyRiskCenterScanTask](https://cloud.tencent.com/document/api/664/103117)

    -   新增入参:FinishWebHook

修改数据结构:

-
[AssetViewVULRiskData](https://cloud.tencent.com/document/api/664/90825#AssetViewVULRiskData)

    -   新增成员:TvdID, IsOneClick

-
[CVMAssetVO](https://cloud.tencent.com/document/api/664/90825#CVMAssetVO)

    -   新增成员:RealAppid, CloudType

-
[VULViewVULRiskData](https://cloud.tencent.com/document/api/664/90825#VULViewVULRiskData)

    -   新增成员:TvdID, IsOneClick

#### TDSQL-C MySQL 版(cynosdb) 版本:2019-01-07

##### 第 93 次发布

发布时间:2024-06-20 01:30:19

本次发布包含了以下内容:

改善已有的文档。

新增数据结构:

-
[ExchangeInstanceInfo](https://cloud.tencent.com/document/api/1003/48097#ExchangeInstanceInfo)
-
[ExchangeRoGroupInfo](https://cloud.tencent.com/document/api/1003/48097#ExchangeRoGroupInfo)
-
[RollbackInstanceInfo](https://cloud.tencent.com/document/api/1003/48097#RollbackInstanceInfo)
-
[RollbackProcessInfo](https://cloud.tencent.com/document/api/1003/48097#RollbackProcessInfo)
-
[RollbackRoGroupInfo](https://cloud.tencent.com/document/api/1003/48097#RollbackRoGroupInfo)

修改数据结构:

-
[BizTaskInfo](https://cloud.tencent.com/document/api/1003/48097#BizTaskInfo)

    -   新增成员:Region, InstanceCLSDeliveryInfos

-
[RollbackData](https://cloud.tencent.com/document/api/1003/48097#RollbackData)

    -   新增成员:RollbackProcess

#### 数据湖计算 DLC(dlc) 版本:2021-01-25

##### 第 93 次发布

发布时间:2024-06-20 01:34:00

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[DescribeTasksOverview](https://cloud.tencent.com/document/api/1342/107503)

#### 物联网边缘计算平台(iecp) 版本:2021-09-14

##### 第 8 次发布

发布时间:2024-06-20 01:46:44

本次发布包含了以下内容:

改善已有的文档。

<font color="#dd0000">**预下线接口**:</font>

-   ApplyMarketComponent
-   CreateApplicationVisualization
-   CreateEdgeUnitApplicationVisualization
-   CreateEdgeUnitApplicationYaml
-   DeleteApplications
-   DeleteEdgeUnitApplications
-   DescribeApplicationVisualization
-   DescribeApplicationYaml
-   DescribeApplicationYamlError
-   DescribeApplications
-   DescribeEdgeUnitApplicationEvents
-   DescribeEdgeUnitApplicationLogs
-   DescribeEdgeUnitApplicationPodContainers
-   DescribeEdgeUnitApplicationPods
-   DescribeEdgeUnitApplicationVisualization
-   DescribeEdgeUnitApplicationYaml
-   DescribeEdgeUnitApplicationYamlError
-   DescribeEdgeUnitCloud
-   ModifyApplicationBasicInfo
-   ModifyApplicationVisualization

#### 大模型知识引擎(lke) 版本:2023-11-30

##### 第 7 次发布

发布时间:2024-06-20 01:56:34

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[CreateReconstructDocumentFlow](https://cloud.tencent.com/document/api/1759/107506)
-
[GetReconstructDocumentResult](https://cloud.tencent.com/document/api/1759/107505)
-
[ReconstructDocument](https://cloud.tencent.com/document/api/1759/107504)

新增数据结构:

-   [Coord](https://cloud.tencent.com/document/api/1759/105104#Coord)
-
[CreateReconstructDocumentFlowConfig](https://cloud.tencent.com/document/api/1759/105104#CreateReconstructDocumentFlowConfig)
-
[DocumentElement](https://cloud.tencent.com/document/api/1759/105104#DocumentElement)
-
[DocumentRecognizeInfo](https://cloud.tencent.com/document/api/1759/105104#DocumentRecognizeInfo)
- [Polygon](https://cloud.tencent.com/document/api/1759/105104#Polygon)
-
[ReconstructDocumentConfig](https://cloud.tencent.com/document/api/1759/105104#ReconstructDocumentConfig)
-
[ReconstructDocumentFailedPage](https://cloud.tencent.com/document/api/1759/105104#ReconstructDocumentFailedPage)

#### 腾讯云可观测平台(monitor) 版本:2018-07-24

##### 第 117 次发布

发布时间:2024-06-20 01:58:59

本次发布包含了以下内容:

改善已有的文档。

修改接口:

- [DeleteAlarmPolicy](https://cloud.tencent.com/document/api/248/51285)

    -   新增入参:PromInsIds

#### 容器服务(tke) 版本:2022-05-01

#### 容器服务(tke) 版本:2018-05-25

##### 第 173 次发布

发布时间:2024-06-20 02:22:36

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[DescribePodChargeInfo](https://cloud.tencent.com/document/api/457/107507)

修改接口:

-   [DescribeIPAMD](https://cloud.tencent.com/document/api/457/101765)

    -   新增出参:EnableTrunkingENI

新增数据结构:

-
[PodChargeInfo](https://cloud.tencent.com/document/api/457/31866#PodChargeInfo)

修改数据结构:

-
[ContainerState](https://cloud.tencent.com/document/api/457/31866#ContainerState)

- <font color="#dd0000">**修改成员**:</font>StartTime, State, FinishTime,
ExitCode, Reason, Message, RestartCount

#### 微服务引擎(tse) 版本:2020-12-07

##### 第 72 次发布

发布时间:2024-06-20 02:26:25

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[UpstreamHealthCheckConfig](https://cloud.tencent.com/document/api/1364/54942#UpstreamHealthCheckConfig)

    -   新增成员:ZeroWeightHeathCheck

#### 微服务平台 TSF(tsf) 版本:2018-03-26

##### 第 109 次发布

发布时间:2024-06-20 02:27:26

本次发布包含了以下内容:

改善已有的文档。

<font color="#dd0000">**预下线接口**:</font>

-   DescribeApplicationBusinessLogConfig

#### Web 应用防火墙(waf) 版本:2018-01-25

##### 第 89 次发布

发布时间:2024-06-20 02:34:10

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-
[DescribeAccessFastAnalysis](https://cloud.tencent.com/document/api/627/60014)

    -   <font color="#dd0000">**修改入参**:</font>TopicId

    -   新增出参:FieldValueRatioInfos, TotalCount

新增数据结构:

-
[AccessFieldValueRatioInfo](https://cloud.tencent.com/document/api/627/53609#AccessFieldValueRatioInfo)

#### 数据开发治理平台 WeData(wedata) 版本:2021-08-20

##### 第 97 次发布

发布时间:2024-06-20 02:35:45

本次发布包含了以下内容:

改善已有的文档。

修改接口:

-   [DiagnosePro](https://cloud.tencent.com/document/api/1267/105332)

    -   <font color="#dd0000">**修改入参**:</font>SearchCondition, ProjectId

修改数据结构:

-
[TaskAlarmInfo](https://cloud.tencent.com/document/api/1267/76336#TaskAlarmInfo)

    -   新增成员:DingDingWebHooks

###
[`v1.0.945`](https://togithub.com/tencentcloud/tencentcloud-sdk-go/blob/HEAD/CHANGELOG.md#Release-v10945)

[Compare
Source](https://togithub.com/tencentcloud/tencentcloud-sdk-go/compare/v1.0.944...v1.0.945)

#### 云安全一体化平台(csip) 版本:2022-11-21

##### 第 39 次发布

发布时间:2024-06-19 01:24:50

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[DescribeVULRiskDetail](https://cloud.tencent.com/document/api/664/107483)
-
[DescribeVulViewVulRiskList](https://cloud.tencent.com/document/api/664/107482)

新增数据结构:

-
[VULRiskInfo](https://cloud.tencent.com/document/api/664/90825#VULRiskInfo)
-
[VULViewVULRiskData](https://cloud.tencent.com/document/api/664/90825#VULViewVULRiskData)
-
[VulImpactComponentInfo](https://cloud.tencent.com/document/api/664/90825#VulImpactComponentInfo)
- [VulTrend](https://cloud.tencent.com/document/api/664/90825#VulTrend)

#### 全球应用加速(gaap) 版本:2018-05-29

##### 第 45 次发布

发布时间:2024-06-19 01:43:58

本次发布包含了以下内容:

改善已有的文档。

修改数据结构:

-
[DomainRuleSet](https://cloud.tencent.com/document/api/608/37023#DomainRuleSet)

    -   新增成员:TLSCiphers, TLSSupportVersion

#### 数据开发治理平台 WeData(wedata) 版本:2021-08-20

##### 第 96 次发布

发布时间:2024-06-19 02:35:11

本次发布包含了以下内容:

改善已有的文档。

新增接口:

-
[MoveTasksToFolder](https://cloud.tencent.com/document/api/1267/107484)

修改数据结构:

-
[OpsTaskCanvasInfoList](https://cloud.tencent.com/document/api/1267/76336#OpsTaskCanvasInfoList)

    -   <font color="#dd0000">**修改成员**:</font>CirculateTaskList

</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:eyJjcmVhdGVkSW5WZXIiOiIzNy40MTMuMiIsInVwZGF0ZWRJblZlciI6IjM3LjQxMy4yIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJyZW5vdmF0ZWJvdCJdfQ==-->

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: opentelemetrybot <[email protected]>
Co-authored-by: Yang Song <[email protected]>
**Description:** Fix a broken URL in a comment
The wiki on how to track tool dependencies for a module has moved.
…-telemetry#33297)

**Description:**
Add a feature gate `connector.datadogconnector.NativeIngest` that
enables datadog connector to use the new native OTel API in APM stats
computation. It is disabled by default.

Follow-up of DataDog/datadog-agent#23503.

---------

Co-authored-by: Pablo Baeyens <[email protected]>
… exporter (open-telemetry#32998)

**Description:** 
Cherry-picking from downstream:
amazon-contributing#105

This PR adds AppSignals metadata flag in user-agent in EMF exporter, so
CWLogs backend can indicate EMF logs request type for the corresponding
actions

---------

Co-authored-by: Min Xia <[email protected]>
Co-authored-by: Jeffrey Chien <[email protected]>
Co-authored-by: Vastin <[email protected]>
… sumo exporter (open-telemetry#33604)

**Description**:

Switched to use compression from client config, [compress_encdoing is
deprecated](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/fc363988211d90ee2ae7c75eda6ce90c04bae868/exporter/sumologicexporter/config.go#L31),
so removing from exporter.

Link to tracking Issue:
-
open-telemetry#33138

**Testing**:

Unit test

**Documentation**:

chloggen
**Description:** <Describe what has changed.> This PR adds an initial
implementation for the MaxMind GeoIP provider for later usage in the
`geoipprocessor`. The processor is still a nop, as no provider can be
configured yet. Providers configuration will be added in
open-telemetry#33268.

- Internal package for temporal attributes conventions reference (should
be removed in favor of
open-telemetry/semantic-conventions#1116):
`processor/geoipprocessor/internal/convention/attributes.go`
- [geoip2-golang](https://github.com/oschwald/geoip2-golang) package
used as a client for data retrieval. See recommended MaxMind clients:
https://dev.maxmind.com/geoip/docs/databases#api-clients

**Link to tracking Issue:** <Issue number if applicable>
open-telemetry#32663

**Testing:** <Describe what testing was performed and which tests were
added.> Database files are generated before running the unit tests
[using MaxMind
writer.](https://github.com/maxmind/MaxMind-DB/tree/0a9c1aa26cd7b91bee2efe27e7d174797d8211a6/test-data#how-to-generate-test-data).
The generation time of those files seems not to be an issue (0.189s):

```
$ go test -v
=== RUN   TestInvalidNewProvider
--- PASS: TestInvalidNewProvider (0.00s)
=== RUN   TestProviderLocation
=== PAUSE TestProviderLocation
=== CONT  TestProviderLocation
=== RUN   TestProviderLocation/nil_IP_address
=== RUN   TestProviderLocation/unsupported_database_type
=== RUN   TestProviderLocation/no_IP_metadata_in_database
=== RUN   TestProviderLocation/all_attributes_should_be_present_for_IPv4_using_GeoLite2-City_database
=== RUN   TestProviderLocation/subset_attributes_for_IPv6_IP_using_GeoIP2-City_database
--- PASS: TestProviderLocation (0.00s)
    --- PASS: TestProviderLocation/nil_IP_address (0.00s)
    --- PASS: TestProviderLocation/unsupported_database_type (0.00s)
    --- PASS: TestProviderLocation/no_IP_metadata_in_database (0.00s)
    --- PASS: TestProviderLocation/all_attributes_should_be_present_for_IPv4_using_GeoLite2-City_database (0.00s)
    --- PASS: TestProviderLocation/subset_attributes_for_IPv6_IP_using_GeoIP2-City_database (0.00s)
PASS
ok  	github.com/open-telemetry/opentelemetry-collector-contrib/processor/geoipprocessor/internal/provider/maxmindprovider	0.189s
```

Testing database files are removed on sucessful test execution.

**Documentation:** <Describe the documentation added.> README.md file
…nv (open-telemetry#33572)

**Description:** 
The observer extension currently only exposes `endpoint` in its endpoint
environment that is made available to the receiver creator for
dynamically configuring receivers. Some receivers require `host` and
`port` to be configured separately, so `endpoint` containing both is
incompatible with those receivers. Exposing these independently allows
the receiver creator to be compatible with those receivers.

**Link to tracking Issue:**
Resolves open-telemetry#33571
…eta (open-telemetry#33658)

**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.-->

Counterpart to open-telemetry/opentelemetry-collector/pull/10352.

**Link to tracking Issue:**
open-telemetry/opentelemetry-collector/issues/8510
…etry#33005)

**Description:** Add support for k8s.ingress endpoint

As described in the issue, this will allow users to dynamically obtain
Kubernetes ingress ressource, facilitating the monitoring of certificate
expiration with the Blackbox Exporter for example.
I didn't create a global ingress resource with sub-endpoints for each
path because I don't see a relevant 'target'. I'm uncertain about the
impact of my decision regarding the 'UID' as it's structured as
'{namespace}/{ingress UID}/{host}{path}'. Since a path automatically
starts with a '/', and can contain other '/', should I escape them ?

**Link to tracking Issue:** <Issue number if applicable>
open-telemetry#32971

---------

Signed-off-by: Ludovic Ortega <[email protected]>
Co-authored-by: Chris Mark <[email protected]>
…of creating it for each batch (open-telemetry#33643)

**Description:** 
Refactored sender to be created once and reused instead of creating a
new sender each batch.

**Link to tracking Issue:**
-
open-telemetry#33105
- jira: https://sumologic.atlassian.net/browse/OSC-751 

**Testing:** 

- Unit test passed 

**Documentation:**
- chloggen
**Description:**

Deprecate `exporter/elasticsearch`'s "dedup" configuration. In a future
release we will remove this configuration, and always deduplicate
wherever necessary.

**Link to tracking Issue:**


open-telemetry#33773

**Testing:**

N/A

**Documentation:**

Updated the README.
…elemetry#33774)

**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.-->
This PR changes the system resource detector so as to only try to fetch
the CPU info when required. The CPU info attributes are disabled by
default so we should only fetch this information when at least one of
those is enabled.

**Link to tracking Issue:** <Issue number if applicable>
open-telemetry#33768

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

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

/cc @mx-psi

---------

Signed-off-by: ChrsMark <[email protected]>
**Description:**

Deprecate `exporter/elasticsearch`'s "dedot" configuration. In a future
release we will remove this configuration, and always dedot ECS mode,
never for raw/none modes.

**Link to tracking Issue:**


open-telemetry#33772

**Testing:**

N/A

**Documentation:**

Updated the README.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.