# Public Synthetic Monitor's Timezones (AEST / Australia)

**URL:** <https://community.dynatrace.com/t/public-synthetic-monitors-timezones-aest-australia/32102>\
**Category:** Synthetic Monitoring\
**Tags:** synthetic-monitoring\
**Created:** [July 14, 2021, 9:27am UTC](https://community.dynatrace.com/t/public-synthetic-monitors-timezones-aest-australia/32102 "2021-07-14T09:27:22Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThomasEaton](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/thomaseaton/32/38694_2.png) [@ThomasEaton](https://community.dynatrace.com/u/ThomasEaton)\
**Post date:** [July 14, 2021, 9:27am UTC](https://community.dynatrace.com/t/public-synthetic-monitors-timezones-aest-australia/32102/1 "2021-07-14T09:27:22Z")

</div>

All,

I have created a 90 step synthetic, which is to create a quote.&nbsp;[https://www.qbe.com/au/home-insurance](https://www.qbe.com/au/home-insurance)&nbsp;- it is open for the world to access and generate a quote for a policy in Home or Insurance, these were the products i was looking at.

The issue is, I am in UK (UTC+1 / GMT+1 / BST), so AEST (Australia) passes into a new day currently 9 hours ahead of me. So when i record the synthetic, i set my OS timezone to Sydney (if i do not, when we hit 3pm (GMT+1), the website 2nd page, after you hit get a quote, it auto generates the date and you can not change it, is it set to today.

I spoke to DynatraceONE, who gave me a script for changing the date to be updated 1 day ahead. But I need a script which updates it by 10 Hours. I was wondering if anyone has done this before and what people do for synthetics they want running in a specific timezone from the public locations?

Can anyone help me update the below to have 10 hours instead of 1 day (24 hours)?

Increment by a day script:

var today = new Date();  
today.setDate(today.getDate()+1);  
dateformat= today.getFullYear() + “-” + (“0” + (today.getMonth() + 1)).slice(-2) + “-” + (“0” + today.getDate()).slice(-2) ;

function addDays(date, numDays) {  
return new Date(date.getFullYear(), date.getMonth(), date.getDate() + numDays);

}  
function date\_format(date)  
{  
var month = date.getMonth() + 1;  
var twoDigitMonth = (month \< 10) ? (‘0’ + month) : month;  
var twoDigitDate = (date.getDate() \< 10) ? (‘0’ + date.getDate()) : date.getDate();  
// return (twoDigitDate + ‘-’ + twoDigitMonth + ‘-’ + date.getFullYear());  
return (date.getFullYear() + ‘-’ + twoDigitMonth + ‘-’ + twoDigitDate);  
}  
var todayDate = new Date();  
var dateTomorrow = addDays(todayDate, 1);

var dateformat = date\_format(dateTomorrow);  
api.info("dateformat: " + dateformat);  
api.setValue(“dateformat”, dateformat);

---

<div class="post-metadata">

**Author:** ![ThomasEaton](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/thomaseaton/32/38694_2.png) [@ThomasEaton](https://community.dynatrace.com/u/ThomasEaton)\
**Post date:** [July 14, 2021, 10:32am UTC](https://community.dynatrace.com/t/public-synthetic-monitors-timezones-aest-australia/32102/2 "2021-07-14T10:32:28Z")

</div>

I now realise it is java script and being a an extra 14 hours ahead will work as it is in the future and not the past, where the past was the issue. I will implement Dynatrace’s code (+1 day) and see how that goes.

But i learned today that all Public Synthetic locations run in UTC and we have to edit the scripts with a java event, to add code to update the date or time.

---

<div class="post-metadata">

**Author:** ![Karolina\_Linda](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/karolina_linda/32/36089_2.png) [@Karolina\_Linda](https://community.dynatrace.com/u/Karolina_Linda)\
**Post date:** [July 14, 2021, 11:29am UTC](https://community.dynatrace.com/t/public-synthetic-monitors-timezones-aest-australia/32102/3 "2021-07-14T11:29:00Z")

</div>

hi&nbsp;[@ThomasEaton](https://community.dynatrace.com/user/35030), one of our developers will also take a look at the case you provided. Stay tuned 🙂

---

<div class="post-metadata">

**Author:** ![ThomasEaton](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/thomaseaton/32/38694_2.png) [@ThomasEaton](https://community.dynatrace.com/u/ThomasEaton)\
**Post date:** [July 15, 2021, 6:26am UTC](https://community.dynatrace.com/t/public-synthetic-monitors-timezones-aest-australia/32102/4 "2021-07-15T06:26:14Z")

</div>

I added as a step 2, as you can not put it as step 1, that has to be a navigation type event. It didn’t work 😞

---

<div class="post-metadata">

**Author:** ![ThomasEaton](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/thomaseaton/32/38694_2.png) [@ThomasEaton](https://community.dynatrace.com/u/ThomasEaton)\
**Post date:** [August 5, 2021, 10:21am UTC](https://community.dynatrace.com/t/public-synthetic-monitors-timezones-aest-australia/32102/5 "2021-08-05T10:21:57Z")

</div>

In the end, we had a solution given by a product specialist:

 ![ThomasEaton_0-1628158876904.png](https://global.discourse-cdn.com/dynatrace/original/2X/9/9986a2cef13d336cd18b3ac3e8f8bd64028bd84d.png)

He added a DOM Element:&nbsp;document.querySelectorAll(‘button[class\*=“current”]’)[0].parentElement.nextElementSibling

---

<div class="post-metadata">

**Author:** ![ThomasEaton](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/thomaseaton/32/38694_2.png) [@ThomasEaton](https://community.dynatrace.com/u/ThomasEaton)\
**Post date:** [August 5, 2021, 10:32am UTC](https://community.dynatrace.com/t/public-synthetic-monitors-timezones-aest-australia/32102/6 "2021-08-05T10:32:17Z")

</div>

Also, Dynatrace confirmed, all public Synthetic locations are in UCT - would be good to add this to the documentation please.

---

<div class="post-metadata">

**Author:** ![ThomasEaton](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/thomaseaton/32/38694_2.png) [@ThomasEaton](https://community.dynatrace.com/u/ThomasEaton)\
**Post date:** [August 5, 2021, 10:33am UTC](https://community.dynatrace.com/t/public-synthetic-monitors-timezones-aest-australia/32102/7 "2021-08-05T10:33:40Z")

</div>

HI no one ever contacted me 😞 - but we have resolved the issue.

Can you please log a documentation update to show that Public locations run in UTC - I am sure it will help others. - as i bet most people assume the public location synthetic locations run in the locations time zone.. I.E AEST for Sydney? 😞