TwiN

I have to say that 777ms is just a random number I picked that seemed to make sense, but the logic behind it is that even if you have the...

So there's a reason why I haven't implemented this sooner. My biggest concern is, if we have a retry interval (or failed interval, as you named it), its interaction with...

As there has been no reply for several months, I'm going to close this.

Sounds like a good idea! Something like this: ```yaml alerts: - type: slack enabled: true description: "healthcheck failed 3 times in a row" send-on-resolved: true repeating: true ``` That said,...

I have a hard time believing the endpoint to use for health & metrics aren't configurable 🤔 There's a lot of apps that don't use `/healthz`

Oh yeah I understood that point, I just don't understand what the point is. Almost every single application that relies on hitting an endpoint (e.g. prometheus, kubernetes, etc.) should allow...

Thing is, while adding a configuration in `endpoints[].ui` to show the full url is a good idea, it wouldn't provide a consistent experience. For instance, what if the endpoint requires...

Hello @kratenko! The bad news is that unless enough people react to your feature request with a 👍 or somebody else creates a PR for it, I don't think I'll...

> It seems like there is no ability to configure default conditions to be able to decrease the amount of config lines, am I right? Not quite, but you can...

Just so I understand correctly, you're asking if an endpoint returns an error in one of the parameters from the body, you'd like bubble up that error to the UI?...