Skip to content

Add sort field usage to telemetry#139530

Merged
davidkyle merged 3 commits intoelastic:mainfrom
davidkyle:sort-section-usage
Dec 17, 2025
Merged

Add sort field usage to telemetry#139530
davidkyle merged 3 commits intoelastic:mainfrom
davidkyle:sort-section-usage

Conversation

@davidkyle
Copy link
Member

@davidkyle davidkyle commented Dec 15, 2025

Adds tracking for the sort section in a query and leverages the extended reporting added in #135306 to record the particular type of sort used.

An alternative option was to raise sort to a top level field in the SearchUsageStats class along with queries, rescorers and retrievers but sort does not feel special enough to be a top level field and using extended data solves the problem of passing the sort type.

Closes #139513

@davidkyle davidkyle changed the title Add sort to telemetry Add sort field usage to telemetry Dec 15, 2025
@davidkyle davidkyle added the :Search Relevance/Search Catch all for Search Relevance label Dec 15, 2025
@davidkyle davidkyle marked this pull request as ready for review December 15, 2025 16:43
@elasticsearchmachine elasticsearchmachine added the Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch label Dec 15, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-search-relevance (Team:Search Relevance)

@benwtrent
Copy link
Member

@davidkyle I think this is ok? But I admittedly don't know how we actually search and dig into telemetry here. if you know how and this works well, I am for it :)

@davidkyle
Copy link
Member Author

The idea is to create a visualisation similar to this one for retrievers. The queries won't be pretty but it can be visualised in lens.

Screenshot 2025-12-16 at 09 01 42

@davidkyle davidkyle merged commit a34adb6 into elastic:main Dec 17, 2025
35 checks passed
szybia added a commit to szybia/elasticsearch that referenced this pull request Dec 17, 2025
…-err-message

* upstream/main: (45 commits)
  Add sort field usage to telemetry (elastic#139530)
  ES|QL: Release CCS support for FORK (elastic#139630)
  Parameterize VectorSimilarityFunctionsTests on the similarity function (elastic#139516)
  fix broken links from ccs file move (elastic#139655)
  Update docs for v9.2.3 release (elastic#139479)
  Move tsdb bwc tests to x-pack/logsdb (elastic#139671)
  Fix FirstDocIdGroupingAggregatorFunction (elastic#139619)
  Fix release test for node_reduction profiling (elastic#139515)
  Unmute RestClientSingleHostIntegTests.testRequestResetAndAbort (elastic#139656)
  Unmute VerifyVersionConstantsIT.testLuceneVersionConstant (elastic#139644)
  Mute org.elasticsearch.repositories.gcs.GoogleCloudStorageBlobStoreRepositoryTests testReadNonExistingPath elastic#139665
  Mute org.elasticsearch.smoketest.WatcherYamlRestIT test {p0=mustache/10_webhook/Test webhook action with mustache integration} elastic#139663
  [ES|QL] Run aggregations on aggregate metric double with default metric (elastic#138647)
  Enable TDigest field mapper and ES|QL type (elastic#139607)
  Mute org.elasticsearch.index.mapper.HalfFloatSyntheticSourceNativeArrayIntegrationTests testSynthesizeArrayRandom elastic#139658
  Explicitly cleanup test index with shared data path (elastic#136048)
  Mute org.elasticsearch.xpack.core.action.XPackUsageResponseTests testVersionDependentSerializationWriteToOldStream elastic#139576
  Make XPackUsageResponseTests a wire serializing test case (elastic#139643)
  Mute org.elasticsearch.upgrades.UpgradeClusterClientYamlTestSuiteIT test {p0=mixed_cluster/90_ml_data_frame_analytics_crud/Start and stop old regression job} elastic#139654
  Relax error bounds for RandomizedTimeSeriesIT (elastic#139641)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>non-issue :Search Relevance/Search Catch all for Search Relevance Team:Search Relevance Meta label for the Search Relevance team in Elasticsearch v9.3.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add telemetry to track usage of sort

3 participants

Comments