Agent running outside the host

[pmpetit]

Hello, I think for the moment it is not possible, because temboard-agent communicate with pgsql using /var/run/postrges/xxx on the host itself. Do you think it would be possible to have the agent running outside ?

I am thinking about having dockerised agent running on rancher, monitoring my AWS rds databases. Even if i miss some particular OS metrics (on RDS they are not available) Thanks

[bersace]

Hi @pmpetit

Yes, temboard-agent is not cloud native. pgconf plugins only works if temboard-agent and postgres are on the same host. For monitoring, we can do something.

[bersace]

Hi @pmpetit

There is some news on this subject. Next release of temBoard drops managing postgresql.conf, pg_hba.conf and pg_ident.conf file from file system. This reduce the needs for temBoard to be on the same host.

For now, temBoard still require access to the socket and to pg_ctl. Things may change.

Cordialement,

[pmpetit]

Hello, i can see a new temboard release... Any news about the "socket and pg_ctl" needs ? thanks

[pmpetit]

Hello, Just to tell you that i'm trying to split temboard-agent from the host, to use it from with rds DBs, and remove the super-user check on start. Because metric system are not our priority, we can get them easily from cloudwatch.

[bersace]

We need SSL connexion to implement this.