# Monitoring core files?

**URL:** <https://discuss.elastic.co/t/monitoring-core-files/73986>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 5, 2017, 6:25pm UTC](https://discuss.elastic.co/t/monitoring-core-files/73986 "2017-02-05T18:25:35Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![test\_user](https://avatars.discourse-cdn.com/v4/letter/t/eada6e/32.png) [@test\_user](https://discuss.elastic.co/u/test_user)\
**Post date:** [February 5, 2017, 6:25pm UTC](https://discuss.elastic.co/t/monitoring-core-files/73986/1 "2017-02-05T18:25:35Z")

</div>

Hi folks, in order to check our test application against core dump files currently I have cronjob which is checking specific entries on related folder. Can I perform same task with filebeat, so I can remove my cronjob?

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [February 6, 2017, 3:31pm UTC](https://discuss.elastic.co/t/monitoring-core-files/73986/2 "2017-02-06T15:31:40Z")

</div>

are these core dumps binary or do they contain stack-traces only? Filebeat currently processes text files line by line.

---

<div class="post-metadata">

**Author:** ![test\_user](https://avatars.discourse-cdn.com/v4/letter/t/eada6e/32.png) [@test\_user](https://discuss.elastic.co/u/test_user)\
**Post date:** [February 6, 2017, 5:35pm UTC](https://discuss.elastic.co/t/monitoring-core-files/73986/3 "2017-02-06T17:35:52Z")

</div>

they are only binary files.. Might be I should use topbeat to supervise the process which can crash.

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [February 7, 2017, 1:10am UTC](https://discuss.elastic.co/t/monitoring-core-files/73986/4 "2017-02-07T01:10:41Z")

</div>

topbeat? it's metricbeat you mean.

If it's of any help, you can extract the stack-trace from the core-dump into a file and index the stack-trace (either line by line or use multiline to index the complete file as one document). But as developers normally want to investigate core-dumps with a debugger, I think it's of limited use... maybe helpful to figure out if a core-dump trace is somewhat similar though (like show top-N or least-N stack trace positions).

---

<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:** [March 7, 2017, 1:10am UTC](https://discuss.elastic.co/t/monitoring-core-files/73986/5 "2017-03-07T01:10:43Z")

</div>

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