Transforms self-report in x-opaque-id

[stefnestor]

Description

👋 howdy team,

Transforms can cause long running searches, including searching frozen tier when not guarded against. Currently, in order to know the search task is transform related, you have to either guess to check the Transform's JSON query compared to the active search or it has to be a dedicated transform node with the search task.

Would you kindly consider adding (x-opaque-id, X-elastic-product-origin) noted in API conventions? Vs current is just an empty headers:

{
  "node": "OfVPaYgTTf-dWE6f_KNcjw",
  "id": 57979180252,
  "type": "transport",
  "action": "indices:data/read/search",
  "description": "indices[REDACTED-FROM-02010004], search_type[QUERY_THEN_FETCH], source[REDACTED]",
  "start_time": "2025-11-21T18:00:34.330Z",
  "start_time_in_millis": 1763748034330,
  "running_time": "13.1s",
  "running_time_in_nanos": 13190303980,
  "cancellable": true,
  "cancelled": false,
  "headers": {}
}