Add context dimension to DefaultQueryMetrics#10578
Conversation
nishantmonu51
left a comment
There was a problem hiding this comment.
👍 LGTM,
NIT: since we moved it to default now,
Can we now remove the context addition in DruidMetrics.makeRequestMetrics ?
jihoonson
left a comment
There was a problem hiding this comment.
This PR LGTM, but should be called out in the release notes because it can impact on the user metrics store. Also please address #10578 (review).
…that QueryMetrics adds it by default
|
@nishantmonu51 @jihoonson thank you for the review. I addressed the redundant call to |
…t dimensions in QueryMetrics
|
Hmm, I appear to be having an inspection problem after my Update: Had to add method to |
|
@capistrant thanks for the detailed PR description 👍 |
* Add context dimension to DefaultQueryMetrics * remove redundant addition of context dimension from DruidMetrics now that QueryMetrics adds it by default * update SearchQueryMetrics to reflect the same pattern as other default dimensions in QueryMetrics * add PublicApi annotation for context in QueryMetrics Interface
Fixes #10577 .
Release Notes
contextis now a default dimension emitted for all query metrics.contextis ajsonformatted string containing the query context that is tied to the query that the emitted metric refers to. This will alter some of the metrics that are emitted by Druid (adding a dimension that was not previously there). Clients should plan to handle this newcontextdimension in their metrics pipeline. Since the dimension is ajsonformatted string, it is common for clients to parse the dimension and either flatten it or extract the bits they want and discard the fulljsonformatted string blob.Description
Makes the context dimension a default dimension for DruidQueryMetrics. This will allow clients to gain more informations about the queries producing the metrics.
This PR has:
Key changed/added classes in this PR
DefaultQueryMetrics