Thanks for your inputs Hiren.
Scott and Steve can explain better, but from what I gather, the information, redundant as it may be, when present in different formats sometimes helps debug issues. So, as long as the information is helpful in any way, as small as it may be, I think there's no harm capturing it.
"Like pbs_diag, is pbs_snapshot is restricted to run only on machine where PBS Server is running?" No, please see the -H option in the design doc, you can provide the hostname to PBS Server while running it on another machine.
"Like pbs_diag, is pbs_snapshot is restricted to run only by root user?" You don't need to be root, but you do need to have sudo privileges.
Regarding mom daemon information, the doc does mention that we'll capture mom logs and core file information. Now that you mention it, I hadn't thought about making mom logs optional, and I do think that's worth discussing because each mom daemon creates its own logs, so they cumulatively can be huge. @scc What do you think? How does pbs_diag do it?
Hiren, for system information from the moms, could you please be more specific about what kind of information you'd like to be captured?
"Like pbs_diag, please include self logs into snapshot.": It's already there right? please see the '-l' option to pbs_snapshot in the doc
"Why we are restricting list of attributes in --obfuscate option? let's user specified this list." Actually we don't want to restrict --obfuscate, we want it to cover everything that the users might consider sensitive. In fact, if required, I think we should instead have an option called "--dont-obfuscate" to let us know if we should not obfuscate something, as that list will probably be smaller. What do you think?
About the -L option, I'm not sure that I completely understand what you meant, could you please go through the interface documentation for -L option and let me know what you'd like to change?
Thanks for the feedback!