# Icinga-Powershell-Plugins: Plans for "network-checks" like http, tcp, dhcp etc

**URL:** <https://community.icinga.com/t/icinga-powershell-plugins-plans-for-network-checks-like-http-tcp-dhcp-etc/6582>\
**Category:** Icinga 2\
**Tags:** windows, powershell, windows-agent, icinga2\
**Created:** [January 29, 2021, 11:05am UTC](https://community.icinga.com/t/icinga-powershell-plugins-plans-for-network-checks-like-http-tcp-dhcp-etc/6582 "2021-01-29T11:05:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![stevie-sy](https://community.icinga.com/letter_avatar_proxy/v4/letter/s/898d66/32.png) [@stevie-sy](https://community.icinga.com/u/stevie-sy)\
**Post date:** [January 29, 2021, 11:05am UTC](https://community.icinga.com/t/icinga-powershell-plugins-plans-for-network-checks-like-http-tcp-dhcp-etc/6582/1 "2021-01-29T11:05:45Z")

</div>

Hi,

Before I create a feature-request on GitHub I wanted to ask if there are any plans to include some - let’s say “network checks” - into the Icinga-PowerShell-Framework and Icinga-PowerShell-Plugins like check\_http, check\_tcp, check\_dhcp etc. from the Monitoring Plugins in the future?

The background to this question is as follows:  
We rolled out the Icinga Agent on the Windows Server and we also started to rollout the new Powershell-Framework incl. Plugins to these servers instead of or in addition of the “old” checks (we don’t want to use NSClient any more). Since then we receive more and more requests from colleagues that we should also perform some checks using the windows agent to check e.g. is a local WebSite running, is a local port open etc. So everything we are doing now using our Master, Satellite Servers and Linux servers where the agent is installed and running there the checks from monitoring plugins.

---

<div class="post-metadata">

**Author:** ![cstein](https://community.icinga.com/user_avatar/community.icinga.com/cstein/32/7745_2.png) [@cstein](https://community.icinga.com/u/cstein)\
**Post date:** [January 29, 2021, 12:04pm UTC](https://community.icinga.com/t/icinga-powershell-plugins-plans-for-network-checks-like-http-tcp-dhcp-etc/6582/2 "2021-01-29T12:04:27Z")

</div>

Hello and thank you for the feedback.

TCP is already listed as feature request: [Feature Request Check Command TCP · Issue #100 · Icinga/icinga-powershell-plugins (github.com)](https://github.com/Icinga/icinga-powershell-plugins/issues/100)

For HTTP and DHCP there is currently nothing planed. It would be interesting to see what should be able to be checked. I honestly have less interest in re-writing the check\_http plugin for Linux with the 200 arguments provided.

If we can get a list of features for both plugins, we would add it for the roadmap for 1.4.0 or 1.5.0.

---

<div class="post-metadata">

**Author:** ![stevie-sy](https://community.icinga.com/letter_avatar_proxy/v4/letter/s/898d66/32.png) [@stevie-sy](https://community.icinga.com/u/stevie-sy)\
**Post date:** [January 29, 2021, 12:11pm UTC](https://community.icinga.com/t/icinga-powershell-plugins-plans-for-network-checks-like-http-tcp-dhcp-etc/6582/3 "2021-01-29T12:11:14Z")

</div>

thank you @cstein for the fast answer. I ask my colleagues what exactly they imagine and with this information I create a feature request. And of course I understand why you don’t want to rewrite the full function of every plugin from the monitoring plugins. 😉