-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
Do not use x-opaque-id for deprecations originated from Kibana #82810
Labels
Comments
pgomulka
added
>bug
blocker
needs:triage
Requires assignment of a team area label
v7.17.0
labels
Jan 19, 2022
Pinging @elastic/es-core-infra (Team:Core/Infra) |
pgomulka
added a commit
to pgomulka/elasticsearch
that referenced
this issue
Jan 20, 2022
deprecated log messages originating from kibana's requests should not be deduplicated with the use of x-opaque-id because kibana populates it with UUID. closes elastic#82810
pgomulka
added a commit
to pgomulka/elasticsearch
that referenced
this issue
Jan 25, 2022
…lastic#82855) deprecated log messages originating from any elastic product requests should not be deduplicated with the use of x-opaque-id. If present, the value of X-elastic-product-origin will be used as part of the throttling key. relates elastic#82810
pgomulka
added a commit
to pgomulka/elasticsearch
that referenced
this issue
Jan 25, 2022
…backport (elastic#82855) deprecated log messages originating from any elastic product requests should not be deduplicated with the use of x-opaque-id. If present, the value of X-elastic-product-origin will be used as part of the throttling key. relates elastic#82810
closing by #82855 and backports to 8.0 and 7.17 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Kibana is at the moment using x-opaque-id with a UUID which is causing a deprecation log throttling to not work. A new unique value on x-opaque-id is causing that every deprecation is considered unique.
We need to implement a workaround to exclude requests originating from Kibana from using x-opaque-id when emitting a deprecation log.
a workaround to elastic/kibana#120124
edit: x-opaque-id won't be use for deprecation log throttling for any requests originating from elastic stack (x-elastic-product-origin present)
The text was updated successfully, but these errors were encountered: