Skip to content
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

x-pack/filebeat/input/entityanalytics/{okta,azuread/fetcher/graph}: add ability to remove request trace logs #40004

Merged
merged 1 commit into from
Jun 28, 2024

Commits on Jun 28, 2024

  1. x-pack/filebeat/input/entityanalytics/{okta,azuread/fetcher/graph}: a…

    …dd ability to remove request trace logs
    
    This is essentially a replay of elastic#39969, but for the entity analytics
    providers.
    
    The previous configuration system did not allow users to remove trace
    logs from agents after they are no longer needed. This is potential
    security risk as it leaves potentially sensitive information on the file
    system beyond its required lifetime. The mechanism for communicating to
    the input whether to write logs is not currently powerful enough to
    indicate that existing logs should be removed without deleting logs from
    other instances. So add an enabled configuration option to allow the
    target name to be sent independently of whether the files should be
    written or removed.
    
    The new option is optional, defaulting to the previous behaviour so
    that it can be opted into via progressive repair in the client
    integrations.
    efd6 committed Jun 28, 2024
    Configuration menu
    Copy the full SHA
    01b288a View commit details
    Browse the repository at this point in the history