# Custom agent for unsupported OS systems

**URL:** <https://discourse.sensu.io/t/custom-agent-for-unsupported-os-systems/1183>\
**Category:** Sensu Go\
**Created:** [May 16, 2019, 9:33pm UTC](https://discourse.sensu.io/t/custom-agent-for-unsupported-os-systems/1183 "2019-05-16T21:33:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jspaleta](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.sensu.io/jspaleta/32/141_2.png) [@jspaleta](https://discourse.sensu.io/u/jspaleta)\
**Post date:** [May 16, 2019, 9:35pm UTC](https://discourse.sensu.io/t/custom-agent-for-unsupported-os-systems/1183/2 "2019-05-16T21:35:59Z")

</div>

Hey,  
Ironically i just posted a topic about this just a few minutes before you posted…

> [@Jef Practice: Monitoring Legacy Unix systems with Sensu Go](https://discourse.sensu.io/t/jef-practise-monitoring-legacy-unix-systems-with-sensu-go/1181/1):
>
> Having Sensu Go written in Golang comes with some great forward looking benefits, especially for containerized workloads. But… Golang doesn’t compile natively on legacy Unix environments so we can’t easily offer a native agent to run on critical systems that are still in operation. If they weren’t critical, we’d all have found a way to move them to linux most likely. Even though there’s no native agent for these legacy systems Sensu Go can still support some monitoring workloads by making use of…

---

_[View the full topic](https://discourse.sensu.io/t/custom-agent-for-unsupported-os-systems/1183)._