We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug In https://github.com/vmware-tanzu/antrea/blob/master/build/yamls/elk-flow-collector/kibana.ndjson, the field name shows up as ipfix.destinationServiceName, but according to the documentation (https://github.com/vmware-tanzu/antrea/blob/master/docs/network-flow-visibility.md#ies-from-antrea-ie-registry) & the code, the name should be ipfix.destinationServicePortName. As a result, it seems that the dashboards for Pod-to-Service traffic throughput cannot be created properly (they stay empty).
ipfix.destinationServiceName
ipfix.destinationServicePortName
Versions: Antrea v0.10.1 and TOT
The text was updated successfully, but these errors were encountered:
zyiou
Successfully merging a pull request may close this issue.
Describe the bug
In https://github.com/vmware-tanzu/antrea/blob/master/build/yamls/elk-flow-collector/kibana.ndjson, the field name shows up as
ipfix.destinationServiceName
, but according to the documentation (https://github.com/vmware-tanzu/antrea/blob/master/docs/network-flow-visibility.md#ies-from-antrea-ie-registry) & the code, the name should beipfix.destinationServicePortName
. As a result, it seems that the dashboards for Pod-to-Service traffic throughput cannot be created properly (they stay empty).Versions:
Antrea v0.10.1 and TOT
The text was updated successfully, but these errors were encountered: