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

The destination service label for tcp connection opened/closed metrics are inconsistent #17234

Closed
nrjpoddar opened this issue Sep 19, 2019 · 0 comments · Fixed by #17235
Closed
Assignees

Comments

@nrjpoddar
Copy link
Member

Bug description
Metrics istio_tcp_connections_closed_total and istio_tcp_connections_opened_total have destination_service label set to the destination.service.name attribute where as this label should be set to the destination.service.host as is done for all other metrics.

Affected product area (please put an X in all that apply)

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[x] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Expected behavior
destination_service label is set to the destination.service.host attribute

Steps to reproduce the bug
Install Istio and run TCP traffic through the merge, query istio_tcp_connections_closed_total and istio_tcp_connections_opened_total metric.

Version (include the output of istioctl version --remote and kubectl version)
1.3, 1.2, 1.1

@nrjpoddar nrjpoddar self-assigned this Sep 19, 2019
nrjpoddar pushed a commit to nrjpoddar/istio that referenced this issue Sep 19, 2019
istio-testing pushed a commit to istio-testing/istio that referenced this issue Sep 20, 2019
istio-testing pushed a commit to istio-testing/istio that referenced this issue Sep 20, 2019
fpesce pushed a commit that referenced this issue Oct 16, 2019
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 a pull request may close this issue.

1 participant