Skip to content

cloudflare_logpush: expose max_in_flight_bytes and retry_after input options to the user for configuration #11912

@efd6

Description

@efd6

The next 8.16 version of the http_endpoint input in beats will have max_in_flight_bytes and retry_after options that allow specification of behaviour for when downstream processing cannot keep up with pushed events. We should expose these options to the user when they become available.

Metadata

Metadata

Assignees

Labels

Integration:cloudflare_logpushCloudflare LogpushTeam:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]bugSomething isn't working, use only for issuesenhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions