-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[processor/resourcedetectionprocessor] Expose Azure resource tags #32953
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
Changes from 5 commits
3e1f7a1
785ed35
92b19af
dbffdbf
aa887a6
8d97230
82f87e0
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
# Use this changelog template to create an entry for release notes. | ||
|
||
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix' | ||
change_type: 'enhancement' | ||
|
||
# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver) | ||
component: processor/resourcedetectionprocessor | ||
|
||
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`). | ||
note: Add support for Azure tags in ResourceDetectionProcessor. | ||
|
||
# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists. | ||
issues: [32953] | ||
|
||
# (Optional) One or more lines of additional information to render under the primary note. | ||
# These lines will be padded with 2 spaces and then inserted directly into the document. | ||
# Use pipe (|) for multiline entries. | ||
subtext: | ||
|
||
# If your change doesn't affect end users or the exported elements of any package, | ||
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label. | ||
# Optional: The change log or logs in which this entry should be included. | ||
# e.g. '[user]' or '[user, api]' | ||
# Include 'user' if the change is relevant to end users. | ||
# Include 'api' if there is a change to a library API. | ||
# Default: '[user]' | ||
change_logs: [user] |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -390,6 +390,26 @@ processors: | |
override: false | ||
``` | ||
|
||
It also can optionally gather tags from the azure instance that the collector is running on. | ||
|
||
Azure custom configuration example: | ||
|
||
```yaml | ||
processors: | ||
resourcedetection/azure: | ||
detectors: ["azure"] | ||
azure: | ||
# A list of regex's to match tag keys to add as resource attributes can be specified | ||
tags: | ||
- ^tag1$ | ||
- ^tag2$ | ||
- ^label.*$ | ||
Comment on lines
+403
to
+406
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is just adding all tags acceptable in terms of performance and number? i.e. Do Azure instances typically have a lot of tags? Asking because I would like to keep it simple: if you want to filter, you can do that in a different component in your pipeline like the transform processor There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Azure supports a max of 50 tags per resource, how many are actually in use of course varies depending on people's use cases. When implementing this I decided to keep it aligned with how the AWS implementation was exposed to users. The thought there was if someone is in a multi-cloud environment having them both configured the same, makes it easier for them to be used but I am not glued to that implementation choice. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks for the detailed reply! I agree it's valuable to be aligned with the AWS detector. I guess we can always add an 'add all of them' setting if needed. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. You're welcome. As for the And CLA is finally signed. There was a hiccup on our side. |
||
``` | ||
|
||
Matched tags are added as: | ||
|
||
* azure.tags.<tag name> | ||
|
||
### Azure AKS | ||
|
||
* cloud.provider ("azure") | ||
|
Uh oh!
There was an error while loading. Please reload this page.