22 Jul 2024
08:46 PM
- last edited on
23 Jul 2024
07:45 AM
by
MaciejNeumann
Trying to figure out what the expirationTimestamp field is for in Third-party synthetic API - POST third-party monitors to Dynatrace
Their documentation is not helpful at all, since it basically just restates the name of the field in a longer way:
"The timestamp of the monitor expiration, in UTC milliseconds." - Thanks Dynatrace, super helpful, lol...
Just wondering why and when I would want to put an expiration date on a synthetic test I'm sending to Dynatrace. We already send the interval value in the tests object (scheduleIntervalInSeconds), which effectively tells Dynatrace when the next test result should be in, so I don't think it is related to that.
Anyone know what the point of that field is and why I would/wouldn't want to use it?
Thanks.
02 Jan 2025 02:55 PM
Hi, @36Krazyfists! Have you managed to find the answer to your question? It would be great if you share it with the Community 🙂