Skip to content

all capabilities emit beholder logs automatically#1844

Closed
patrickhuie19 wants to merge 1 commit intomainfrom
feat/add-beholder-logger-to-all-loops
Closed

all capabilities emit beholder logs automatically#1844
patrickhuie19 wants to merge 1 commit intomainfrom
feat/add-beholder-logger-to-all-loops

Conversation

@patrickhuie19
Copy link
Copy Markdown
Contributor

While looking at some gaps in logs from trigger capabilities in prod, I realized we could benefit in the capabilities by pushing everything through the beholder logger. The alternative is leaving it up to individual capabilities as to which of their logs go through beholder or not, but as we expect logs to eventually end up in our internal log viewer, this shouldn't be a security issue anyways.

@github-actions
Copy link
Copy Markdown

✅ API Diff Results - No breaking changes


📄 View full apidiff report

@patrickhuie19
Copy link
Copy Markdown
Contributor Author

cc @pkcll

@github-actions
Copy link
Copy Markdown

This PR is stale because it has been open 30 days with no activity.
Remove the stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Mar 21, 2026
@github-actions
Copy link
Copy Markdown

This PR has been automatically closed because it has been stale for > 30 days.
If you wish to continue working on this PR, please reopen it and make any necessary changes.

@github-actions github-actions bot closed this Mar 28, 2026
@github-actions github-actions bot deleted the feat/add-beholder-logger-to-all-loops branch March 28, 2026 00:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant