# Proper maintenance of the Elastic Stack

**URL:** <https://discuss.elastic.co/t/proper-maintenance-of-the-elastic-stack/312030>\
**Category:** Elasticsearch\
**Created:** [August 12, 2022, 5:31pm UTC](https://discuss.elastic.co/t/proper-maintenance-of-the-elastic-stack/312030 "2022-08-12T17:31:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![MKirby](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MKirby](https://discuss.elastic.co/u/MKirby)\
**Post date:** [August 12, 2022, 5:31pm UTC](https://discuss.elastic.co/t/proper-maintenance-of-the-elastic-stack/312030/1 "2022-08-12T17:31:20Z")

</div>

Good Afternoon Elasticsearch Guru's

I have been running my ELK SIEM for a few months now, almost a year actually and my syslogs stopped being shown. I have them coming in again now, but I need to clean up my indices so that it does not stop again. Is there a good description and documentation that I can review to become more aquainted with the difference between deleteting, flushing, and merging indices? I don't want to loose data but I also cannot have the syslogs stop coming in as well.

Thank you for your help and guidance. It is always much appreciated.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 16, 2022, 5:33am UTC](https://discuss.elastic.co/t/proper-maintenance-of-the-elastic-stack/312030/2 "2022-08-16T05:33:52Z")

</div>

What is the full output of the [cluster stats API](https://www.elastic.co/guide/en/elasticsearch/reference/8.3/cluster-stats.html)?

---

<div class="post-metadata">

**Author:** ![MKirby](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MKirby](https://discuss.elastic.co/u/MKirby)\
**Post date:** [August 16, 2022, 2:00pm UTC](https://discuss.elastic.co/t/proper-maintenance-of-the-elastic-stack/312030/3 "2022-08-16T14:00:13Z")

</div>

Thank you for the response Christian. I will get that information for you on Friday. At this time I do not have remote access to the Elastic Stack SIEM.

I do have one other question that relates to this topic.

Is there a or can the Logstash server send the logstash logs to a folder that is not located on the Logstash server? Ie adding in the Logstash.yml file for the location of the Logfiles \192.168.50.15\C$\Logstash\_logs\ Where the ip indicated is not the IP of the Logstash server? We have a log server that has terrabytes of space that we want to send the logs to, which will ensure that it never stops logging.

Thank you again for all you assistance.

---

<div class="post-metadata">

**Author:** ![MKirby](https://avatars.discourse-cdn.com/v4/letter/m/e56c9b/32.png) [@MKirby](https://discuss.elastic.co/u/MKirby)\
**Post date:** [August 19, 2022, 4:53pm UTC](https://discuss.elastic.co/t/proper-maintenance-of-the-elastic-stack/312030/4 "2022-08-19T16:53:45Z")

</div>

The API output is very large and I am unable to pull it out of the environment. Is there a specific area to look in the output?

If I am looking to perform a regular removal or clearing of the indexes so that my syslogs do not stop populating every week what is the best way to do that.

As an example I have indexes from 2021 that I want to keep but they are taking up an index and if I remove one or two I then get more syslog data. I want to automate and ensure that syslogs continue to be collected without losing current data that is 6 months old. Data older than 6months is good to be put into cold storage.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 16, 2022, 4:53pm UTC](https://discuss.elastic.co/t/proper-maintenance-of-the-elastic-stack/312030/5 "2022-09-16T16:53:49Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
