Description of problem: If the postgresql collectd plugin is not configured correctly it will fail Collectd from starting. We need to enable it only if its is actually configured and the database is local.
Yaniv - please reply here to bug 1429861 comment 13. Thanks. For that bug I don't separate local/remote dbs.
(In reply to Yedidyah Bar David from comment #13) > (In reply to Yaniv Dary from comment #12) > > - We can not assume we are the owners of the postgres and have permission to > > the stats. > > Indeed, and this is true also for a local db. We are going to use engine db > creds, which should work the same whether local or remote. > > > - Most likely it is monitored on the remote site > > Indeed. But IMO there is some added value in monitoring and keeping stats > etc. in our own store even then. E.g. one day we might base decisions on > these stats, and would like to be able to make these decisions also for > remote dbs. > > > - We need to be able to work out of the box and not have collectd fail on no > > prmissions to stats table for example. > > See above. > > Do we need permissions that the engine db user does not have? I depends on what the admin user defined in that instance and I don't think we should collect from remote unless we are sure we will not fail on permissions.
(In reply to Yaniv Dary from comment #2) > (In reply to Yedidyah Bar David from comment #13) > > Do we need permissions that the engine db user does not have? > > I depends on what the admin user defined in that instance I do not understand. Which admin user? > and I don't think > we should collect from remote unless we are sure we will not fail on > permissions. If we need extra permissions, we should ask for them. Do we? Please note that this applies also to local db.