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: Check for mountpoint during Elastic size limit calculations #12308

Merged
merged 1 commit into from
Feb 12, 2024

Conversation

petiepooo
Copy link
Contributor

Instead of just directory existence, this checks if the directories are separate mountpoints when determining disk size and log_size_limit calculations.

It also sets the percentage to 80 if /nsm/elasticsearch is a separate mountpoint. This allows for better disk utilization on server configurations where /nsm is based on large slow HDDs for increased PCAP retention but /nsm/elasticsearch is based on SSDs for faster Elasticsearch performance.

The mountpoint command has been in RHEL and derivatives at least to RHEL7, and debian and derivatives for just as long.

Instead of just existence, this checks if the directories are separate mountpoints when determining disk size and log_size_limit calculations.

It also sets the percentage to 80 if /nsm/elasticsearch is a separate mountpoint.  This allows for better disk utilization on server configurations where /nsm is based on large slow HDDs for increased PCAP retention but /nsm/elasticsearch is based on SSDs for faster Elasticsearch performance.
@petiepooo
Copy link
Contributor Author

It looks like there's similar logic in soup.. would you like that added to this PR as well?

@TOoSmOotH TOoSmOotH changed the title feat: check for mountpoint during Elastic size limit calculations FEATURE: Check for mountpoint during Elastic size limit calculations Feb 12, 2024
@TOoSmOotH
Copy link
Contributor

It looks like there's similar logic in soup.. would you like that added to this PR as well?

That is legacy code that isn't called anymore.

@TOoSmOotH TOoSmOotH merged commit 2db5f4d into Security-Onion-Solutions:2.4/dev Feb 12, 2024
2 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Feb 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants