feat(analytics): Adds analytics dashboard #358
Conversation
WalkthroughThis update introduces an analytics dashboard feature, including backend data aggregation, frontend visualization, and supporting documentation. It adds audit logging for key user actions, updates audit event naming, enables audit logging by default, and provides tools for generating test audit data. Several new UI components and entitlements are also introduced. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant WebApp
participant AuditClient
participant Backend
participant DB
User->>WebApp: Performs code search/navigation
WebApp->>AuditClient: createAuditClient(action, metadata, domain)
AuditClient->>Backend: Auth & org check, create audit event
Backend->>DB: Insert audit record
WebApp->>Backend: Request analytics data (if on dashboard)
Backend->>DB: Aggregate audit logs by period/bucket
DB-->>Backend: Aggregated analytics data
Backend-->>WebApp: Analytics data
WebApp-->>User: Render analytics dashboard/charts
Possibly related PRs
Poem
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
msukkari
changed the title
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 5
🧹 Nitpick comments (9)
packages/web/src/components/ui/chart.tsx (1)
70-101: Consider sanitizing color values before CSS injection.While the risk is minimal since you're only injecting CSS custom properties from configuration, it's good practice to validate color values before using
dangerouslySetInnerHTML. This prevents potential CSS injection if the configuration is ever sourced from user input.Consider adding color validation:
const ChartStyle = ({ id, config }: { id: string; config: ChartConfig }) => { const colorConfig = Object.entries(config).filter( ([, config]) => config.theme || config.color ) if (!colorConfig.length) { return null } + // Validate color values to prevent CSS injection + const isValidColor = (color: string) => { + // Allow hex colors, rgb/rgba, hsl/hsla, and CSS color names + const colorRegex = /^(#[0-9A-Fa-f]{3,8}|rgb\(|rgba\(|hsl\(|hsla\(|[a-zA-Z]+)[\s\S]*$/; + return colorRegex.test(color); + }; + return ( <style dangerouslySetInnerHTML={{ __html: Object.entries(THEMES) .map( ([theme, prefix]) => ` ${prefix} [data-chart=${id}] { ${colorConfig .map(([key, itemConfig]) => { const color = itemConfig.theme?.[theme as keyof typeof itemConfig.theme] || itemConfig.color - return color ? ` --color-${key}: ${color};` : null + return color && isValidColor(color) ? ` --color-${key}: ${color};` : null }) .join("\n")} } ` ) .join("\n"), }} /> ) }packages/web/src/app/[domain]/components/searchBar/searchBar.tsx (1)
208-214: Consider error handling for audit logging.The audit logging implementation looks correct with proper action naming and metadata. However, consider whether audit logging failures should be handled gracefully to avoid impacting the search experience.
Since
createAuditClientappears to be a fire-and-forget operation, consider wrapping it in a try-catch to prevent any potential errors from affecting the search submission:+ try { createAuditClient({ action: "user.performed_code_search", metadata: { message: query, }, }, domain) + } catch (error) { + // Log error but don't block search functionality + console.error('Failed to create audit log:', error); + }packages/web/src/app/[domain]/settings/analytics/page.tsx (1)
11-19: Consider loading state for entitlement check.The entitlement-based conditional rendering is well implemented. However, consider handling the loading state while the entitlement check is in progress to improve user experience.
Consider adding a loading state:
function AnalyticsPageContent() { - const hasAnalyticsEntitlement = useHasEntitlement("analytics"); + const { hasEntitlement: hasAnalyticsEntitlement, isLoading } = useHasEntitlement("analytics"); + if (isLoading) { + return <div>Loading...</div>; // Or your preferred loading component + } + if (!hasAnalyticsEntitlement) { return <AnalyticsEntitlementMessage />; } return <AnalyticsContent />; }Note: This assumes the
useHasEntitlementhook supports a loading state. If it doesn't, you may need to check its implementation or handle loading differently.docs/docs/features/analytics.mdx (1)
17-17: Consider more concise wording.As suggested by the style checker, consider replacing "in order to" with "to" for more concise writing.
-This dashboard is backed by [audit log](/docs/configuration/audit-logs) events. Please ensure you have audit logging enabled in order to see these insights. +This dashboard is backed by [audit log](/docs/configuration/audit-logs) events. Please ensure you have audit logging enabled to see these insights.packages/db/tools/scripts/inject-audit-data.ts (1)
30-34: Consider validating action names against a source of truth.The hardcoded action names could become out of sync with the actual system if action names change elsewhere in the codebase.
Consider importing action constants from a shared location or adding validation:
+import { AUDIT_ACTIONS } from '../../../shared/auditActions'; // if such constants exist + - const actions = [ - 'user.performed_code_search', - 'user.performed_find_references', - 'user.performed_goto_definition' - ]; + const actions = [ + AUDIT_ACTIONS.CODE_SEARCH, + AUDIT_ACTIONS.FIND_REFERENCES, + AUDIT_ACTIONS.GOTO_DEFINITION + ];packages/web/src/ee/features/analytics/actions.ts (1)
23-98: Consider query performance optimization.This complex query with multiple CTEs and generate_series calls could be expensive for large datasets or wide date ranges.
Consider these optimizations:
- Add query timeout handling
- Consider pagination for very large date ranges
- Add database indexes on timestamp and orgId columns (if not already present)
- Consider caching results for frequently accessed data
+ // Consider adding query optimization + const queryTimeout = 30000; // 30 seconds + const rows = await prisma.$queryRaw<AnalyticsResponse>` + SET statement_timeout = ${queryTimeout}; WITH core AS (packages/web/src/ee/features/analytics/analyticsContent.tsx (3)
171-182: Consider extracting savings calculation logic to a utility function.The savings calculation logic here is duplicated in the main component (lines 369-374). Consider extracting this to a shared utility function to maintain DRY principles.
Create a utility function:
export function calculateSavings( totalOperations: number, avgMinutesSaved: number, avgSalary: number ): number { const totalMinutesSaved = totalOperations * avgMinutesSaved const hourlyRate = avgSalary / (40 * 52) // 40 hours/week, 52 weeks/year const hourlySavings = (totalMinutesSaved / 60) * hourlyRate return Math.round(hourlySavings * 100) / 100 }
309-309: Use Array.from for cleaner array generation.Replace the hardcoded array with a more idiomatic approach:
-{[1, 2, 3, 4, 5, 6, 7, 8, 9, 10].map((i) => ( +{Array.from({ length: 10 }, (_, i) => i + 1).map((i) => (
369-374: Good implementation, but consider reusing the savings calculation utility.As mentioned earlier, this calculation logic duplicates what's in the SavingsChart component. Once you extract the utility function, use it here as well.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (6)
docs/images/analytics_demo.mp4is excluded by!**/*.mp4docs/images/code_nav_chart.pngis excluded by!**/*.pngdocs/images/code_search_chart.pngis excluded by!**/*.pngdocs/images/cost_savings_chart.pngis excluded by!**/*.pngdocs/images/dau_chart.pngis excluded by!**/*.pngyarn.lockis excluded by!**/yarn.lock,!**/*.lock
📒 Files selected for processing (26)
CHANGELOG.md(1 hunks)docs/docs.json(1 hunks)docs/docs/configuration/audit-logs.mdx(4 hunks)docs/docs/configuration/environment-variables.mdx(1 hunks)docs/docs/features/analytics.mdx(1 hunks)packages/db/prisma/migrations/20250619231843_add_audit_indexes/migration.sql(1 hunks)packages/db/prisma/schema.prisma(1 hunks)packages/db/tools/scriptRunner.ts(2 hunks)packages/db/tools/scripts/inject-audit-data.ts(1 hunks)packages/shared/src/entitlements.ts(1 hunks)packages/web/package.json(3 hunks)packages/web/src/app/[domain]/browse/[...path]/components/pureCodePreviewPanel.tsx(5 hunks)packages/web/src/app/[domain]/components/searchBar/searchBar.tsx(2 hunks)packages/web/src/app/[domain]/settings/analytics/page.tsx(1 hunks)packages/web/src/app/[domain]/settings/layout.tsx(1 hunks)packages/web/src/auth.ts(1 hunks)packages/web/src/components/ui/chart.tsx(1 hunks)packages/web/src/ee/features/analytics/actions.ts(1 hunks)packages/web/src/ee/features/analytics/analyticsContent.tsx(1 hunks)packages/web/src/ee/features/analytics/analyticsEntitlementMessage.tsx(1 hunks)packages/web/src/ee/features/analytics/types.ts(1 hunks)packages/web/src/ee/features/audit/actions.ts(2 hunks)packages/web/src/env.mjs(1 hunks)packages/web/src/features/search/fileSourceApi.ts(1 hunks)packages/web/src/features/search/listReposApi.ts(1 hunks)packages/web/src/features/search/searchApi.ts(1 hunks)
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md
[duplication] ~10-~10: Possible typo: you repeated a word.
Context: ...pec/v2.0.0.html). ## [Unreleased] ### Added - Added analytics dashboard. [#358](https://git...
(ENGLISH_WORD_REPEAT_RULE)
docs/docs/features/analytics.mdx
[style] ~17-~17: Consider a more concise word here.
Context: ...e ensure you have audit logging enabled in order to see these insights. <video autoPlay ...
(IN_ORDER_TO_PREMIUM)
🪛 Biome (1.9.4)
packages/web/src/components/ui/chart.tsx
[error] 81-81: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build
🔇 Additional comments (29)
packages/web/package.json (1)
114-114: LGTM! Appropriate dependencies for the analytics dashboard.The added dependencies (
date-fnsandrecharts) and the updatedlucide-reactversion are suitable choices for implementing the analytics feature. These are well-maintained libraries with good community support.Also applies to: 123-123, 142-142
packages/web/src/features/search/listReposApi.ts (1)
8-10: Audit logging correctly removed from API layer.The removal of audit service imports and logging calls aligns with the PR objective of replacing API-based query audit events with UI-based audit events. The core functionality remains intact.
packages/web/src/components/ui/chart.tsx (1)
1-366: Well-structured chart component with excellent theming support!This is a comprehensive chart wrapper that provides:
- Theme-aware styling with CSS custom properties
- Custom tooltip and legend components with flexible configuration
- Proper TypeScript typing throughout
- Clean separation of concerns
The implementation follows React best practices and provides a good abstraction over Recharts.
CHANGELOG.md (1)
10-12: Changelog entry properly documents the new feature.The analytics dashboard addition is correctly documented in the "Unreleased" section following the Keep a Changelog format.
packages/web/src/app/[domain]/settings/layout.tsx (1)
88-91: Consider adding entitlement gating for the Analytics navigation item.The Analytics feature appears to require entitlement checks based on the PR summary mentioning "entitlement gating". Should this navigation item be conditionally rendered based on the user's analytics entitlement?
#!/bin/bash # Description: Check if analytics entitlement is being used elsewhere in the codebase # Search for analytics entitlement usage rg -A 3 "analytics.*entitlement|entitlement.*analytics" --type ts --type tsx # Search for the analytics page implementation to see if it has entitlement checks fd -e tsx -e ts "analytics" --exec grep -l "entitlement" {} \; # Check the specific analytics page file cat packages/web/src/app/[domain]/settings/analytics/page.tsx 2>/dev/null || echo "Analytics page file not found"docs/docs.json (1)
39-39: LGTM! Analytics documentation properly integrated.The analytics documentation page is correctly added to the Features navigation section, maintaining consistency with the existing structure.
docs/docs/configuration/environment-variables.mdx (1)
42-42: ```shell
#!/bin/bashList all occurrences of the environment variable across the repository
rg -n "SOURCEBOT_EE_AUDIT_LOGGING_ENABLED"
Check for default assignments in JSON, YAML, TS, or JS config/schema files
rg -n '"SOURCEBOT_EE_AUDIT_LOGGING_ENABLED".*default' -t json -t yaml -t ts -t js
Check for any hardcoded assignments in .env or shell scripts
rg -n '^SOURCEBOT_EE_AUDIT_LOGGING_ENABLED='
</details> <details> <summary>packages/db/prisma/migrations/20250619231843_add_audit_indexes/migration.sql (1)</summary> `1-5`: **LGTM! Well-designed indexes for analytics queries.** The composite indexes are properly structured for analytics use cases: - `idx_audit_core_actions_full` supports efficient org-scoped queries with time filtering - `idx_audit_actor_time_full` enables user-specific time-series analytics Column ordering follows best practices with high-cardinality fields first. </details> <details> <summary>packages/db/tools/scriptRunner.ts (2)</summary> `4-4`: **Clean script integration following established patterns.** The audit data injection script is properly imported and follows the existing code structure. --- `14-14`: **Script registration completed correctly.** The inject-audit-data script is properly registered in the scripts registry, maintaining consistency with existing script entries. </details> <details> <summary>packages/shared/src/entitlements.ts (2)</summary> `41-41`: **Analytics entitlement properly added to the system.** The new analytics entitlement is correctly added to the entitlements array, following the established pattern. --- `48-49`: **Enterprise plans correctly configured with analytics access.** Both self-hosted enterprise plans (regular and unlimited) properly include the analytics entitlement, maintaining the enterprise feature distinction while excluding cloud and OSS plans appropriately. </details> <details> <summary>packages/web/src/features/search/searchApi.ts (1)</summary> `129-129`: **Good practice: Unused parameter naming.** Renaming `apiKeyHash` to `_apiKeyHash` clearly indicates the parameter is unused after removing audit logging from the API level. This follows the convention of prefixing unused parameters with an underscore. </details> <details> <summary>packages/web/src/app/[domain]/components/searchBar/searchBar.tsx (1)</summary> `46-46`: **LGTM: Proper import of audit client.** The import statement correctly brings in the `createAuditClient` function for audit logging. </details> <details> <summary>packages/web/src/app/[domain]/settings/analytics/page.tsx (1)</summary> `7-9`: **Good component structure.** The default export pattern is clean and follows React conventions. </details> <details> <summary>packages/web/src/auth.ts (1)</summary> `144-159`: **LGTM: Parameter cleanup in signIn handler.** Removing the unused `account` parameter simplifies the function signature while maintaining the audit logging functionality. The audit logging implementation correctly handles user authentication events. Note: The TODO comment on line 152 suggests the organization ID handling may need attention for multi-tenant scenarios. </details> <details> <summary>packages/web/src/features/search/fileSourceApi.ts (1)</summary> `15-16`: **LGTM - Clean removal of audit logging from API route.** The changes correctly remove audit logging dependencies from the file source API. The underscore prefix on `_apiKeyHash` properly indicates an unused parameter, and removing the `org` parameter is consistent with no longer needing it for audit logging. </details> <details> <summary>packages/db/prisma/schema.prisma (1)</summary> `249-253`: **Well-designed indexes for analytics performance.** The new audit indexes are properly structured for analytics queries: - `idx_audit_core_actions_full` efficiently supports org-scoped time-series analytics - `idx_audit_actor_time_full` enables fast user-specific activity queries The descriptive comments and clear naming convention make the intent obvious. </details> <details> <summary>docs/docs/configuration/audit-logs.mdx (2)</summary> `43-43`: **Documentation accurately reflects the new audit action naming.** The updated action names from `"query.code_search"` to `"user.performed_code_search"` properly reflect the shift to UI-based audit logging and provide clearer semantic meaning. Also applies to: 57-57, 71-71 --- `119-121`: **Audit action types table correctly updated.** The new entries for `user.performed_code_search`, `user.performed_find_references`, and `user.performed_goto_definition` with consistent actor/target types properly document the new audit actions. </details> <details> <summary>packages/web/src/ee/features/analytics/analyticsEntitlementMessage.tsx (1)</summary> `1-47`: **Well-implemented enterprise feature gating component.** The component follows React and accessibility best practices: - Proper use of semantic HTML and design system components - External link includes security attributes (`rel="noopener"`) - Clear, user-friendly messaging about enterprise features - Responsive design with appropriate styling The implementation effectively guides users toward requesting trial access. </details> <details> <summary>packages/web/src/app/[domain]/browse/[...path]/components/pureCodePreviewPanel.tsx (3)</summary> `20-21`: **Proper imports and setup for UI-based audit logging.** The imports and domain hook usage are correctly implemented to support the new audit logging approach. Also applies to: 45-45 --- `140-145`: **Audit logging correctly implemented for find references action.** The audit event creation follows the proper pattern: - Uses the new `user.performed_find_references` action name - Includes meaningful metadata with the symbol name - Properly scoped to the current domain - Dependency array correctly updated to include domain Also applies to: 157-157 --- `164-169`: **Audit logging correctly implemented for goto definition action.** The audit event creation is consistent with the find references implementation: - Uses the proper `user.performed_goto_definition` action name - Includes symbol name in metadata for traceability - Properly integrated with domain context - Dependency array correctly maintains domain reference Also applies to: 198-198 </details> <details> <summary>packages/web/src/ee/features/analytics/types.ts (1)</summary> `1-10`: **Well-structured schema definition.** The Zod schema effectively validates analytics response data with appropriate types for time-based analytics. The period enum, date bucket, and numeric metrics are correctly defined. </details> <details> <summary>packages/web/src/ee/features/analytics/analyticsContent.tsx (4)</summary> `1-1`: **LGTM!** Correct use of the "use client" directive for this interactive dashboard component. --- `29-153`: **Well-implemented chart component with proper theming and formatting.** The AnalyticsChart component demonstrates good practices: - Proper UTC to local date conversion for display - Clean value formatting with K/M abbreviations - Comprehensive tooltip implementation - Good use of gradients and theming --- `519-519`: **Safe type assertions given the data filtering context.** The type assertions for period are safe here because the data has already been filtered by period type (day/week/month). Also applies to: 536-536 --- `595-596`: **Good UX with comprehensive operation count display.** Excellent user experience touch showing the total number of operations that the savings calculation is based on. The use of `toLocaleString()` for number formatting is a nice detail. </details> </blockquote></details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
packages/web/src/app/[domain]/browse/[...path]/components/pureCodePreviewPanel.tsx
Outdated
Show resolved
Hide resolved
packages/web/src/app/[domain]/browse/[...path]/components/pureCodePreviewPanel.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (2)
CHANGELOG.md (1)
16-17: Addresses previous feedback: Audit logging default change documented.This entry correctly addresses the previous review comment about documenting that audit logs are now enabled by default.
docs/docs/configuration/audit-logs.mdx (1)
15-16: Addresses previous feedback but fix phrase repetition.This correctly addresses the previous review comment about updating the section since audit logs are now enabled by default. However, there's a phrase repetition issue to fix.
-## Enabling/Disabling Audit Logs -Audit logs are enabled by default and can be controlled with the `SOURCEBOT_EE_AUDIT_LOGGING_ENABLED` [environment variable](/docs/configuration/environment-variables). +## Enabling/Disabling Audit Logs +Audit logging is enabled by default and can be controlled with the `SOURCEBOT_EE_AUDIT_LOGGING_ENABLED` [environment variable](/docs/configuration/environment-variables).
🧹 Nitpick comments (1)
docs/docs/features/analytics.mdx (1)
17-17: Minor style improvement: Consider more concise phrasing.Consider replacing "in order to see" with "to see" for more concise writing.
-This dashboard is backed by [audit log](/docs/configuration/audit-logs) events. Please ensure you have audit logging enabled in order to see these insights. +This dashboard is backed by [audit log](/docs/configuration/audit-logs) events. Please ensure you have audit logging enabled to see these insights.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (11)
CHANGELOG.md(1 hunks)docs/docs/configuration/audit-logs.mdx(5 hunks)docs/docs/features/analytics.mdx(1 hunks)packages/web/src/app/[domain]/browse/[...path]/components/pureCodePreviewPanel.tsx(5 hunks)packages/web/src/app/[domain]/components/searchBar/searchBar.tsx(2 hunks)packages/web/src/app/[domain]/search/components/codePreviewPanel/codePreview.tsx(5 hunks)packages/web/src/ee/features/analytics/analyticsContent.tsx(1 hunks)packages/web/src/ee/features/analytics/analyticsEntitlementMessage.tsx(1 hunks)packages/web/src/ee/features/audit/actions.ts(2 hunks)packages/web/src/ee/features/audit/factory.ts(1 hunks)packages/web/src/initialize.ts(0 hunks)
💤 Files with no reviewable changes (1)
- packages/web/src/initialize.ts
✅ Files skipped from review due to trivial changes (1)
- packages/web/src/ee/features/analytics/analyticsContent.tsx
🚧 Files skipped from review as they are similar to previous changes (4)
- packages/web/src/app/[domain]/components/searchBar/searchBar.tsx
- packages/web/src/ee/features/analytics/analyticsEntitlementMessage.tsx
- packages/web/src/ee/features/audit/actions.ts
- packages/web/src/app/[domain]/browse/[...path]/components/pureCodePreviewPanel.tsx
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md
[duplication] ~10-~10: Possible typo: you repeated a word.
Context: ...pec/v2.0.0.html). ## [Unreleased] ### Added - Added analytics dashboard. [#358](https://git...
(ENGLISH_WORD_REPEAT_RULE)
[duplication] ~13-~13: Possible typo: you repeated a word.
Context: ...//pull/358) ### Fixed - Fixed issue where invites appeared to be crea...
(ENGLISH_WORD_REPEAT_RULE)
docs/docs/configuration/audit-logs.mdx
[grammar] ~15-~15: This phrase is duplicated. You should probably use “Audit Logs” only once.
Context: ...ebot deployment. ## Enabling/Disabling Audit Logs Audit logs are enabled by default and can be contr...
(PHRASE_REPETITION)
docs/docs/features/analytics.mdx
[style] ~17-~17: Consider a more concise word here.
Context: ...e ensure you have audit logging enabled in order to see these insights. <video autoPlay ...
(IN_ORDER_TO_PREMIUM)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build
🔇 Additional comments (11)
packages/web/src/app/[domain]/search/components/codePreviewPanel/codePreview.tsx (5)
24-25: LGTM: Proper audit logging imports added.The imports for audit logging functionality are correctly added and align with the PR's objective to track user interactions for analytics.
56-56: LGTM: Domain context properly retrieved.The
useDomainhook is correctly used to get the current domain context for audit logging.
123-128: LGTM: Audit logging for goto definition action.The audit logging implementation correctly captures the goto definition action with appropriate metadata. The action name follows the standardized
"user.performed_*"convention mentioned in the documentation.
167-172: LGTM: Audit logging for find references action.The audit logging implementation correctly captures the find references action with appropriate metadata, consistent with the goto definition implementation.
163-163: LGTM: Dependencies correctly updated.The dependency arrays for both callbacks properly include the
domainparameter to ensure the callbacks are recreated when the domain changes.Also applies to: 190-190
packages/web/src/ee/features/audit/factory.ts (2)
4-4: LGTM: Appropriate entitlement import added.The
hasEntitlementimport is correctly added to support the new entitlement-based audit logging enablement.
10-11: LGTM: Enhanced audit logging enablement logic.The updated logic correctly combines both environment variable check and entitlement verification, following security best practices. This ensures audit logging is only enabled when both configuration is set and the organization has the appropriate entitlement.
CHANGELOG.md (1)
10-11: LGTM: Analytics dashboard feature properly documented.The changelog entry correctly documents the addition of the analytics dashboard feature with appropriate PR reference.
docs/docs/features/analytics.mdx (1)
1-51: LGTM: Comprehensive analytics feature documentation.The documentation provides excellent coverage of the analytics dashboard features, including clear descriptions of metrics, visual examples, and proper license key requirements. The structure and content align well with the PR's analytics dashboard implementation.
docs/docs/configuration/audit-logs.mdx (2)
43-43: LGTM: Updated audit action names in examples.The example responses correctly use the new
"user.performed_code_search"action name, consistent with the new audit action naming convention.Also applies to: 57-57, 71-71
119-121: LGTM: Updated audit action types table.The audit action types table correctly reflects the new
"user.performed_*"action naming convention, replacing the previous generic approach with more specific user interaction tracking.
analytics_demo.mp4
Summary by CodeRabbit
New Features
Enhancements
Bug Fixes
Documentation
Chores