docs(llm-analytics): Document configurable cooldown for evaluation reports

[inkeep]

Changes

Updates the LLM Analytics evaluations documentation to reflect the new configurable cooldown feature for count-triggered evaluation reports (added in PostHog/posthog#55544).

What changed

1. Default report configuration table – Updated the Cooldown row:

   • Default value changed from "60 minutes" to "1 hour" (matching how the UI now displays it)
   • Description updated to "Minimum hours between count-triggered reports (1–24 hours)" to reflect the configurable range

2. Customizing reports section – Added a new bullet point:

   • "Adjust the minimum hours between reports (1–24) to control how often count-triggered reports can fire"

Why

Previously, count-triggered evaluation reports were locked to a 1-hour cooldown. Users can now configure the cooldown from 1 to 24 hours via a "Minimum hours between reports" input in the UI. The documentation needed to reflect this user-facing change.

---

This PR was created by the Inkeep Content Writer agent, which is maintained by the Docs and Wizard team. Please reach out on Slack for help if needed.

[github-actions]

Deploy preview

Status	Details	Updated (UTC)
🟢 Ready	View preview	Apr 21, 2026 07:06PM

[github-actions]

Vale prose linter → found 6 errors, 6 warnings, 2 suggestions in your markdown

Full report → Copy the linter results into an LLM to batch-fix issues.

Linter being weird? Update the rules!

contents/docs/llm-analytics/evaluations.mdx — 6 errors, 6 warnings, 2 suggestions

Line	Severity	Message	Rule
15:98	warning	Avoid trivializing words. 'easy to' can sound dismissive to the reader.	PostHogDocs.Trivializers
24:98	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
41:52	suggestion	Address the reader directly. Use 'you' instead of 'the user'.	PostHogDocs.DirectAddress
84:4	warning	'Code-based evaluations (Hog)' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
98:15	warning	'globals' is a possible misspelling.	PostHogBase.Spelling
109:63	suggestion	Address the reader directly. Use 'you' instead of 'the user'.	PostHogDocs.DirectAddress
125:5	warning	'Writing Hog evaluation code' heading should be in sentence case, and product names should be capitalized.	PostHogBase.SentenceCase
127:115	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
209:63	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
234:70	warning	Capitalize 'Workflows' for PostHog's product. Use 'workflows' for the general industry concept.	PostHogBase.ProductNames
254:5	warning	'Cooldown' is a possible misspelling.	PostHogBase.Spelling
254:90	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
266:45	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash
312:45	error	Hi, Andy here... use an en dash ( – ) with spaces. On Mac, holding down the Option and hyphen key will give you an en dash.	PostHogBase.EnDash

[github-actions]

Hey @andrewm4894! This docs PR was generated for you by an agent. You're responsible for reviewing and merging it into production.

1. Review and approve the PR
2. Merge the PR
   a. Check the preview env and CI build and merge it yourself
   b. Enable auto-merge if you're confident in the changes