# Low footprint way of importing Windows Service Data

**URL:** <https://discuss.elastic.co/t/low-footprint-way-of-importing-windows-service-data/350282>\
**Category:** Elasticsearch\
**Created:** [January 3, 2024, 7:56am UTC](https://discuss.elastic.co/t/low-footprint-way-of-importing-windows-service-data/350282 "2024-01-03T07:56:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![randomnamegenerator](https://avatars.discourse-cdn.com/v4/letter/r/7ab992/32.png) [@randomnamegenerator](https://discuss.elastic.co/u/randomnamegenerator)\
**Post date:** [January 3, 2024, 7:56am UTC](https://discuss.elastic.co/t/low-footprint-way-of-importing-windows-service-data/350282/1 "2024-01-03T07:56:40Z")

</div>

Hello All,

We are looking to import windows server service status (on or off etc) data into our ELK stack from client servers which currently have filebeat installed.

Is there a way of doing this without installing metricbeat or similar on each client server, I am hoping we can just use a filebeat module to achieve this as we don´t need detailed information.

Thanks in advance

---

<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:** [January 31, 2024, 7:56am UTC](https://discuss.elastic.co/t/low-footprint-way-of-importing-windows-service-data/350282/2 "2024-01-31T07:56:48Z")

</div>

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