-
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
Update 8.x from main #40719
Merged
Merged
Update 8.x from main #40719
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…_cluster metricset (#40634) * initial commit for datastore cluster * mage update * update: - data.json - field.yml * doc updates * datastore_cluster -> datastorecluster * resolve review comments * fix UTs * update URL for UTs * update UTs * fix field mapping * update data.json
…0661) * log total time taken for ListTimeSeries requests * add changelog entry * fix PR id * log total time taken for AggregatedList request * update changelog entry * remove log * Update x-pack/metricbeat/module/gcp/metrics/compute/metadata.go Co-authored-by: subham sarkar <[email protected]> * Update x-pack/metricbeat/module/gcp/metrics/metrics_requester.go Co-authored-by: subham sarkar <[email protected]> * Update x-pack/metricbeat/module/gcp/metrics/compute/metadata.go Co-authored-by: Harnish Chavda <[email protected]> * Update x-pack/metricbeat/module/gcp/metrics/metrics_requester.go Co-authored-by: Harnish Chavda <[email protected]> --------- Co-authored-by: subham sarkar <[email protected]> Co-authored-by: Harnish Chavda <[email protected]>
To fix the failing linter rule that requires OSS code to not depend on x-pack code, this change removes the dependency on x-pack/dockerlogbeat/pipelinemock from the Filebeat filestream input. It does this by creating a mock client that is local to filestream test code ("A little copying is better than a little dependency"). Fixes #40293
* [Packetbeat] Fix Packetbeat parsing mongodb OP_MSG * Fixes handling OP_MSG based request/response, missing "end" timestamp and "duration" field for the event
Adding required dependencies to run Synthetics to Wolfi-based heartbeat images, from wolfi-os package manager.
* refactor fleet mode detection and storage
CEL programs used in the CEL input are specific to return an object that includes an array. This is tested for, but currently the check is indirect and only shows that the type is not expected, rather than a more informative message that the events array is missing. This changes that so that when no events field is present, an error is returned directly. This will flow on to a status update in the handling of the returned error by the input Run method, alerting the user more promptly to the cause. Since a CEL input program is not valid if it returns no events field, a hard error (fleet status failed rather than degraded) seems appropriate.
* Fix windows test pipeline by reflecting browser monitor build constraints in the include file
* Add support of snapshot in virtualmachine * mage update and add fields.yml * Update data_test.go * address comments, mage update * Lint error * Add createtime * Update CHANGELOG.next.asciidoc * Add state and id for snapshot * update changelog * lint change * lint change
Co-authored-by: Craig MacKenzie <[email protected]> (cherry picked from commit fff09dc) Co-authored-by: elastic-vault-github-plugin-prod[bot] <150874479+elastic-vault-github-plugin-prod[bot]@users.noreply.github.com> Co-authored-by: Julien Lind <[email protected]>
* New images with `-wolfi` suffix get created * Wolfi is used for preparing the file structure for Docker images
…_cluster metricset (#40694) * initial commit * add childEntity * add changelog entry * resolve review comments
* Remove extra debug messages --------- Signed-off-by: constanca <[email protected]>
* refactor: consistently use one uuid library the codebase is using a mix of github.com/google/uuid and github.com/gofrs/uuid Update the codebase to use github.com/gofrs/uuid consistently and bump to the current major version. * lint: fix linting issues * refactor: move to gofrs/uuid * lint: add gomodguard setting * lint: fix more linter issues * lint: more linting errors * lint: completely remove gofrs/uuid v4 * lint: more linting errors * lint: more linting errors * lint: fix more linting errors * fix: replace uuid.MustParse with uuid.Must(uuid.FromString()) * refactor: update uuid.Parse to uuid.FromString * lint: fix linting errors * lint: fix linting errors * docs: fix nolint comments * lint: fix linting errors * docs: update nolint comments * test: update uuid parsing err * lint: fix linter issues * lint: fix linter issues * lint: run go mod tidy * lint: regenerate notice * build: regenerate notice * build: regenerate notice * refactor: cleanup double uuid conversion * test: gracefully log the error
…0692) * Add option to prevent new session creation and pre-create cached sessions
Co-authored-by: Julien Lind <[email protected]>
* Automatically label PRs to `main` with `backport-8.x` When the `main` branch switches over to `9.0`, we will want most PRs that are merged into `main` to also be backported to `8.x`. This PR makes this process easier by automatically adding the `backport-8.x` label to all PRs targeting the `main` branch. The exceptions will be PRs for changes that should _only_ be present in `9.0`. For such PRs, authors should simply remove the `backport-8.x` label from their PR. * Fix typo in comment * Add missing v prefix to label for consistent with backport PR rule
botelastic
bot
added
the
needs_team
Indicates that the issue/PR needs a Team:* label
label
Sep 10, 2024
jlind23
requested review from
belimawr,
leehinman,
gizas and
constanca-m
and removed request for
a team
September 10, 2024 07:16
This pull request doesn't have a |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update 8.X with all the latest changes from main except the 9.X bump