-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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 telemetry templates #47894
Fix telemetry templates #47894
Conversation
Hi @bochengchu. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1 question, rest looks good.
{{- if or $prom $sdMetrics $sdLogs }} | ||
defaultProviders: | ||
{{- if or $prom $sdMetrics }} | ||
metrics: | ||
{{ if $prom }}- prometheus{{ end }} | ||
{{ if $sdMetrics }}- stackdriver{{ end }} | ||
{{ if and $sdMetrics $sdLogs }}- stackdriver{{ end }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do we need logs enabled to turn on metrics? And the opposite on L22
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The semantics would be: only set defaultProviders if both metrics and logs are default.
If one of them is default and another is custom, say metrics is default and log has custom setting, and we write {{ if $sdMetrics }}, it will end up having both defaultProviders set and EnvoyFilters created.
Not sure if it is okay to have both, but I think having only one of them can reduce confusion.
b2c3480
to
f92364f
Compare
/ok-to-test |
f92364f
to
0f41137
Compare
fix configmap
0f41137
to
f4cc136
Compare
/cherry-pick release-1.19 |
@bochengchu: only istio org members may request cherry picks. You can still do the cherry-pick manually. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-1.19 |
@zirain: #47894 failed to apply on top of branch "release-1.19":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@zirain: new issue created for failed cherrypick: #48436 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-1.20 |
@jacob-delgado: new pull request created: #48444 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Please provide a description of this PR:
If both SD metrics & SD logs are default, set in defaultProvider.
If any of SD metrics or logs has custom config set, use EnvoyFilter.