[pull] master from DataDog:master#634
Merged
Merged
Conversation
* Add adaptive concurrency gradient controller metrics to envoy integration * Add adaptive concurrency filter to E2E Docker environments * Add adaptive concurrency metrics to OpenMetrics path and E2E assertions * Add focused symmetric metadata check for adaptive concurrency metrics * Add changelog entry * Assert adaptive concurrency metric values and annotate gauge units - Pin fixture values in the legacy and OpenMetrics unit tests so a wrong mapping or metric type is caught, not just a wrong name. - Set unit_name=request on concurrency_limit and burst_queue_size for consistency with rq_blocked. - Trim the symmetric test docstring/comments and drop a dead import. * Use a thousands separator in the gradient metric description * Group datadog_checks test imports into a single block * Refine adaptive concurrency test scope and metric description - Promote the legacy expected-value map to a module constant so the metric list and its values share one source of truth. - Guard the symmetric metadata test against a vacuous pass when the controller emits nothing. - Recast the min_rtt_calculation_active description to drop the semicolon. * Assert adaptive concurrency metrics in the E2E test * Wire adaptive concurrency metrics into the legacy real-environment tests Fix a stat_prefix typo (ingress-https -> ingress_http) that had gone undetected because the legacy path's real-Docker integration and e2e tests never asserted the new metrics against a live Envoy. - Add a real-environment integration test asserting presence and tags. - Extend the legacy e2e test to cover the same metrics. - Correct the mocked unit test fixture to match real Envoy output. * Update envoy/metadata.csv Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com> * Update envoy/tests/test_unit.py Co-authored-by: dkirov-dd <166512750+dkirov-dd@users.noreply.github.com> * Update envoy/tests/legacy/common.py Co-authored-by: dkirov-dd <166512750+dkirov-dd@users.noreply.github.com> * Fix definition order after applying suggestion in legacy/common.py The applied GitHub suggestion referenced ADAPTIVE_CONCURRENCY_METRIC_VALUES before its definition, breaking ruff (F821). * Centralize adaptive concurrency Prometheus metric values Derive ADAPTIVE_CONCURRENCY_PROMETHEUS_METRICS and ADAPTIVE_CONCURRENCY_PROMETHEUS_GAUGE_VALUES from a single values dict instead of maintaining the metric names in both places independently. --------- Co-authored-by: domalessi <111786334+domalessi@users.noreply.github.com> Co-authored-by: dkirov-dd <166512750+dkirov-dd@users.noreply.github.com>
* Add native_dynamic type * Add changelog entry * Add regression tests for _total gauge/counter dispatch - New tests/test_metrics_config.py pins construct_metrics_config so a gauge/counter pair collapses to a single native_dynamic entry while lone _total entries and NON_CONFORMING_METRICS keep their existing behavior. - Value/type assertions in test_istiod and test_istio_agent verify the gauge sample is submitted as a gauge and the counter sample as a monotonic count, catching regressions where the native transformer locks to the wrong type. * Apply ruff formatting --------- Co-authored-by: Juanpe Araque <juanpedro.araque@datadoghq.com>
…24178) * fix(mysql): use SHOW ALL REPLICAS STATUS for MariaDB multi-channel replication Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> * add changelog for #24178 * refactor(mysql): use replica_keyword variable; add Connection_name tagging test Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )