[main][Automation] Update elastic/beats to 00068f79631b - #2
Open
github-actions[bot] wants to merge 57 commits into
Open
github-actions[bot] wants to merge 57 commits into
github-actions[bot] wants to merge 57 commits into
Conversation
github-actions
Bot
added
automation
skip-changelog
Team:Elastic-Agent-Control-Plane
labels
github-actions
Bot
force-pushed
the
update-beats-main
branch
from
January 23, 2026 01:25
bb44061 to
e0bd27e
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
from
January 27, 2026 01:30
e0bd27e to
858a89c
Compare
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
2 times, most recently
from
January 29, 2026 01:48
0c5e100 to
40890ad
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
from
January 30, 2026 01:48
40890ad to
770d4d0
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
from
February 2, 2026 01:55
770d4d0 to
586580d
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
from
February 3, 2026 01:54
586580d to
112a403
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
from
February 4, 2026 01:49
112a403 to
6e7085a
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
from
February 5, 2026 01:51
6e7085a to
5e622eb
Compare
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
from
February 6, 2026 01:50
5e622eb to
b2a1116
Compare
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
2 times, most recently
from
February 10, 2026 02:08
59d429a to
4212820
Compare
github-actions
Bot
changed the title
github-actions
Bot
changed the title
github-actions
Bot
force-pushed
the
update-beats-main
branch
2 times, most recently
from
February 12, 2026 01:56
fdd46b7 to
8ee536b
Compare
* Update packaging * Regenerate mocks --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* chore: Update all Buildkite pipeline files (GCP/AWS) Made with ❤️️ by updatecli * chore: Update all Buildkite pipeline files (Azure) Made with ❤️️ by updatecli --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: navyau09 <119856217+navyau09@users.noreply.github.com>
…ic#15602) * Expand ES exporter auth and TLS documentation * Address Carson's comments * docs: fix navigation title and add version note for 9.5 Collector rename Add rename note on the Collector landing page, update navigation_title to "OpenTelemetry", and fix remaining "EDOT Collector" references in newly-added content blocks. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Apply PR review suggestions --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
…tic#16329) * Fix flaky TestPolicyReassignWithTamperProtectedEndpoint cleanup Re-fetch the policy 2 uninstall token after endpoint confirms the new policy is active (getEndpointPolicyID returns a different ID). The earlier fetch happens before reassignment; on slow infrastructure endpoint can update its policy.id field before persisting the new tamper-protection hash, so the pre-reassignment token is stale and elastic-endpoint uninstall fails with "Invalid uninstall token". The second addEndpointCleanup (registered last, runs first via LIFO) uses the fresh token. If it succeeds the earlier cleanup is a no-op because the endpoint binary is already gone. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * Fix linter warnings --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
* fix(test): wait for non-empty JSON record in TestSystemMetricsWithLogstashOutput Logstash's file output plugin creates the output file before writing the first record. The previous poll condition only checked file existence, so the test could read an empty file in the narrow window between file creation and the first write. Move the read and parse inside the EventuallyWithTf callback and retry until a valid JSON object is present, preventing the silent nil result that caused downstream key-comparison failures. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * remove unused downloadData function Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: alexandra5000 <96738481+alexandra5000@users.noreply.github.com>
…lastic#16337) Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>
These files are used for picking the starting (pre-upgrade) or ending (post-upgrade) agent versions in upgrade integration tests. The content is based on responses from https://www.elastic.co/api/product_versions and https://snapshots.elastic.co The current update is generated based on the following requirements: `.package-version` ```json { "version": "9.6.0-SNAPSHOT", "build_id": "9.6.0-2dfcb053", "manifest_url": "https://snapshots.elastic.co/9.6.0-2dfcb053/manifest-9.6.0-SNAPSHOT.json", "summary_url": "https://snapshots.elastic.co/9.6.0-2dfcb053/summary-9.6.0-SNAPSHOT.html", "core_version": "9.6.0", "stack_version": "9.6.0-SNAPSHOT", "stack_build_id": "9.6.0-2dfcb053-SNAPSHOT" } ``` `testing/integration/testdata/.upgrade-test-agent-versions.yml` ```json { "UpgradeToVersion": "9.6.0", "CurrentMajors": 1, "PreviousMajors": 2, "PreviousMinors": 2, "SnapshotBranches": [ "9.5", "9.4", "8.19" ] } ``` Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Add `timeout` mapping in output_elasticsearch.go so the ES exporter's timeoutInterceptor receives a non-zero value — when timeout=0 is passed, context.WithTimeout immediately cancels every request. Use the beats transport timeout (default 90s) as the source of truth. Replace removed xconfmap.Validate with confmap.Validate in beatsauth_test.go (xconfmap.Validate was dropped in confmap/xconfmap v0.159.0). Move go.opentelemetry.io/collector/confmap/xconfmap to indirect in go.mod since it is no longer imported directly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
These files are used for picking the starting (pre-upgrade) or ending (post-upgrade) agent versions in upgrade integration tests. The content is based on responses from https://www.elastic.co/api/product_versions and https://snapshots.elastic.co The current update is generated based on the following requirements: `.package-version` ```json { "version": "9.6.0-SNAPSHOT", "build_id": "9.6.0-336c7e6a", "manifest_url": "https://snapshots.elastic.co/9.6.0-336c7e6a/manifest-9.6.0-SNAPSHOT.json", "summary_url": "https://snapshots.elastic.co/9.6.0-336c7e6a/summary-9.6.0-SNAPSHOT.html", "core_version": "9.6.0", "stack_version": "9.6.0-SNAPSHOT", "stack_build_id": "9.6.0-336c7e6a-SNAPSHOT" } ``` `testing/integration/testdata/.upgrade-test-agent-versions.yml` ```json { "UpgradeToVersion": "9.6.0", "CurrentMajors": 1, "PreviousMajors": 2, "PreviousMinors": 2, "SnapshotBranches": [ "9.5", "9.4", "8.19" ] } ``` Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Bulk-bump all opentelemetry-collector-contrib packages from v0.157.0 to v0.159.0 in both go.mod and internal/edot/go.mod. This resolves the packaging build failure caused by xconfmap.Validator/Validate being removed in xconfmap v0.159.0 — packages still at v0.157.0 referenced the removed symbols once MVS selected v0.159.0 to satisfy the ES exporter requirement. Also bump confmap/provider/httpsprovider from v1.63.0 to v1.65.0 in internal/edot/go.mod to align all core OTel collector deps at v1.65.x. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…n elastic-otel-collector The elastic-otel-collector binary uses the beatprocessor OTel component which supports add_docker_metadata and add_kubernetes_metadata, but these processors register themselves via init() and were never imported by the edot binary. Add a platform-specific imports file so their init() runs on startup. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Prevent renovate from updating internal cross-module imports of the root elastic-agent module.
These files are used for picking the starting (pre-upgrade) or ending (post-upgrade) agent versions in upgrade integration tests. The content is based on responses from https://www.elastic.co/api/product_versions and https://snapshots.elastic.co The current update is generated based on the following requirements: `.package-version` ```json { "version": "9.6.0-SNAPSHOT", "build_id": "9.6.0-73daec83", "manifest_url": "https://snapshots.elastic.co/9.6.0-73daec83/manifest-9.6.0-SNAPSHOT.json", "summary_url": "https://snapshots.elastic.co/9.6.0-73daec83/summary-9.6.0-SNAPSHOT.html", "core_version": "9.6.0", "stack_version": "9.6.0-SNAPSHOT", "stack_build_id": "9.6.0-73daec83-SNAPSHOT" } ``` `testing/integration/testdata/.upgrade-test-agent-versions.yml` ```json { "UpgradeToVersion": "9.6.0", "CurrentMajors": 1, "PreviousMajors": 2, "PreviousMinors": 2, "SnapshotBranches": [ "9.5", "9.4", "8.19" ] } ``` Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…elastic#16359) * [beatreceiver] Set compression level only when kafka output is set * add chanheloh * Add test
The dynamic inputs runtime override (agent.internal.runtime.dynamic_inputs) previously accepted a single runtime name and moved every component with inputs rendered from a dynamic variable provider off the otel runtime. To allow finer control for testing and benchmarking: - The override runtime can now be set per beat and per input type, with the same precedence scheme as the general runtime configuration. The legacy scalar form keeps working and maps to the top-level default. - A new static_variables list excludes provider variables that cannot change at runtime (e.g. kubernetes.node.name): an input is only treated as dynamic if it resolved at least one provider variable not covered by the list. The variables each input resolves are recorded during rendering and logged at debug level for introspection. Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* Add local stack provisioner * Fix linter warnings * update docs * review fixes
The two beats and elastic-agent exclusions are intended for all modules from those repositories.
These files are used for picking the starting (pre-upgrade) or ending (post-upgrade) agent versions in upgrade integration tests. The content is based on responses from https://www.elastic.co/api/product_versions and https://snapshots.elastic.co The current update is generated based on the following requirements: `.package-version` ```json { "version": "9.6.0-SNAPSHOT", "build_id": "9.6.0-de2c51e0", "manifest_url": "https://snapshots.elastic.co/9.6.0-de2c51e0/manifest-9.6.0-SNAPSHOT.json", "summary_url": "https://snapshots.elastic.co/9.6.0-de2c51e0/summary-9.6.0-SNAPSHOT.html", "core_version": "9.6.0", "stack_version": "9.6.0-SNAPSHOT", "stack_build_id": "9.6.0-de2c51e0-SNAPSHOT" } ``` `testing/integration/testdata/.upgrade-test-agent-versions.yml` ```json { "UpgradeToVersion": "9.6.0", "CurrentMajors": 1, "PreviousMajors": 2, "PreviousMinors": 2, "SnapshotBranches": [ "9.5", "9.4", "8.19" ] } ``` Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
These files are used for picking the starting (pre-upgrade) or ending (post-upgrade) agent versions in upgrade integration tests. The content is based on responses from https://www.elastic.co/api/product_versions and https://snapshots.elastic.co The current update is generated based on the following requirements: `.package-version` ```json { "version": "9.6.0-SNAPSHOT", "build_id": "9.6.0-edd9776a", "manifest_url": "https://snapshots.elastic.co/9.6.0-edd9776a/manifest-9.6.0-SNAPSHOT.json", "summary_url": "https://snapshots.elastic.co/9.6.0-edd9776a/summary-9.6.0-SNAPSHOT.html", "core_version": "9.6.0", "stack_version": "9.6.0-SNAPSHOT", "stack_build_id": "9.6.0-edd9776a-SNAPSHOT" } ``` `testing/integration/testdata/.upgrade-test-agent-versions.yml` ```json { "UpgradeToVersion": "9.6.0", "CurrentMajors": 1, "PreviousMajors": 2, "PreviousMinors": 2, "SnapshotBranches": [ "9.5", "9.4", "8.19" ] } ``` Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* fix(deps): update tooling-test * Update EDOT go.mod * Update NOTICE.txt and/or NOTICE-fips.txt --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* fix(deps): update misc * Update NOTICE.txt and/or NOTICE-fips.txt --------- Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
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.
What
Update
elastic/beatsto the latest version on branchmain.Changeset