fix: adapt event_type to be fetched from descripto#150
Closed
betinacosta wants to merge 5 commits into
Closed
Conversation
betinacosta
changed the title
betinacosta
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated the auditlog-ng client audit log event name handling to derive the event name directly from the protobuf event descriptor.
Previously, event names were in the format:
sap.als.AuditEvent.<EVENT_TYPE>.v2
With this change, event names now follow the protobuf descriptor naming convention:
sap.auditlog.auditevent.v2.<EVENT_TYPE>
Example:
sap.auditlog.auditevent.v2.ConfigurationChange
This aligns the OTEL event name format with the ALS protobuf schema and the Audit Log SDK implementation, where the event type is resolved from the protobuf DESCRIPTOR.
Breaking Changes
The auditlog-ng client no longer supports user-provided audit event types. Event names are now derived exclusively from the protobuf event descriptor (DESCRIPTOR) and follow the protobuf schema naming convention: