-
Notifications
You must be signed in to change notification settings - Fork 389
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 target_format
property to the Logs attribute remapper
#682
Conversation
7c27806
to
d89bc5a
Compare
target_format
property to the Logs attribute remapper
-> target_format have to be lowercase
18c1b10
to
a283a89
Compare
a283a89
to
9fdb263
Compare
2972184
to
0abc246
Compare
@@ -185,6 +186,7 @@ The following arguments are supported: | |||
- `source_type`: (Required) Defines where the sources are from (log `attribute` or `tag`). | |||
- `target`: (Required) Final `attribute` or `tag` name to remap the sources. | |||
- `target_type`: (Required) Defines if the target is a log `attribute` or `tag`. | |||
- `target_format`: (Optional) If the target of the remapper is an attribute, try to cast the value to a new specific type. If the cast is not possible, the original type is kept. `string`, `integer`, or `double` are the possible types. |
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.
Maybe you can make it more explicit that users should only set the target_format if the target_type is an attribute. It's already said, but for this kind of valid / invalid values it's better to be super explicit and not being afraid of being repetitive.
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.
thank you for pointing this out
d47f20e
to
8649967
Compare
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.
Looks good, some minor doc changes. Thanks!
- `preserve_source`: (Optional, default = false) Remove or preserve the remapped source element. | ||
- `override_on_conflict`: (Optional, default = false) Override the target element if already set. | ||
- `name`: (Optional) Name of the processor | ||
- `is_enabled`: (Optional, default = false) If the processor is enabled or not. | ||
- category_processor | ||
- `target`: (Required) Name of the target attribute whose value is defined by the matching category. | ||
- `target`: (Required) Name of the target attribute whose value is defined by the matching category.` |
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.
Looks like an unintended change?
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.
yes thanks 👌
8649967
to
0d3f676
Compare
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
Any idea when this might be released? This feature is exactly what I was hunting for in the docs. |
Hello, we'll release in the next few weeks. |
Add target_format to attribute remapper
related to PR