-
Notifications
You must be signed in to change notification settings - Fork 71
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
confgenerator : Add otel logging support for systemd_journald
receiver.
#1872
base: master
Are you sure you want to change the base?
Conversation
6e369a7
to
c731e31
Compare
systemd_journald
receiver.systemd_journald
receiver.
@@ -682,6 +682,61 @@ func (r LoggingReceiverSystemd) Components(ctx context.Context, tag string) []fl | |||
return input | |||
} | |||
|
|||
func (r LoggingReceiverSystemd) Pipelines(ctx context.Context) ([]otel.ReceiverPipeline, error) { | |||
operators := []map[string]any{} | |||
operators = append(operators, map[string]any{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should use ModifyFields
here instead of using the deprecated operators
option to do these manipulations.
}) | ||
} | ||
|
||
func testSystemdLog(t *testing.T, otel bool) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to see this actually test the schema of the log entries, instead of just testing that one exists.
Probably that means we should send a particular canary message to journald and then check how it is represented in Cloud Logging.
Description
Add otel logging support for
systemd_journald
receiver.Related issue
b/394593541
How has this been tested?
Checklist: