-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[processor/transform] Write log if truncation or limiting is performed #9730
Comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
The functions now support logging so this issue can be worked. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Any functions in the transform processor that truncate or limit attributes should write out a log, following the specification. Currently there are 2 functions,
truncate_all
andlimit
that do this. Those functions, and any functions added in the future, should be able to write a log once per record on which the function was performed.Additional context
Originated from comment in #9552. The functionality was not originally added as part of the
truncate_all
andlimit
PRs due to the lack of a logger infunctions.go
. I experimented with print statements, which probably could work, but I think using an actualzap.logger
is the proper solution.The text was updated successfully, but these errors were encountered: