Mahadevan

Currently, pgmetrics can only parse local log files that are actually present as files in the filesystem. In case of remote servers, you'll have to first fetch the log files...

> Would it be possible to add a small section to the docs highlighting what extensions are needed for what feature? Perhaps even showing the ideal/expected settings associated for each....

This was done to support SCRAM-SHA-256 which was not available in lib/pq. Now that lib/pq also supports SCRAM-SHA-256, the fork is no longer needed and we should be going back...

Yes, a PR for native graphite support is welcome! I suggest starting off by copying `cmd/pgmetrics/csv.go` to `cmd/pgmetrics/graphite.go`, and esstentially port your JS code to a top-level function: ```go func...

The path to the key was picked up, but it was unable to open the file. Maybe the file was deleted (but was loaded into ssh-agent before deletion)?

Commit b3a91f4 has been tagged as release_1.0

rtop does attempt to use the agent first, on all platforms. Could you debug through sshhelper.go function tryAgentConnect() and see what's going on?

Hmm, maybe it is picking up the key file auth method first, before the ssh-agent method. Can you try an experiment please? - comment out line 118 in sshhelper.go: auths...

Hmm, it does for me. Can you try with a non-password-protected private key?

Please check with commit f753d19. With this rtop will natively support encrypted private keys, and also support auth via ssh-agent correctly.