ELK and disk space

[danliberti]

Hi everyone,

I’m deploying OptScale and manage a large number of accounts. I’ve noticed this generates a significant amount of data in ELK.

I’d like to understand whether ELK is strictly required, or if it’s acceptable to install OptScale without the --with-elk flag. For testing, I started an installation without ELK and didn’t notice any issues.

Is it safe to remove the /optscale/elk directory without affecting data collection or overall functionality?

Are there known features or workflows in OptScale that specifically depend on ELK?

Thanks in advance for any guidance!

[fiblan]

To reduce a significant amount of data in Elk, you can enable the cleanelkdb CronJob by setting deploy_cleanelkdb: "true".
https://github.com/hystax/optscale/blob/integration/documentation/periodic_jobs.md#cleanelkdb

ELK is disabled by default. You can not install ELK, but you’ll lose centralized logging and Kibana for troubleshooting — filebeat is configured to send logs to Logstash, so either reconfigure filebeat to an external ELK or accept no centralized logs.

[danliberti]

Hi @fiblan, tks for the explanation

i'll disable elk and setup clean of mongodb via job