Support for setting "IP Family" accross all monitor types #4381

New issue

Open

opened 2026-02-28 04:00:36 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-28 04:00:36 -05:00

Owner

Originally created by @gbrackley on GitHub (Oct 27, 2025).

This is simply a ticket to port the functionality in one monitor to the other types.

Not asking to act on all hosts that resolve for a given DNS name.
Not asking to check all protocols for a given name

see:

🏷️ Feature Request Type

Change to existing monitor

🔖 Feature description

With the new release and support for "IP Family" on the http monitor type is possible to monitor dual stack hosts/services and know when it is degraded. This is really good thank you.

Could the "IP Family" functionality be added to other monitor types. examples:

the SMTP with starttls and certificate validation can't be locked to IPv6 or IPv4

✔️ Solution

Implement the same functionality in the http monitor type in:

ICMP
SMTP
TCP
SNMP
...

Anywhere where DNS resolution is performed to resolve host names.

Originally created by @gbrackley on GitHub (Oct 27, 2025). ### 📑 I have found these related issues/pull requests This is simply a ticket to port the functionality in one monitor to the other types. Not asking to act on all hosts that resolve for a given DNS name. Not asking to check all protocols for a given name see: - #5880 - #1025 - #1242 - #6121 ### 🏷️ Feature Request Type Change to existing monitor ### 🔖 Feature description With the new release and support for "IP Family" on the http monitor type is possible to monitor dual stack hosts/services and know when it is degraded. This is really good thank you. Could the "IP Family" functionality be added to other monitor types. examples: - the SMTP with starttls and certificate validation can't be locked to IPv6 or IPv4 ### ✔️ Solution Implement the same functionality in the http monitor type in: - ICMP - SMTP - TCP - SNMP - ... Anywhere where DNS resolution is performed to resolve host names.

deekerman added the

feature-request

A:monitor

type:enhance-existing

labels

2026-02-28 04:00:36 -05:00

deekerman commented

2026-02-28 04:00:39 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Oct 27, 2025):

Feel free to do a PR for the monitors that matter to you 😉
We are all volunteers here.

Agreee that this would be nice to have.

@CommanderStorm commented on GitHub (Oct 27, 2025): Feel free to do a PR for the monitors that matter to you 😉 We are all volunteers here. Agreee that this would be nice to have.

deekerman commented

2026-02-28 04:00:40 -05:00

Author

Owner

@Alloc86 commented on GitHub (Dec 18, 2025):

Would also love this (TCP port specifically, but the idea to have it everywhere is obviously better ;) ).

@Alloc86 commented on GitHub (Dec 18, 2025): Would also love this (TCP port specifically, but the idea to have it everywhere is obviously better ;) ).

deekerman commented

2026-02-28 04:00:40 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Dec 18, 2025):

I can review your PR if you want to look into enabling this for said monitor.

@CommanderStorm commented on GitHub (Dec 18, 2025): I can review your PR if you want to look into enabling this for said monitor.