Use reqwest 0.12 and 0.11. Allow CDLA-Permissive-2.0#5
Merged
joshcoughlan merged 26 commits intoAutomattic:update_azure_cratesfrom Jan 29, 2026
Merged
Conversation
…24453) * chore(core): Move `AtomicF64` type into `vector-common` * chore(core): Move `stats` module to `vector-common` * chore(core): Add new `AtomicEwma` type * enhancement(observability): Add `_utilization_mean` buffer metrics The source and transform buffer utilization metrics currently measure either the instantaneous level or a histogram, neither of which is a reliable single-valued reflection of the actual status. For this purpose, we introduce a `mean` metric that uses the EWMA calculations to produce a simple moving average that will better track the actual value. * Fix buffer utilization test counts for added metric * Update wording of new metric documentation * Tweak outputs wording
…24462) Clarify glob syntax in file source documentation
* chore(deps): bump lru to 0.16.3 * Ignore RUSTSEC-2026-0002 due to aws-sdk-s3 * Update licenses
…EWMA alpha (#24467) * enhancement(observability): Add configuration for buffer utilization EWMA alpha * Restore comment
…pine in the docker-images group (#24426) * chore(deps): bump alpine Bumps the docker-images group in /distribution/docker/alpine with 1 update: alpine. Updates `alpine` from 3.22 to 3.23 --- updated-dependencies: - dependency-name: alpine dependency-version: '3.23' dependency-type: direct:production update-type: version-update:semver-minor dependency-group: docker-images ... Signed-off-by: dependabot[bot] <support@github.com> * Update alpine in distribution/docker/distroless-static/Dockerfile --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Thomas <thomas.schneider@datadoghq.com>
…n use_otlp_decoding is enabled (#24480) * fix(opentelemetry source): emit events_received metric when use_otlp_decoding is enabled * chore: add changelog fragment for opentelemetry metric fix * test(opentelemetry): add test to verify metric emission with use_otlp_decoding * Format long lines
* Use tls-rustls-aws-lc-rs flag in sqlx * cargo vdev build licenses * Add changelog * Checkout Cargo.lock from master * cargo check * Update Cargo.lock * Update changelog * Use tls-rustls-ring instead of tls-rustls-aws-lc-rs * Update licenses
* Update app.js removes transcend file reference * Delete website/assets/js/cookie-banner.js deletes transcend file
…24498) Bumps [undici](https://github.com/nodejs/undici) from 7.16.0 to 7.18.2. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](nodejs/undici@v7.16.0...v7.18.2) --- updated-dependencies: - dependency-name: undici dependency-version: 7.18.2 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
) With the introduction of internal timing measurements in seconds as histograms, the lower bound of 2^-6 (~15ms) in the internal histogram storage is no longer precise enough to properly capture the required measurements. This change extends the smallest bucket down to 2^-12 (~244us), which is the inverse of the largest bucket of 2^12 (4096).
* fix(metrics): absolute to incremental histogram conversion * chore(changelog): add details on fix histogram changelog
* enhancement(cli): Shell autocompletion for vector cli This adds support for generating autocompletion for different shells for the vector cli. Superseds [#9823](#9823) * chore: add changelog * Bump versions * Update changelog * vdev build licenses --------- Co-authored-by: Thomas <thomas.schneider@datadoghq.com>
) * enhancement(observability): Standardize buffer size metric names Many of the buffer size metric names have been specified (in `docs/specs/buffer.md`) in a way that conflicts with the metric naming specification (in `docs/specs/instrumentation.md`). In particular, the latter specifies that metric names should end with a unit (ex `_bytes` or `_events`) but the former placed the units within the name (ex `buffer_byte_size` or `buffer_max_event_size`). This latter leads to a confusing metric name which seems to report the maximum event size that may be buffered while in reality it is reporting the maximum size of the buffer in terms of events. This change adds parallel metrics for these names that provide the standardized names. The existing names are thus deprecated and will be removed in a future version. * Add links in deprecated_message --------- Co-authored-by: Thomas <thomas.schneider@datadoghq.com>
* fix(host_metrics source): use recv_from_full in fetch_netlink_inet_headers add netlink to allowed words list * Update changelog * Use while let instead of loop --------- Co-authored-by: Thomas <thomasqueirozb@gmail.com>
* Fix duplicated domains * chore(website): update hugo templates to work with 0.152.2
* Add usage method to VRL functions with descriptions from cue files * vdev build licenses
Vector has long had two `codecs` libraries: a separate `codecs` crate in `lib` and a `codecs` module in `src`. This change merges both into the crate to reduce confusion over where codec functionality is found.
…sing time (#24481) * chore(core): Add `ingest_timestamp` to `EventMetadata` We want to record the time at which events are ingested in order to track latency as each travels through the topology. This is currently recorded for log events using the Vector namespace in the `vector.ingest_timestamp` metadata field, but we want it to be usable for all event types. As such, we need a new field in `struct EventMetadata`. This change adds the new field as an `Option` so as to retain sane semantics for `Default` implementations and to avoid extra calls to `Utc::now`. The `SourceSender::send` method sets this if the source doesn't so as to ensure complete coverage. For backward compatibility, this metadata is still inserted into the Vector log namespace metadata, taken from this new field. Since this metadata is set up before passing the events to the `SourceSender`, the ingest timestamp is set manually in sources that can create Vector namespace logs. * Add new `EwmaGauge` wrapper to handle both in one update step * enhancement(observability): Add metrics to measure total event processing time This adds an optional `trait BufferInstrumentation` hook to `struct BufferSender` which is called at the very start of the buffer send path. We use that hook to take the previously added universal event `ingest_timestamp` metadata and from it calculate the total time spent processing the event, including buffering delays. This time is emitted in internal metrics as a `event_processing_time_seconds` histogram and `event_processing_time_mean_seconds` gauge, the latter using an EWMA to smooth the mean over time. * Update wording on the lognamespacing tutorial docs. * Pre-create metrics to avoid extraneous labels * Fix tests * Move setting ingest timestamp back into `insert_standard_vector_source_metadata` * Assert an upper limit on the average latency gauge too
* do not log TCP io errors * Revert "do not log TCP io errors" This reverts commit 2846926. * tcp: silence connectionResets when reading from the socket * remove extension trait * add changelog * fix changelog * use a wrapper around FramedRead to raise the error if the buffer was not empty * Fixup changelog --------- Co-authored-by: Bruce Guenter <bruce.guenter@datadoghq.com>
github-actions
bot
added
domain: sinks
domain: sources
domain: topology
domain: codecs
labels
joshcoughlan
merged commit fc8d910
into
Automattic:update_azure_crates
38 of 54 checks passed
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
9 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.
Summary
PR contains a bunch of commits because the first commit is a merge with master. Only the last 2 commits are "real". If the branch is updated I can cherry-pick the last two commits and make this PR way smaller
Vector configuration
NA
How did you test this PR?
make check-clippy./scripts/run-integration-test.sh int azuremake testChange Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
Notes
@vectordotdev/vectorto reach out to us regarding this PR.pre-pushhook, please see this template.make fmtmake check-clippy(if there are failures it's possible some of them can be fixed withmake clippy-fix)make testgit merge origin masterandgit push.Cargo.lock), pleaserun
make build-licensesto regenerate the license inventory and commit the changes (if any). More details here.