-
Notifications
You must be signed in to change notification settings - Fork 25k
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 no use x-opaque-id
for deduplicating Elastic originating requests
#82855
Do no use x-opaque-id
for deduplicating Elastic originating requests
#82855
Conversation
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
* @see <a href="https://logging.apache.org/log4j/2.x/manual/filters.htmlf">Log4j2 Filters</a> | ||
*/ | ||
@Plugin(name = "RateLimitingFilter", category = Node.CATEGORY, elementType = Filter.ELEMENT_TYPE) | ||
public class RateLimitingFilter extends AbstractFilter { | ||
|
||
private volatile boolean useXOpaqueId = true; | ||
private static final String KIBANA_OPRDUCT_ORIGIN = "kibana"; |
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.
is this a typo or intentional?
private static final String KIBANA_OPRDUCT_ORIGIN = "kibana"; | |
private static final String KIBANA_PRODUCT_ORIGIN = "kibana"; |
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.
that was a typo. The constant is not needed as this change will apply to all elastic originating requests
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Hi @pgomulka, I've created a changelog YAML for you. |
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.
LGTM, but I would not change the naming of the member or setter.
|
||
private volatile boolean useXOpaqueId = true; | ||
// a flag to disable/enable use of xOpaqueId controlled by changing cluster setting | ||
private volatile boolean useXOpaqueIdEnabled = true; |
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 the addition of "enabled"? The "use" prefix already denotes a boolean.
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.
true - it does not make sens to me now either. I can't remember what I was thinking when renaming..
…mulka/elasticsearch into disable_xopaqueid_kibana_originating
…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
💔 Backport failed
You can use sqren/backport to manually backport by running |
…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
x-opaque-id
for deduplicating Elastic originating requests
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 #82810
gradle check
?