Hi @Avyayah
I cannot extend the duration to more than 1000 secs.
See this article:
Since the sampling interval has a significant impact on the size of the log file and the server load, you should set the sample interval based on the average elapsed time for the issue to occur so you can establish a baseline before the issue occurs again. This will allow you to spot any trend leading to the issue.
Fifteen minutes will provide a good window for establishing a baseline during normal operations. Set the sample interval to 15 seconds if the average elapsed time for the issue to occur is about four hours. If the time for the issue to occur is eight hours or more, set the sampling interval to no less than five minutes; otherwise, you will end up with a very large log file, making it more difficult to analyze the data.
If you are looking for an alternative of performance monitor, then check the Extended Events (XEvents) architecture which enables users to collect as much or as little data as is necessary to monitor, identify, or troubleshoot performance in SQL Server.
See this doc: Quickstart: Extended Events.
Best regards,
Cosmog Hong
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".