Can match phase shard APM metric with search request context#137196
Conversation
|
Pinging @elastic/es-search-foundations (Team:Search Foundations) |
|
Hi @chrisparrinello, I've created a changelog YAML for you. |
| // TODO remove the exception handling as it's now in canMatch itself | ||
| responses.add(new CanMatchNodeResponse.ResponseOrFailure(canMatch(shardSearchRequest))); | ||
| indexShard.getSearchOperationListener().onCanMatchPhase(System.nanoTime() - shardCanMatchStartTimeInNanos); | ||
| } catch (Exception e) { |
There was a problem hiding this comment.
Could you restore the try catch please and the TODO? Sadly, more work is required to remove it, around removing dead code from the can match serialization layer, add a transport version for it etc. Feel free to take that on as a follow-up if you wish, I can share more details about it.
There was a problem hiding this comment.
Do we still need to restore the TODO before responses.add(...)
// TODO remove the exception handling as it's now in canMatch itself
There was a problem hiding this comment.
It is restored based on looking at the full diff between main and this branch (actually the full diff shows the TODO as unmodified and in the try block, not the catch block). Sorry the commit history messed up when I did a bad rebase.
server/src/main/java/org/elasticsearch/index/search/stats/ShardSearchPhaseAPMMetrics.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/elasticsearch/search/SearchService.java
Outdated
Show resolved
Hide resolved
server/src/main/java/org/elasticsearch/index/search/stats/ShardSearchPhaseAPMMetrics.java
Outdated
Show resolved
Hide resolved
…astic#137314) We recently introduced metrics attributes to track search latencies at the shard and coord level. With elastic#137196 we are introducing such attributes to the can match phase latency metrics. The time range filter is not currently accessible when recording the metrics. This commit exposes it.
ℹ️ Important: Docs version tagging👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version. We use applies_to tags to mark version-specific features and changes. Expand for a quick overviewWhen to use applies_to tags:✅ At the page level to indicate which products/deployments the content applies to (mandatory) What NOT to do:❌ Don't remove or replace information that applies to an older version 🤔 Need help?
|
eb689a2 to
40a500e
Compare
Add search request attributes context to: