Provide support of configuring ignore_older events in apache access-logs #10809
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andrewkroh
added
Integration:apache
andrewkroh
approved these changes
Aug 19, 2024
|
/test |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
|
|
|
@muthu-mps or @ishleenk17 also gently asking for review of this PR. Thank you |
|
Package apache - 1.25.0 containing this change is available at https://epr.elastic.co/search?package=apache |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please label as enhancement
Currently, there is no option for ignoring events older than X. This can be problematic, if there are hundreds of gigabytes of historical logfiles, that cannot be deleted, but shall not be ingested in Elastic.'
In more detail: We have apache as an internal core reverse-proxy and save the access logs on a fileshare, where elastic agent should ingest them. However some production environments have an uncompressed volume size of up to 227 GB, which currently should not all be ingested into Elastic, as there might be other retention periods as we currently have on our fileshare.
Therefore this option should prevent the ingestion of those old files, and should be configurable the same way, as it is already possible in the custom log integration.