For Ping (Or HTTPs) Add a minimum response time - After that, warn, then service alert #2456

New issue

Closed

opened 2026-02-28 02:55:26 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 02:55:26 -05:00

Owner

Originally created by @francismiles1 on GitHub (Aug 9, 2023).

⚠️ Please verify that this feature request has NOT been suggested before.

I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

there are people suggesting Ping TTL etc, but what I am suggesting is setting a minimum and maximum bar on response times.
For some failing services, their response times go through the roof, but still work. Its useful to know this before the inevitable crash.

✔️ Solution

Add a minimum and maximum response time capability.
If response times (averaged over the number of times this happens - set by the user) fall within these bounds, alert with a WARNING
If response times fall outside of the Maximum, or service Fails, Alert with FAIL

❓ Alternatives

No response

📝 Additional Context

No response

Originally created by @francismiles1 on GitHub (Aug 9, 2023). ### ⚠️ Please verify that this feature request has NOT been suggested before. - [X] I checked and didn't find similar feature request ### 🏷️ Feature Request Type New Monitor ### 🔖 Feature description there are people suggesting Ping TTL etc, but what I am suggesting is setting a minimum and maximum bar on response times. For some failing services, their response times go through the roof, but still work. Its useful to know this before the inevitable crash. ### ✔️ Solution Add a minimum and maximum response time capability. If response times (averaged over the number of times this happens - set by the user) fall within these bounds, alert with a WARNING If response times fall outside of the Maximum, or service Fails, Alert with FAIL ### ❓ Alternatives _No response_ ### 📝 Additional Context _No response_

deekerman

2026-02-28 02:55:26 -05:00

closed this issue
added the
feature-request
label

deekerman commented

2026-02-28 02:55:32 -05:00

Author

Owner

@Computroniks commented on GitHub (Aug 9, 2023):

Is this a duplicate of #459 and #1813? If it is, could you please close this issue to try and avoid cluttering the issue list too much.

@Computroniks commented on GitHub (Aug 9, 2023): Is this a duplicate of #459 and #1813? If it is, could you please close this issue to try and avoid cluttering the issue list too much.

deekerman commented

2026-02-28 02:55:32 -05:00

Author

Owner

@francismiles1 commented on GitHub (Aug 10, 2023):

Oops, sorry, didn't see those. Yes, will close.

@francismiles1 commented on GitHub (Aug 10, 2023): Oops, sorry, didn't see those. Yes, will close.