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

Feature request: add a configurable and persistent storage for agent unset messages #23446

Closed
2 tasks
pereyra-m opened this issue May 15, 2024 · 1 comment
Closed
2 tasks
Labels
duplicated This issue or pull request already exists type/enhancement New feature or request

Comments

@pereyra-m
Copy link
Member

Wazuh version Component Install type Install method Platform
All Logcollector Agent Packages/Sources OS version

Description

An user has made a feature request at #23377.

It happens that currently the agent has only two different mechanisms to avoid missing logs with logcollector

  • The only_future_events option to keep reading files since the last timestamp when the agent was running
  • The leaky bucket, that holds in memory the events until the connection is re-established

The second in particular has some drawbacks, for example:

  • A restart of the agent during the disconnection period causes the loss of all events in memory
  • The disconnection period could be long, and the buffer insufficient

That's why @protocolpaladin proposed a configurable log retention threshold with high capacity (GBs) to store the logs until they can be sent to the manager.

DoD

  • The corresponding team analyzes the feature request
  • The feature is included in the backlog or rejected
@pereyra-m pereyra-m added the type/enhancement New feature or request label May 15, 2024
@vikman90
Copy link
Member

@pereyra-m this issue seems to be a duplicate of #15294.

@vikman90 vikman90 closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
@vikman90 vikman90 added the duplicated This issue or pull request already exists label May 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicated This issue or pull request already exists type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants