Skip to content

feat(logs): Handle inbound filters for logs #4938

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

Zylphrex
Copy link
Member

This adds support for the release inbound filter on logs. We currently do not support client ip because logs do not have an ip attribute.

This adds support for the release inbound filter on logs. We currently do not
support client ip because logs do not have an ip attribute.
@Zylphrex Zylphrex requested a review from a team as a code owner July 14, 2025 15:37
Copy link
Member

@Dav1dde Dav1dde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is going to be a bigger change. Inbound filters must be evaluated in the first layer that is applicable. Meaning it cannot be guarded by a if is_processing as it is now.

Since this is the first thing which requires it, we will also have to move normalization to the same layer, as the filtering can depend on attributes of the normalization. As a result of this we will need a proper way of keeping track and validating the origin of the original byte count of a log.

Unfortunately this is now hitting your PR, but these steps were skipped when originally implementing logs, it is now catching up to us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants