feat: add wildcard pattern support for logging header capture (e.g. x-custom-*)

[BearTS]

Summary

Adds wildcard pattern support to the logging headers configuration, allowing users to capture groups of headers by prefix (e.g. x-custom-*) or all headers at once using *, rather than only exact header name matches.

Changes

• Introduced loggingHeaderMatchesPattern to handle exact matches, trailing wildcard (x-custom-*), and bare wildcard (*) patterns against incoming header names
• Updated captureLoggingHeaders to iterate over all request headers and match each against configured patterns, replacing the previous single-key lookup
• Updated the UI description and placeholder text to document wildcard support

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

Configure logging headers with a wildcard pattern such as x-custom-* or * and send requests with matching headers. Verify that the captured headers appear in the metadata field of log entries.

go test ./plugins/logging/...

cd ui
pnpm i || npm i
pnpm test || npm test
pnpm build || npm run build

Screenshots/Recordings

Before: Placeholder showed X-Tenant-ID, X-Request-Source, X-Correlation-ID with no mention of wildcard support.

After: Placeholder shows X-Tenant-ID, X-Request-Source, x-custom-* and the description explains exact names, prefix wildcards, and the bare * option.

Breaking changes

• Yes
• No

Related issues

Security considerations

Using * as a logging header pattern will capture all request headers, which may include sensitive values such as Authorization or session tokens. Users should be aware of the PII and secrets exposure risk when enabling broad wildcard patterns, and ensure log storage is appropriately access-controlled.

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

  • Logging headers configuration now supports wildcard patterns (e.g., x-custom-*, *) as well as exact names.
  • Request headers matching configured patterns are automatically captured as metadata, with support for bare (*) and prefix (prefix*) wildcards.
  • Headers with the x-bf-lh- prefix are always captured.

• Documentation

  • Clarified logging configuration help text and updated placeholder examples for header input.
  • Shortened Models section copy to “Attach descriptions and tags to specific models.”

[coderabbitai]

📝 Walkthrough

Walkthrough

Adds wildcard pattern matching for configured logging headers (exact, *, prefix*) in the backend and updates UI help text/placeholder to document wildcard usage; also tweaks a Models subheading string in the UI.

Changes

Logging Header Wildcard Patterns

Layer / File(s)	Summary
Backend wildcard pattern matching implementation plugins/logging/main.go	New loggingHeaderMatchesPattern helper supports exact match, bare wildcard (*), and trailing-prefix patterns (prefix*) for lowercased names. captureLoggingHeaders now iterates configured patterns (lowercased/trimmed), matches them against all request header names, and adds matched header/value pairs to metadata.
Logging UI help text and placeholder update ui/app/workspace/config/views/loggingView.tsx	Updated "Logging Headers" help text to document comma-separated header names and wildcard patterns with examples (x-custom-*, *), notes that x-bf-lh- headers are always captured, and changed the textarea placeholder to X-Tenant-ID, X-Request-Source, x-custom-*.

Model Catalog UI Text

Layer / File(s)	Summary
Models subheading text replacement ui/app/workspace/model-catalog/views/attributesTab.tsx	Replaced the subheading text under "Models" with: “Attach descriptions and tags to specific models.”

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hopped through headers, wild and neat,
I taught them patterns, trim and sweet.
From prefix blooms to every star (*),
UI signs point to where they are.
A nibble of docs, a tiny tweak — hooray!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main feature being added: wildcard pattern support for logging header capture with a concrete example.
Description check	✅ Passed	The description comprehensively covers all key template sections including summary, changes, type, affected areas, testing, screenshots, security considerations, and breaking changes acknowledgment.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 06-01-feat_support_wildcard_on_request_headers

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.12.2)

level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"

---

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

[BearTS]

• feat: add log_pre_transform_request_data config to capture original client HTTP body before Bifrost transformations #3964
• feat: add wildcard pattern support for logging header capture (e.g. x-custom-*) #3958 👈 (View in Graphite)
• 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 well-scoped, the matching logic is correct, and the wildcard behaviour is consistent with how header keys are stored.

The matching helper covers all three code paths correctly, header lowercasing is handled consistently between the transport layer and the new pattern loop, the UI preserves E2E test identifiers, and no existing behaviour is regressed.

No files require special attention.

Important Files Changed

Filename	Overview
plugins/logging/main.go	Adds loggingHeaderMatchesPattern and updates captureLoggingHeaders to iterate all headers and match against configured patterns; logic is correct, header keys are pre-lowercased by the transport layer, and the new O(patterns x headers) loop is acceptable for typical header counts.
ui/app/workspace/config/views/loggingView.tsx	Updates description text and placeholder to document wildcard pattern support; data-testid attribute preserved, no logic changes.
ui/app/workspace/model-catalog/views/attributesTab.tsx	Removes 'Editorial - decoupled from pricing sync.' from the Models section description; cosmetic-only, unrelated to the wildcard feature.

_{Reviews (2): Last reviewed commit: "feat: support wildcard on request header..." | Re-trigger Greptile}

[coderabbitai]

Actionable comments posted: 1

🤖 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.

Inline comments:
In `@ui/app/workspace/config/views/loggingView.tsx`:
- Around line 237-240: Add a short security note to the header capture help text
in loggingView.tsx warning that wildcard patterns (especially "*" ) will capture
all headers including sensitive ones like Authorization/API keys; update the JSX
text block that currently describes comma-separated and wildcard header patterns
(the help text string around "Comma-separated list of request headers to
capture...") to append a concise sentence such as "Note: '*' captures all
headers — review for sensitive data before enabling." so users are explicitly
warned about possible exposure.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 39dedea0-569f-421a-9b4e-6087e324299b

📥 Commits

Reviewing files that changed from the base of the PR and between a70594c and f67aaef.

📒 Files selected for processing (2)

• plugins/logging/main.go
• ui/app/workspace/config/views/loggingView.tsx

[coderabbitai]

Actionable comments posted: 1

🤖 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.

Inline comments:
In `@plugins/logging/main.go`:
- Around line 483-488: When iterating allHeaders in the wildcard scan (the loop
over for hKey, hVal := range allHeaders where
loggingHeaderMatchesPattern(pattern, hKey) is checked) skip any header whose
name starts with the normalized prefix "x-bf-lh-" so those headers are not added
again into metadata; implement a guard before creating/setting metadata that
continues the loop if strings.HasPrefix(strings.ToLower(hKey), "x-bf-lh-") (or
equivalent) to avoid duplicating headers already handled by the dedicated
normalized block.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2ea59c8f-80e6-44ef-87a8-b8fe4c8f685e

📥 Commits

Reviewing files that changed from the base of the PR and between f67aaef and d26c778.

📒 Files selected for processing (3)

• plugins/logging/main.go
• ui/app/workspace/config/views/loggingView.tsx
• ui/app/workspace/model-catalog/views/attributesTab.tsx

[akshaydeo]

Merge activity

• Jun 3, 6:54 AM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 3, 6:54 AM UTC: @akshaydeo merged this pull request with Graphite.