Open
Conversation
Updated the description for `envoy.server.state` from [Legacy] to [OpenMetrics V2 and Legacy] The metric `envoy.server.state` is available with the OpenMetrics version of the integration and not just Legacy as per these links Openmetrics: https://github.com/DataDog/integrations-core/blob/d6a7e88d5abe6e817dc819a73cf9a3c3d9040d54/envoy/datadog_checks/envoy/metrics.py#L324 Legacy: https://github.com/DataDog/integrations-core/blob/d6a7e88d5abe6e817dc819a73cf9a3c3d9040d54/envoy/datadog_checks/envoy/metrics.py#L499
Contributor
|
This PR does not modify any files shipped with the agent. To help streamline the release process, please consider adding the |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files🚀 New features to boost your workflow:
|
maycmlee
approved these changes
Feb 12, 2026
Contributor
maycmlee
left a comment
maycmlee
left a comment
There was a problem hiding this comment.
Small edit, but approving
| envoy.server.debug_assertion_failures,count,,,,[Legacy] Number of debug assertion failures detected in a release build if compiled with -define log_debug_assert_in_release=enabled or zero otherwise,-1,envoy,, | ||
| envoy.server.hot_restart_epoch,gauge,,,,[Legacy] Current hot restart epoch,0,envoy,, | ||
| envoy.server.state,gauge,,,,[Legacy] Current State of the Server,0,envoy,, | ||
| envoy.server.state,gauge,,,,[OpenMetrics V2 and Legacy] Current State of the Server,0,envoy,, |
Contributor
There was a problem hiding this comment.
Suggested change
| envoy.server.state,gauge,,,,[OpenMetrics V2 and Legacy] Current State of the Server,0,envoy,, | |
| envoy.server.state,gauge,,,,[OpenMetrics v2 and Legacy] Current State of the Server,0,envoy,, |
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
2 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.
Updated the description for
envoy.server.statefrom [Legacy] to [OpenMetrics V2 and Legacy] The metricenvoy.server.stateis available with the OpenMetrics version of the integration and not just Legacy as per these linksOpenmetrics:
integrations-core/envoy/datadog_checks/envoy/metrics.py
Line 324 in d6a7e88
Legacy:
integrations-core/envoy/datadog_checks/envoy/metrics.py
Line 499 in d6a7e88
What does this PR do?
Updated the description field to [OpenMetrics V2 and Legacy] as the
envoy.server.statecomes from both the openmetrics and legacy version of the Envoy integrationMotivation
This escalation: https://datadoghq.atlassian.net/browse/AGENT-15550
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged