docs(glossary): add Pulse, Chart Any Table, Agentic Access

[jannikmaierhoefer]

Summary

Scheduled glossary review of the last month of docs changes surfaced three shipped features/concepts with dedicated docs pages that were missing from lib/glossary-data.js:

• Pulse — outlier-chart strip above the Observations table (/docs/observability/features/pulse)
• Chart Any Table — Table | Chart toggle for the Observations table (/docs/observability/features/events-table-charts)
• Agentic Access — the new agentic-access pages added across observability, evaluation, and prompt management (/docs/observability/features/agentic-access and siblings)

While adding these, I also fixed three relatedTerms entries (Custom Dashboards, Embedding, Generation) that pointed at a nonexistent "Token Tracking" term — the actual glossary term is "Token", so these links were silently rendering as plain, unlinked text. Replaced with "Token", and linked the new Pulse/Chart Any Table terms from Custom Dashboards.

Other findings (not actioned in this PR)

• The three "agentic access" pages use inconsistent titles/H1s for the same concept: Agentic access (observability, evaluation pages, H1 "Agentic access to observability/evaluation") vs. Agentic Prompt Management (prompt-management page, different pattern and casing). sidebarTitle is consistently "Agent Access" across all three. Worth a follow-up copy pass to align the prompt-management page with the other two.
• The Langfuse Agent Skill and Langfuse CLI (introduced earlier this year, referenced heavily from the new agentic-access pages) are also missing glossary entries, but predate the last-month review window so I left them out of scope here.
• Remote Experiment and Filter Search Bar terminology in recent commits (secure remote experiment triggers, v4 consistency pass) already matches the existing glossary entries — no action needed.

Test plan

• node -e "require('./lib/glossary-data.js')" loads without errors, no duplicate ids
• pnpm run format — no changes needed
• Spot-check /docs/glossary renders the new entries and related-term links resolve correctly

---

Generated by Claude Code

Greptile Summary

Adds glossary entries for Agentic Access, Chart Any Table, and Pulse while correcting related-term references that previously targeted a nonexistent term.

• Adds three glossary definitions with links to their corresponding documentation.
• Connects the new observability terms through related-term links.
• Replaces invalid “Token Tracking” references with the existing “Token” term.

Confidence Score: 5/5

The PR appears safe to merge; the added glossary entries and corrected cross-links conform to the existing glossary contracts.

All new identifiers, categories, related-term targets, and documentation links resolve correctly, with no blocking or non-blocking defect identified.

_{Reviews (1): Last reviewed commit: "docs(glossary): add Pulse, Chart Any Tab..." | Re-trigger Greptile}

Context used:

• Knowledge Base — Product Documentation Content (content/docs, content/guides, content/faq)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
langfuse-docs	Ready	Preview	Aug 6, 2026 11:45am

[github-actions]

@claude review

[claude]

LGTM — mechanical glossary data addition with no logic changes.

What was reviewed

• Verified the three new linked docs pages (pulse, events-table-charts, agentic-access) exist in content/docs/observability/features/.
• Programmatically checked lib/glossary-data.js for duplicate ids and dangling relatedTerms references (none found) — confirms the "Token Tracking" → "Token" fix resolves the previously broken links.
• Checked alphabetical placement of the three new entries within TERMS — consistent with surrounding entries.

Extended reasoning...

Overview

This PR touches a single file, lib/glossary-data.js, adding three new glossary term objects (Pulse, Chart Any Table, Agentic Access) and fixing three relatedTerms arrays that referenced a nonexistent "Token Tracking" term instead of the actual "Token" term. Pure static data, no logic, components, or build config changed.

Security risks

None. This is a static JS data array consumed by the glossary page component; no user input, no auth, no external calls.

Level of scrutiny

Low. This is exactly the kind of mechanical, self-contained content change the approval guidelines describe — new data entries following an established schema, plus a small, verifiable bugfix (dangling term references). I independently confirmed via a script that there are no duplicate ids and no relatedTerms pointing at nonexistent terms, and confirmed the three newly linked docs pages exist in the repo.

Other factors

No prior reviews exist on this PR from me. The PR description is thorough and includes a self-check (node -e "require(...)" for duplicate IDs) that I independently re-verified. The bug-hunting system found no issues, and the one candidate issue it raised (categorizing "Agentic Access" only under PLATFORM) was investigated and ruled out — categorization choices for a glossary card are editorial, not a bug.