Skip to content

Support HTTP query parameters in httpjson filebeat input #20559

@spinscale

Description

@spinscale

Describe the enhancement: The httpjson filebeat input only works if the API contains all information in the JSON. However there are a lot of APIs where pagination is not part of the request JSON (because there may be none), but the pagination information is stored in HTTP query parameters. Those APIs should be support as well. This also means that one needs to have the ability of to keep state on the beats side like counting up an integer, as many APIs do not offer that as part of their response.

Describe a specific use case for the enhancement or feature: APIs like the GitHub API use HTTP query parameters for pagination, i.e. per_page and page for the current page number. See https://docs.github.com/en/rest/reference/orgs#list-organization-members

Metadata

Metadata

Assignees

No one assigned

    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