Hi Prajwal V,
the timestamp returned by the error, does it look like the local time of the SiteScope server?
..
RequestExpired
Request timestamp is too skewed. Timestamps must be within 900 seconds of server time.
Timestamp date: 2017-01-04T18:05:21.426Z
..
Most likely your system runs ahead of the
I didn't find any option to force SiteScope to send a specific timestamp, but this hint:
http://cmshelpcenter.saas.hp.com/CMS/10.30/cp-docs/docs/eng/doc_lib/Content/AWS_ts.htm
..
Problem: The following error messages occur during the discovery:
Request timestamp is too skewed. Timestamps must be within 900 seconds of server time. Timestamp date: 2015-06-30T04:17:39.196Z
Solution: Change the probe time and time zone to the standard local time.
..
You might wanna enable debug logging for the individual monitor and check the logfile, as SiteScope logs quite some details with debug logging enabled, like
"metricName=" + metricName +
", namespace=" + namespace +
", startTime=" + request.getStartTime() +
so with this you can see what SiteScope sends as startTime.
From what I understand, we simply take the local time and use it as starttime for the request, but there is no way to adjust this by an offset or alike.
Greetings
Siggi