Distributed Deployment Configuration

Assume you have Gatus deployed in several security subnets (or zones) to monitor individual services because one single Gatus instance is not able to reach those services (administratively prohibited due to firewall rules, etc.)

gRPC support

Would love to see support for gRPC service monitoring. We're using gatus for our external APIs but our internal service mesh consists of mostly gRPC services where we already implement the [gRPC health checking protocol](https://github.com/grpc/grpc/blob/master/doc/health-checking.md) and integrate with k8s and Docker,

Idle HTTP connections are never closed, so checks stop re-resolving DNS and report stale latency

## Summary

Listen on Unix Socket

### Describe the feature request

[Bug] SSH and STARTTLS endpoints reject valid IPv6 addresses

### Describe the bug

Endpoint group dropdown chevron points in unusual direction

### Describe the bug

Include clickable endpoint links in built-in alert notifications

### Describe the feature request

ICMP on IPv6 with Addresses doesn't really work

Hi,

Add optional OIDC-group-based visibility for endpoint groups

### Describe the feature request

Add PushWard as an alerting provider

### Describe the feature request

Suite timeout does not stop the remaining endpoints

## Describe the bug

fix(suite): match alert results to endpoints by name

## Summary

feat(ui): Subtle visual polish of the dashboard

## Summary

Support theme selection through URL query parameter

<!-- Thank you for contributing! -->

Add configurable click URLs to ntfy alerts

<!-- Thank you for contributing! -->

Support DNS query type SOA

### Describe the feature request

Re-evaluate a failed endpoint before recording the failure (opt-in retries)

This is a follow-up to #59 ("Retry request in case of failure"), which was closed in 2021 with the suggestion that `failure-threshold` covers it, and with an invitation to open a new request if there is interest. #1456 and #1714 are two more reports of the same need: bursts of `context deadline exceeded` or `no route

Release prebuild binaries along docker images

### Describe the feature request

[Feature Request] Nested groups via opt-in group path separator (e.g. "cluster/domain")

### Describe the feature request

[CONTEXT] not usable in urls

### Describe the bug

Feature Request: choose which IP protocol is used

Hi,

fix(jsonpath): support object keys containing dots via quoted accessors

Fixes #1238

fix(ssh): support keyboard-interactive authentication for endpoints and tunnels

## Summary

Feature request: Add a configuration option to allow defining CORS origins

With reference to discussion <https://github.com/TwiN/gatus/discussions/1118>.

Persist reminder timestamp across restarts

### Describe the bug

Clarify docs on maintenance windows

https://github.com/TwiN/gatus#maintenance is not precise how gatus ig going to handle endpoint-specific `maintenance-windows` WRT the global `maintenance` entry: will the endpoint-specific be added to the global one or replace the global one?

fix(websocket): apply the client timeout to reads and writes

QueryWebSocket hands client.timeout to DialContext, but gorilla/websocket clears the connection deadline once the handshake completes, so ReadMessage runs with no deadline at all. A server that accepts the connection and never replies blocks the check forever while it holds a monitoringSemaphore slot, and with the defa

fix(alerting): Redact telegram token from errors on send failure

Fixes #1837

skip-invalid-config-update: an invalid config reload stops all checks and the web server while the process keeps running

### Describe the bug

Web Push (browser notification) alerting provider

### Describe the feature request