-
Notifications
You must be signed in to change notification settings - Fork 238
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
Upgrade to OTel v0.116.0 #2314
base: main
Are you sure you want to change the base?
Upgrade to OTel v0.116.0 #2314
Conversation
💻 Deploy preview available: https://deploy-preview-alloy-2314-zb444pucvq-vp.a.run.app/docs/alloy/latest/ |
The `regex` argument is deprecated and may be removed in upcoming versions. | ||
Use the [ExtractPatterns](extract-patterns) function from `otelcol.processor.transform` instead. | ||
|
||
[extract-patterns]: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/{{< param "OTEL_VERSION" >}}/pkg/ottl/ottlfuncs/README.md#extractpatterns |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@clayton-cornell This link doesn't seem to work, but I don't know why. It's almost identical to a similar link in the otelcol.processor.transform
doc. Any ideas why this is?
The same link is also present in the next section btw.
{{< admonition type="warning" >}} | ||
|
||
The `regex` argument is deprecated and may be removed in upcoming versions. | ||
Use the [ExtractPatterns](extract-patterns) function from `otelcol.processor.transform` instead. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use the [ExtractPatterns](extract-patterns) function from `otelcol.processor.transform` instead. | |
Use the [ExtractPatterns][extract-patterns] function from `otelcol.processor.transform` instead. |
PR Description
Upgrading to the latest version of OTel.
Community components
Pinging community component owners:
otelcol.exporter.splunkhec
: @adlotsof, @PatMis16.otelcol.exporter.datadog
: @polyrain.Please feel free to open a PR to update the community components :) There have been a few minor changes to the upstream code. You could either merge to my PR, or wait for my PR to be merged and then to merge yours to
main
. It is not necessary to update the community components for v1.6, since the upstream changes are not that big. If you decide to not update them at all with the latest changes, that's ok too.Which issue(s) this PR fixes
Fixes #2255
Fixes #2243
PR Checklist