Timestamp formatting in SolarWinds Observability notification services

New user here. I am trying to configure a notification service within SolarWinds Observability (specifically a webhook service). Is there any way to change the timestamp formats? Instead of as a string, I want to send them in int64 format.

Find more posts tagged with

help

Observability

SaaS

Alerts

Accepted answers

All comments

tony.johnson

I do not believe it is possible to transform the values sent. Can you share a screenshot of what you are configuring?

przemyslaw.gedek

@sr66 thanks for bringing this up! The SWO notification service does support the unixTimestamp variable, which I believe could meet your needs - though currently, this is available only for Website Monitoring alerts.

To better assist you, could you share what type of alerts you're looking to configure notifications for? Understanding your use case will help us guide you more effectively and better plan our roadmap.

Spaw

Hello All,

Im also suffering same issue.

While creating notification services for any alert like device down the time comes in UTC instead of IST.

Could you please share us workaround to convert the timezone.

Spaw

Hello Tony,

Kindly find the email received with different timezone.

przemyslaw.gedek

Hi @Spaw, thanks for your message!

It looks like your use case differs slightly from @sr66’s. While @sr66 is looking to convert a specific UTC timestamp (e.g., Sep 11, 2025 13:59:37 UTC) into a Unix timestamp format (e.g., 1757599177000), your goal is to convert it into a different time zone, such as IST, which would be Sep 11, 2025 at 19:29:37 IST.

To clarify:

Timestamp conversion is partially supported, specifically for Website Monitoring alerts. We are planning the expand availability of this functionality for other types of alerts.
Time zone selection for Notifications, however, is not currently supported. This feature is on our roadmap but no delivery date has been defined yet.

We appreciate your feedback - it helps us better understand how these features are being used.