Skip to content

Conversation

atburke
Copy link
Contributor

@atburke atburke commented Oct 9, 2025

This change updates events.FromEventFields to return unknown event when an event fails to unmarshal, instead of the unmarshal error. This prevents a single malformed audit event from breaking the entire webui audit log.

Follow-up to #59882.

Changelog: Fixed malformed audit events breaking the audit log

@tigrato
Copy link
Contributor

tigrato commented Oct 11, 2025

Is it possible to avoid using unknown here and fallback to the correct event that we miss?

@atburke
Copy link
Contributor Author

atburke commented Oct 14, 2025

@tigrato we could for scp events. For any other malformed events, I don't think there's a way to know ahead of time which event to correct to.

@rosstimothy
Copy link
Contributor

@tigrato we could for scp events. For any other malformed events, I don't think there's a way to know ahead of time which event to correct to.

Can we do both here? I agree that an unknown event in the ui is better than an error that prevents viewing any events. However, for the SCP case, can we detect the error and create the appropriate event so it isn't display as an unknown event?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants