You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I don't know if this is the right place to request a feature, but, with increased adoption of the pS testpoint replacing the toolkits , it would be extremely useful if
pscheduler throubleshoot --stats --host $node
would produce statistics like CPU load, memory usage and memory free for $node, memory used in $node by opensearch, postgress, logstash, and other potential hoggers. Those numbers are extremely useful for someone debugging remote hosts.
Also, something like
systemctl restart perfsonar.service
to restart all perfsonar associated unit files in a given host.
Raul
The text was updated successfully, but these errors were encountered:
I don't know if this is the right place to request a feature, but, with increased adoption of the pS testpoint replacing the toolkits , it would be extremely useful if
pscheduler throubleshoot --stats --host $node
would produce statistics like CPU load, memory usage and memory free for $node, memory used in $node by opensearch, postgress, logstash, and other potential hoggers. Those numbers are extremely useful for someone debugging remote hosts.
Also, something like
systemctl restart perfsonar.service
to restart all perfsonar associated unit files in a given host.
Raul
The text was updated successfully, but these errors were encountered: