feat: add alias column to materialized view and filter support

[impoiler]

Summary

Adds alias as a dimension to the mv_logs_hourly materialized view, enabling filtering and grouping of log analytics by alias.

Changes

• Added alias to the SELECT clause of the materialized view query using COALESCE(alias, '') AS alias
• Updated the GROUP BY clause to include the new alias column
• Added alias to the unique index mv_logs_hourly_uniq to maintain correctness for concurrent refreshes
• Added alias to mvLogsHourlyRequiredColumns so schema validation and repair paths recognize it as a required column
• Added filtering support for alias in applyMatViewFiltersOnly using the Aliases field from SearchFilters

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

go test ./...

After deploying, verify that:

1. The materialized view is refreshed or recreated with the alias column present
2. Querying log analytics with an alias filter returns correctly scoped results
3. The unique index on mv_logs_hourly includes alias without conflicts

Breaking changes

• Yes
• No

The unique index definition has changed. The existing materialized view and its index will need to be dropped and recreated (or handled via the startup ensure/repair path) to reflect the new schema. Existing deployments should verify that the repair path correctly detects and applies the updated column set.

Related issues

#4071

Security considerations

No security implications. alias is an existing log attribute being surfaced as an analytics dimension.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

Summary by CodeRabbit

• New Features
  • Logs hourly aggregation now includes alias as a visible dimension for hourly summaries.
  • Added support for filtering/searching logs by alias, enabling more precise and efficient log queries.

[coderabbitai]

Warning

Review limit reached

@impoiler, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 10 minutes and 30 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: efbe867a-3dad-4ca9-8fe4-5a78e246566e

📥 Commits

Reviewing files that changed from the base of the PR and between c829950 and 107ef5b.

📒 Files selected for processing (1)

• framework/logstore/matviews.go

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 06-05-fix_bug_add_alias_filter_support_for_matview_queries

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[impoiler]

• fix: broaden Mantle model matching to all gpt variants #4091
• test: remove TestCollectApplicableGovernanceIDs_UserScopedModelConfigs #4090
• feat: add business unit CRUD, team assignment, and governance endpoints to OpenAPI spec #4082
• feat: add inline loading shell to #root before React mounts #4063
• fix: reduce FTS index left() cap from 800k to 250k chars to stay within tsvector limit #4057
• feat: add alias column to materialized view and filter support #4078 👈 (View in Graphite)
• feat: add "View logs" menu item to customer, team, and virtual key tables #4073
• feat: extract BudgetDisplay component with progress bar and tooltip #4055
• feat: add clickable links for routing rule, selected key, virtual key, and prompt in log detail views #4054
• fix: standardize page container layout with no-padding-parent and 100dvh sizing #4046
• fix: add colored tooltip values and subtle cursor highlight to dashboard charts #4044
• feat: add customer detail sheet and remove inline usage section from customer sheet #4026
• fix: replicates vk hierarchy flow for ghost nodes reconcilation #4088
• feat: supports multiple customers logs and usage tracking #4066
• fix: fixes virtual key model configs UI #4052
• fix: fixes cascade deletes for model configs #4051
• feat: adds support for multiple team and bu units in logstore #4041
• feat: adds team budget and rl collection exporters #4040
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Confidence Score: 5/5

Safe to merge; the change is additive, follows the established scalar-column pattern, and the startup repair path correctly handles existing deployments via mvLogsHourlyRequiredColumns.

All five touched locations (DDL SELECT, GROUP BY, unique index, required-columns list, filter helper) are internally consistent. The alias column uses COALESCE(alias, '') matching every other nullable scalar column in the view. The repair path will detect any existing view missing the new column and drop-recreate it. No logic errors, data-correctness issues, or concurrency problems were found.

No files require special attention.

Important Files Changed

Filename	Overview
framework/logstore/matviews.go	Adds alias as a GROUP BY dimension to mv_logs_hourly, its unique index, required-columns list, and applyMatViewFiltersOnly; follows the established scalar-column pattern used by user_id/virtual_key_id; repair path correctly picks up the new column via mvLogsHourlyRequiredColumns.

_{Reviews (5): Last reviewed commit: "fix: [BUG] add alias filter support for ..." | Re-trigger Greptile}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

framework/logstore/matviews.go (1)

69-83: ⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

Avoid rebuilding mv_logs_hourly in place during a rolling deploy.

Adding alias to mvLogsHourlyRequiredColumns forces repairMatViewShapes to DROP MATERIALIZED VIEW ... CASCADE on every upgrade from the old shape. Existing replicas can still have matViewsReady=true and keep routing eligible reads to mv_logs_hourly, so they can hit relation "mv_logs_hourly" does not exist between the drop and recreate/index phase. This needs a staged migration path or a temporary cluster-wide fallback to raw queries instead of an in-place repair.

As per coding guidelines, framework/** changes should preserve backward-compatible data formats and check migration behavior carefully.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@framework/logstore/matviews.go` around lines 69 - 83, The change to
mvLogsHourlyRequiredColumns (adding "alias") causes repairMatViewShapes to DROP
and recreate mv_logs_hourly in-place, which breaks rolling deploys; instead,
modify the migration approach: avoid dropping mv_logs_hourly inside
repairMatViewShapes when only adding a nullable/optional column—either implement
a staged migration that creates a new materialized view name (e.g.,
mv_logs_hourly_v2), backfills it, then atomically swap readers, or have
repairMatViewShapes detect incompatible shapes and set matViewsReady=false so
code routes reads to raw queries until all replicas are upgraded. Update
mvLogsHourlyRequiredColumns and repairMatViewShapes to follow this staged path
(or fall back to raw queries) rather than performing DROP ... CASCADE on
mv_logs_hourly during rolling upgrades.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@framework/logstore/matviews.go`:
- Around line 69-83: The change to mvLogsHourlyRequiredColumns (adding "alias")
causes repairMatViewShapes to DROP and recreate mv_logs_hourly in-place, which
breaks rolling deploys; instead, modify the migration approach: avoid dropping
mv_logs_hourly inside repairMatViewShapes when only adding a nullable/optional
column—either implement a staged migration that creates a new materialized view
name (e.g., mv_logs_hourly_v2), backfills it, then atomically swap readers, or
have repairMatViewShapes detect incompatible shapes and set matViewsReady=false
so code routes reads to raw queries until all replicas are upgraded. Update
mvLogsHourlyRequiredColumns and repairMatViewShapes to follow this staged path
(or fall back to raw queries) rather than performing DROP ... CASCADE on
mv_logs_hourly during rolling upgrades.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 72243e0e-f1de-46b3-887f-7ec70896c7f1

📥 Commits

Reviewing files that changed from the base of the PR and between e9ef1b2 and 5816c9f.

📒 Files selected for processing (1)

• framework/logstore/matviews.go

[akshaydeo]

Merge activity

• Jun 5, 2:00 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 5, 2:19 PM UTC: @akshaydeo merged this pull request with Graphite.