Skip to content
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

Osquerybeat: Upgrade to osquery 5.10.2 #37115

Merged
merged 5 commits into from Nov 15, 2023

Conversation

aleksmaus
Copy link
Member

What does this PR do?

Upgrade to osquery 5.10.2.
Upgrade osquery-go client library to the latest.

Why is it important?

Picking up the latest osquery release.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas

Screenshots

Screenshot 2023-11-13 at 4 18 45 PM

@aleksmaus aleksmaus requested review from a team as code owners November 13, 2023 21:23
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 13, 2023
Copy link
Contributor

mergify bot commented Nov 13, 2023

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @aleksmaus? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@elasticmachine
Copy link
Collaborator

elasticmachine commented Nov 14, 2023

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-11-14T23:08:17.917+0000

  • Duration: 174 min 44 sec

Test stats 🧪

Test Results
Failed 0
Passed 28702
Skipped 2015
Total 30717

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@pierrehilbert
Copy link
Collaborator

Do we have something we want to highlight in the changelog?

Copy link

@tomsonpl tomsonpl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀 Thank you for doing this Aleks 🙇

@aleksmaus
Copy link
Member Author

Do we have something we want to highlight in the changelog?

Updated the changelog

@aleksmaus aleksmaus merged commit 0f65629 into elastic:main Nov 15, 2023
115 checks passed
aleksmaus added a commit to elastic/kibana that referenced this pull request Nov 15, 2023
## Summary

Update exported fields reference for osquery 5.10.2.

## Related PR

- Requires elastic/beats#37115
- Requires elastic/integrations#8488
jillguyonnet pushed a commit to jillguyonnet/kibana that referenced this pull request Nov 16, 2023
…#171147)

## Summary

Update exported fields reference for osquery 5.10.2.

## Related PR

- Requires elastic/beats#37115
- Requires elastic/integrations#8488
Scholar-Li pushed a commit to Scholar-Li/beats that referenced this pull request Feb 5, 2024
* Osquerybeat: Upgrade to osquery 5.10.2

* Update changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-skip Skip notification from the automated backport with mergify >enhancement Team:Asset Mgt v8.12.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants