-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[processor/k8sattributes] Automatic resource attributes #37114
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
Closed
zeitlinger
wants to merge
27
commits into
open-telemetry:main
from
zeitlinger:operator-resource-attributes
Closed
Changes from all commits
Commits
Show all changes
27 commits
Select commit
Hold shift + click to select a range
1021e4e
automatically set service instance id
zeitlinger 4bee42d
automatically set service instance id
zeitlinger a5e6ddc
automatically set service instance id
zeitlinger 8b3196f
automatically set service instance id
zeitlinger a9bb403
add label rules, test annotation override
zeitlinger 02c50e8
add service version
zeitlinger 0e1aeb0
automatically set service name
zeitlinger 575b8d9
automatically set service name
zeitlinger 74b9b1a
automatically set service name
zeitlinger 109c985
automatically set service name
zeitlinger fa8ede3
automatically set service name
zeitlinger 18143ad
lint
zeitlinger 1a3372e
add changelog entry
zeitlinger abdd9ec
add docs
zeitlinger b0a0e07
part-of is not part of semconv
zeitlinger 529df25
add app.kubernetes.io/instance
zeitlinger 1029b1e
update service.version
zeitlinger e59e647
add app.kubernetes.io/instance
zeitlinger 7a66579
rename
zeitlinger ccaf3fe
fix merge, revert implicit "enabled: true"
zeitlinger 0560d17
custom prefixes
zeitlinger dec8a07
add, customizations and missing namespace rule
zeitlinger 8f3afb6
add, customizations and missing namespace rule
zeitlinger 890ed61
add, customizations and missing namespace rule
zeitlinger 387ebca
format
zeitlinger 43e39fa
format
zeitlinger c30d1ed
format
zeitlinger File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
change_type: enhancement | ||
|
||
component: k8sattributesprocessor | ||
|
||
note: Add option to configure resource attributes using the same logic as the OTel operator | ||
|
||
issues: [37114] | ||
|
||
subtext: | | ||
If you are using the file log receiver, you can now create the same resource attributes as traces (via OTLP) received | ||
from an application instrumented with the OpenTelemetry Operator - | ||
simply by adding the `extract: { automatic_attributes: { enabled: true }}` configuration to the `k8sattributesprocessor` processor. | ||
See the [documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/k8sattributesprocessor/README.md#config-example) for more details. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Can we just move well known attributes from this section to where all the other pre-defined resource attributes are configured
extract.metadata
, and disabled by default?Then this section would be responsible for taking resource attributes from annotations only. Instead of calling it
automatic_attributes
, it can be something likeThen, if we want to provide flexibility for annotations extraction, we could add
extract.annotations
with the same syntax as we currently have forextract.labels
. That is not really needed right now.Providing such interface would be consistent with the existing one and easier to understand by the end users. Please let me know WDYT.