-
Notifications
You must be signed in to change notification settings - Fork 81
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
Add output type kafka to agent policies #2850
Add output type kafka to agent policies #2850
Conversation
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.
LGTM 🚀
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.
Log message typo but otherwise looks good
internal/pkg/policy/policy_output.go
Outdated
@@ -54,6 +55,9 @@ func (p *Output) Prepare(ctx context.Context, zlog zerolog.Logger, bulker bulk.B | |||
case OutputTypeLogstash: | |||
zlog.Debug().Msg("preparing logstash output") | |||
zlog.Info().Msg("no actions required for logstash output preparation") | |||
case OutputTypeKafka: | |||
zlog.Debug().Msg("preparing kafka output") | |||
zlog.Info().Msg("no actions required for logstash kafka preparation") |
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.
"logstash kafka" -> "kafka output" :-)
What is the problem this PR solves?
fleet-server gives an error if kafka appears an the output type in an agent policy.
How does this PR solve the problem?
Add
OutputTypeKafka
to policy output as a nop similar to logstash handling.Design Checklist
I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration files./changelog/fragments
using the changelog toolRelated issues