The problem is that the pollers write to rrd's local to the poller box
and observium isn't written in a way where these can be easily
distributed. I wrote the patch that added that comment as that was my
goal. I tested using parallel rsync methods as well as using glusterfs
replicated filesystem across multiple datacenters but couldn't get my
polling runs + syncing to complete within 5 minute runs (quickest I
could get were 8 minute runs writing to about 16,000+ rrds). I have a
large number of ports however so smaller installations could probably
work.
I wonder what the plans are for being able to distribute observium
across multiple hosts, geographically or not. Or if anyone else has
attempted this.
What would be great would be the option to use something like graphite
for the graphing backend so pollers could just send data to graphite and
observium could use graphite to create the graphs for the web interface.
>On 2013-06-24 14:46, Benjamin Abadie wrote:
>> Hi,
>> I'm reading the following as a comment in poller-wrapper.py :
>>
>> Additionally, if a hostname wildcard is passed, add it to the where
>> clause. This is
>> important in cases where you have pollers distributed geographically
>> and want to limit
>> pollers to polling hosts matching their geographic naming scheme.
>>
>> Do you have some advice on how I could implement this (that is,
>> multiple pollers on multiple servers) ? Even if it is not shiny enough
>> to be put in production, that's just for testing purposes.
>>
>> I hope my brain cured since last time I posted on this ML, and is now
>> compatible with Adam's one.
>
>There is no geographic distribution possible.
>
>adam.
