# Monitor multiple systemd services

**URL:** <https://hub.mender.io/t/monitor-multiple-systemd-services/7499>\
**Category:** Mender Monitor\
**Created:** [January 31, 2025, 3:31am UTC](https://hub.mender.io/t/monitor-multiple-systemd-services/7499 "2025-01-31T03:31:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chadrockey](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/chadrockey/32/1885_2.png) [@chadrockey](https://hub.mender.io/u/chadrockey)\
**Post date:** [January 31, 2025, 3:31am UTC](https://hub.mender.io/t/monitor-multiple-systemd-services/7499/1 "2025-01-31T03:31:36Z")

</div>

Is it the intended usage to have a separate .sh file for every service you wish to monitor?

So you’ll have between 1 and ~20? .sh in /etc/mender-monitor/monitor.d/available?

Just making sure you’re not supposed to provide a list of systemd services somewhere instead.

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [February 4, 2025, 10:42am UTC](https://hub.mender.io/t/monitor-multiple-systemd-services/7499/2 "2025-02-04T10:42:59Z")

</div>

Hi @chadrockey,

Yes, as far as I can see the standard strategy is to create an `.sh` file per unit to monitor, or alternatively, create a custom monitoring script which combines the logic into one.

Greetz,  
Josef