We currently have no system of tracking information like this. It's a lot of word to add new entity types to track things, probably far more work than this is worth.
This kind of thing is what the 'application' system is for, but we still have no real way of storing state in the database for applications, which limits its effectiveness somewhat.
Any suggestions on how to maintain state for this kind of thing in a generic way would be helpful :)
adam.
On 2014-06-02 01:42, David Peall wrote:
Hi
I want to monitor Postgres servers and was wondering the best way to go about this.
On the master server there are several clusters each with a number of databases. On the replication servers the same exists but I’d like to monitor the streaming replication delay.
I’m just wondering what the best layout would be to bring the data into Observium?
Regards — David Peall _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium