Support timezone in notifications

[ksurl]

apk add tzdata to docker image and support TZ environment variable to set the timezone. alpine is pretty straightforward. you just add this to the start up before running the app

cp -f "/usr/share/zoneinfo/${TZ}" /etc/localtime && echo "${TZ}" > /etc/timezone.

I would suggest a script to run the cp and the npm startup and set the script as the entrypoint

[louislam]

Timezone is already handled in the frontend and you can change in the "Settings" page.
All dates stored in SQLite are in UTC.

[ksurl]

The discord notification uses utc time

[rezzorix]

Interesting.

Just realized that for Discord notifications the time of incident is sent.
In Telegram notifications just give information on that status - without any time...

@louislam
maybe would be good to either streamline notification texts on backend for each service
OR (maybe even better)
let users customise the notification text (including setting a timezone for this notifications)

I really would contribute more than only writing enhancements and testing builds but my coding skill are far too limited ... 😔

[Simon-Peham]

The same is in the Slack notifications it is also in UTC

[tgxn]

Same for all the notifications I think; they are all UTC. I'd like for them to follow the instance timezone, if configured (if it's "Auto" or not configured we can consider it to be UTC, as we can't infer the client data from the server)

Instance Timezone:

[kamilmirza]

same problem with Pushover notifications
configured desired UTC but no go in Settings

[chris-ard]

Yeah, having the same issue over Slack. Loving Uptime Kuma so far - awesome polish. However, for us to use in production the timezone really needs to be considered in the message (or have it customizable).

For example, we have clients in US, parts of EU, and Australia. The timestamp from Slack takes a lot of figuring out because it will only show us time here. It's also bit confusing as well that it doesn't match relative to the time within slack.

[MostHated]

It would definitely be nice to have all times used within the system to use the proper timezone. While the interface has the right time by setting the timezone, that doesn't really do anything for me, as I don't often look at the interface. I am attempting to pull the data from "api/status-page/heartbeat" to use in various automations.

[windware-ono]

Hello. I'd like the fix implemented. This should be a quick fix.

[FrancisHG]

++ Same, I am using Slack and it is using UTC for text notification, not the configured timezone in UptimeKuma.

[pbunluesin]

I got this issue with Line Notification. it's effect with production which need accurate time.

[drtech981]

Bump, still having this issue. It is messing up with quick fixes since some of my clients are around -13 hrs behind our timezone.
Already have set TZ in uptime-kuma as well as on the ubuntu machine.

[BeyondVertical]

Same problem here with mails. Would be great if this is fixed.
I have docker running and have /etc/timezone in the container via volumes. It is set there correct, but not right in the logs and the pushes.

[stavros-k]

I don't think +1 ing this does not provide any help. Since it's still open, it's an issue. Use the "reactions" on the top post to show you "want" this implemented. Keeps the chat clean and will be easier for contributors to discuss how that would be implemented.

Also reduces the notification "spam" with useless comments to everyone subscribed on this issue.

[mbacicc]

I'm also having timezone problems with email notification.

It would be easily solved by installing tzdata in the base image (both debian and alpine have this package) and passing the TZ env var in the docker container.

[yyahari]

Como solucion a este error en particular con respecto a smtp
hicimos uunas modificaciones,
1.apt update && apt install tzdata -y
2.dpkg-reconfigure tzdata
3.Seleccione mi time zone correspondiente
4.corri "date" dandome la fecha y hora de mi zona horaria
5.edite el archivo /app/server/notification-providers/smtp.js
6.comente el campo:
//if (heartbeatJSON) {
// bodyTextContent = ${msg}\nTime (UTC): ${heartbeatJSON["time"]};
// }

7. agregue;
   let fecha = new Date();
   let fechayhora=fecha.toLocaleString();

   if (heartbeatJSON) {
       bodyTextContent = `${msg}\nTime: ${fechayhora}`;
   }
   

8. con eso me muestra la hora correcta con respecto a mi pais en los correos
   9.Saludos

[Dr0id1]

Do we have an update on that ?

[BeyondVertical]

Do we have an update on that ?

Don't think so. Would be nice to have this feature soon. :)

[louislam]

I recently added server side timezone along with the maintenance pull request. It is configurable in the Settings page.

It is an example of convertion of utc to server timezone.

dayjs.utc(myDate).local().foarmt(<DATE FORMAT>)

[BeyondVertical]

Awesome. When can we get it in the releases? 😂

[roughnecks]

Sorry if I'm posting here, but I think this issue is still current with webhooks notifications.

[CommanderStorm]

What is your notification template?

[roughnecks]

"template": "${heartbeat.time}\r\n${msg}"

[CommanderStorm]

time is in UTC.
If you want the local time, please use localDateTime instead.
If you want the Timezone in addition, you can use timezone

We know that the documetation surroudning the templating system is quite confusing but have not yet have the time to improve this part

[roughnecks]

I see, will make the change. Thanks