-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[libbeat] : add processors "decode_duration", "move_fields" #31301
Conversation
💚 CLA has been signed |
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
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.
@kunsonx Are you still working on this PR? On a quick glance it looks fine, but it's missing tests and documentation.
Could you request a re-review once you're done with coding?
OK. I will finish this works. Should I close this MR and open again when it's done? BTW Where is the guideline for write tests and documentation? I am beginner for this project contribute. |
No need to close/open another PR, just make sure to use the re-review request button once you're done so I get notified and can start reviewing. You can check the contributing docs here: https://www.elastic.co/guide/en/beats/devguide/current/beats-contributing.html, there you will also find information regarding tests and documentation. If you still need something more specific, then try looking how the other processors implement their tests and documentation. |
@belimawr Hi. I finished the Thanks for your time. |
Hey @kunsonx I can already see some linters are failing, could you take a look at them? They're quite strict, so don't be dismayed by it. Usually it takes some iterations until all linter passes. To run it locally, go the root of the repo and run
You will have to fix all lint issues in the files you changed (not only the lines you added). Because we added this linter recently, sometimes we have to ask the linter to ignore some lines/functions with a |
I'm closing it because there hasn't been any updated in a while. @kunsonx, if you still want to work on this, just re-open the PR and push the new commits ;) |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
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.
Great Job!
I added some comments regarding the implementation and some documentation copy. I'll also try to get another reviewer at least for the docs.
libbeat/processors/decode_duration/docs/decode_duration.asciidoc
Outdated
Show resolved
Hide resolved
@dedemorton Thanks for your suggestions it make the docs better. Still has two suggestion here need more helps. 😀 |
@dedemorton could you take another look/help out here? |
@dedemorton Have any idea about the pull request? |
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.
The changes LGTM!
@kunsonx could you update the PR with There were some big changes in the codebase recently, but they should not affect this PR. |
Co-authored-by: DeDe Morton <[email protected]>
Co-authored-by: DeDe Morton <[email protected]>
Done. |
@belimawr Seems had two reviewers approved this pull request. so what is next? |
I've added the backport label to make sure this gets into the next release. It sounds like this is ready to merge! |
Co-authored-by: hxms <[email protected]> Co-authored-by: DeDe Morton <[email protected]> (cherry picked from commit dc1a0ca)
Merge and wait for it to land in the next release ;) Thanks a lot for the contribution! |
I was reviewing the backport and realised we missed the changelog entry 🤦♂️ @kunsonx would you mind creating a new PR adding the changelog entry? You can tag me to review it. |
…3700) Co-authored-by: hxms <[email protected]> Co-authored-by: DeDe Morton <[email protected]> (cherry picked from commit dc1a0ca) Co-authored-by: 冰天雪地 <[email protected]> Co-authored-by: Denis <[email protected]> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: hxms <[email protected]> Co-authored-by: DeDe Morton <[email protected]>
What does this PR do?
Ability to manipulate log fields.
Why is it important?
Give users ability custom log field operations.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs