Skip to content

docs(llm-analytics): Document error trend visualization feature#16111

Open
inkeep[bot] wants to merge 1 commit intomasterfrom
docs-writer-ai-update-2026-03-31T21-47-39-422Z-qt56vw
Open

docs(llm-analytics): Document error trend visualization feature#16111
inkeep[bot] wants to merge 1 commit intomasterfrom
docs-writer-ai-update-2026-03-31T21-47-39-422Z-qt56vw

Conversation

@inkeep
Copy link
Copy Markdown
Contributor

@inkeep inkeep bot commented Mar 31, 2026

Changes

This PR adds documentation for the new error trend visualization feature in the LLM Analytics errors tab, introduced in PostHog/posthog#51743.

Updates to contents/docs/llm-analytics/errors.mdx

Added a new section "Visualizing error trends" that documents:

  • All errors trend – The Error trends button in the table header that opens a trends insight showing all errors over time, broken down by error type (limited to top 10)
  • Individual error trend – The trend icon next to each error row that opens a trends insight for that specific error, showing occurrences across all LLM event types (generations, spans, traces, and embeddings)
  • Both visualizations open in a new tab for non-disruptive exploration

Related


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.

@inkeep inkeep bot requested a review from andrewm4894 March 31, 2026 21:49
@github-actions
Copy link
Copy Markdown
Contributor

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

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Mar 31, 2026

Deploy preview

Status Details Updated (UTC)
🟢 Ready View preview Mar 31, 2026 10:00PM

@github-actions
Copy link
Copy Markdown
Contributor

Vale prose linter → found 2 errors, 0 warnings, 0 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/errors.mdx — 2 errors, 0 warnings, 0 suggestions
Line Severity Message Rule
51:1 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
53:1 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants