Open a1exsh opened 7 years ago
@alexeyklyukin I also think we need a separate call to install the funcs (with security definer option). Then we could grant some role like pgview
permission to execute them, and then finally grant pgview
to anyone we trust to run it remotely.
As for du/df: running less often makes a lot of sense, since these readings are not expected to change very quickly. Every 3-5 ticks should be reasonable. Can we then get rid of subprocesses/queues altogether?
I'd probably supply a SQL file along the way and instruct users to install it with their tools of choice. Actually, for du/df there is another issue: it take a lot of time to return the data, so one of the "ticks" would be slower than the others. Therefore, I'd like to keep the existing multi-threaded functionality at least locally.
Can collect Host information: uptime, hostname, loadavg, etc.
Can collect System information: cpu utilization, context switches, etc.
Can collect Memory information.
Requires stored procs in plpythonu to be installed on the server. Could install automatically on startup assuming enough permissions.
Partition and Postgres collectors are really tricky, but should be doable.