You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
π I have found these related issues/pull requests
I see nothing related to this, but in notifications, like discord webhooks or emails, we should maybe add how long that service was down?
π·οΈ Feature Request Type
Change to existing notification-provider
π Feature description
Say your provider is down for 1000 seconds, you would convert it to minutes or even hours or maybe even days and so on right? But 1000 seconds is 16 minutes, so in the notification you would say something like "Down For: 16 Minutes" or "Down For: 1 week 2 days", and so for, just making everyone know how long it was down.
βοΈ Solution
I would use it for Email system and Discord webhooks, and I know other services have this, and I think it would be nice to have this in Uptime Kuma, Uptime Kuma is one of the best ones out there.
β Alternatives
No response
π Additional Context
No response
The text was updated successfully, but these errors were encountered:
π I have found these related issues/pull requests
I see nothing related to this, but in notifications, like discord webhooks or emails, we should maybe add how long that service was down?
π·οΈ Feature Request Type
Change to existing notification-provider
π Feature description
Say your provider is down for 1000 seconds, you would convert it to minutes or even hours or maybe even days and so on right? But 1000 seconds is 16 minutes, so in the notification you would say something like "Down For: 16 Minutes" or "Down For: 1 week 2 days", and so for, just making everyone know how long it was down.
βοΈ Solution
I would use it for Email system and Discord webhooks, and I know other services have this, and I think it would be nice to have this in Uptime Kuma, Uptime Kuma is one of the best ones out there.
β Alternatives
No response
π Additional Context
No response
The text was updated successfully, but these errors were encountered: