Fix date timestamps | New Troubleshooting Page

[stefnestor]

Summary

👋 howdy, team! This generalizes a top Support article Detect, prevent, and clean-up future dates (@timestamp) into a general new troubleshooting guide on how to detect, cleanup, and avoid-impact-from timestamp data quality issues.

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

[github-actions]

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

• Review docs changes (docs-review). Status: queued.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[github-actions]

🔍 Preview links for changed docs

• troubleshoot/elasticsearch.md
• troubleshoot/elasticsearch/fix-date-timestamps.md

[github-actions]

✅ Elastic Docs Style Checker (Vale)

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.

[marciw]

@stefnestor I'm running the docs review agent on this, but please ignore its comments for now! I will use them in doing my review

[github-actions]

Docs review summary

Focus areas

• Style and clarity: Several wording improvements needed. Grammar error on line 90 (who's → whose), tense issues with "is ran" → "is run" on lines 90 and 96.
• Jargon: No problematic jargon found.
• Frontmatter and applies_to: Critical issue - description field is empty and must be populated with a user-facing summary.
• Content type fit: Title is too generic for a troubleshooting page. Should be problem-focused per troubleshooting guidelines. Structure mostly follows troubleshooting pattern but Investigate section lacks an anchor ID.
• Parent issue satisfaction: Satisfied - the PR generalizes the Support article into a comprehensive troubleshooting guide as requested.

Notes

• The page is well-structured overall with good examples and clear resolution paths.
• Consider whether "Fix date timestamps" is specific enough for users to identify their problem. Troubleshooting pages typically use problem-focused titles like "Performance issues caused by timestamp data quality" or "Searches hit frozen tier unexpectedly".

Generated by Docs review agent for issue #6869 · ● 545.6K

[marciw]

@stefnestor fyi I'm just about done with my review, but I still have a few things to check. Please don't commit anything until I'm done, so I can avoid conflict headaches 🙏

[stefnestor]

Oh, I'm sorry! You mentioned that & I thought you meant reviewing via UI so thought I was sneaking in before you looked at it. Which was bad thinking of me, sorry for the merge issues! 🙈

[marciw]

No worries! I typically push directly to your branch :) (but let me know if that ever gets annoying)

Anyway, I'm done reviewing. I did quite a bit of rewriting again for clarity, so please take a look before you merge.

Preview: https://docs-v3-preview.elastic.dev/elastic/docs-content/pull/6869/troubleshoot/elasticsearch/fix-date-timestamps