Create some system to warn both the DiagManager user and PSSDiag runner that the collection has possible higher resource usage

[gambit9009]

There's no great 100% answer here. Users can select "Detailed" then strip off checks to where it wouldn't be as likely to cause an issue. They could select "General" but then manually add a bunch of collectors, traces, xevents, etc.

On some systems a heavier load, larger queries, etc. could make PSSDiag/SQLDiag use more recourses (large memory grants/CPU usage/Writing to disk) to collect data possibly regardless of some of the collectors.

We can't predict the load on the system at the time PSSDiag is running, but possibly we could just warn based on certain collectors picked. ????
Possibly warn if redundant collectors are picked. (dont know if this still happens but long ago some users might pick all the ways to get query plans and we'd get the same query plan captured many times)

Possibly add a node to the XML that just has better readable for human eyes lines about what exactly is being collected. Or even if not exact, a summary. "Detailed was chosen. Collecting 32 xevents. Collecting 3 custom collectors." etc

Adding this as a possible future enhancement but this would take some work.

[gambit9009]

Probably a dup for #117 but also related to, or could fix....
#165
#55
#85