Telegram notifier - {{.Service.Downtime.Human}} does not work correctly

[jacklul]

I just noticed that after services come back from being offline the {{.Service.Downtime.Human}} returns values in microseconds which makes me believe the notifier has a bug.

No idea if this is only for Telegram notifier, tried using Command one but it doesn't work - it truncates first character from defined command and refuses to work if the first character is space (tried this in attempt to prevent first character from being stripped).

11:49
Your service 'xxxx' is currently offline! (reason: HTTP Error Get "xxxx": dial tcp 1.2.3.4:443: i/o timeout (Client.Timeout exceeded while awaiting headers))

12:34
Your service 'xxxx' is currently online! (was down for 44 milliseconds 246 microseconds)

{{.Service.Uptime.Human}} might have the same bug but I haven't tested that yet.