Skip to content
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

fix(kuma-cp): use the hostname for gateway stats #3467

Merged
merged 1 commit into from Dec 10, 2021
Merged

fix(kuma-cp): use the hostname for gateway stats #3467

merged 1 commit into from Dec 10, 2021

Conversation

jpeach
Copy link
Contributor

@jpeach jpeach commented Dec 10, 2021

Summary

The virtualhost name field is used for Envoy metrics, so using the
actual hostname in this field rather than a xDS resource name results
in Prometheus labels that are a lot more useable.

Full changelog

N/A

Issues resolved

Fix #3320

Documentation

N/A

Testing

  • Unit tests
  • E2E tests
  • Manual testing on Universal
  • Manual testing on Kubernetes

Backwards compatibility

  • Update UPGRADE.md with any steps users will need to take when upgrading.
  • Add backport-to-stable label if the code is backwards compatible. Otherwise, list breaking changes.

@jpeach jpeach requested a review from a team as a code owner December 10, 2021 00:21
The virtualhost name field is used for Envoy metrics, so using the
actual hostname in this field rather than a xDS resource name results
in Prometheus labels that are a lot more useable.

This fixes #3320.

Signed-off-by: James Peach <james.peach@konghq.com>
@jpeach jpeach enabled auto-merge (squash) December 10, 2021 06:32
@jpeach jpeach merged commit 1c33d51 into kumahq:master Dec 10, 2021
@jpeach jpeach deleted the fix/gateway-stats-name branch December 10, 2021 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Re-evaluate virtualhost names for Gateway
2 participants