🤖 GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

🔍 Preview links for changed docs

• docs/release-notes/known-issues.md

This pull request does not have a backport label. Could you fix it @lucabelluccini? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-8.19 is the label to automatically backport to the 8.19 branch.
• backport-9./d is the label to automatically backport to the 9./d branch. /d is the digit.
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

✅ Vale Linting Results

No issues found on modified lines!

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

The runtime field trick to avoid reindexing should be validated.

@lucabelluccini I tested the runtime field workardound.

Without it:

❯ curl -s 'http://localhost:9200/_field_caps?fields=timestamp.us&index=.ds-traces-apm-default-2026.02.27-000001'
{"indices":[".ds-traces-apm-default-2026.02.27-000001"],"fields":{"timestamp.us":{"float":{"type":"float","metadata_field":false,"searchable":true,"aggregatable":true}},"timestamp":{"object":{"type":"object","metadata_field":false,"searchable":false,"aggregatable":false}}}}

The issue in traces view is there:

We apply the runtime field mapping:

❯ curl -X PUT -s 'http://localhost:9200/.ds-traces-apm-default-2026.02.27-000001/_mapping' \
    -H "Content-Type: application/json" -d '
{
  "runtime": {
    "timestamp.us": {
      "type": "long"
    }
  }
}'

And now:

❯ curl -s 'http://localhost:9200/_field_caps?fields=timestamp.us&index=.ds-traces-apm-default-2026.02.27-000001'
{"indices":[".ds-traces-apm-default-2026.02.27-000001"],"fields":{"timestamp.us":{"long":{"type":"long","metadata_field":false,"searchable":true,"aggregatable":true}},"timestamp":{"object":{"type":"object","metadata_field":false,"searchable":false,"aggregatable":false}}}}`

Issue in traces view gone:

Thank you @endorama for testing the workaround - Hugely appreciated (I didn't have a repro on my hands).

Merging! Thanks @lucabelluccini 🚀