Hello All;
I am considering expanding my design to allow for more than one syslog-ng
servers, each with it's own PHP/MySql backend.
The problem is that when searching for data on just one of servers, you're
limited to what just that one server knows about.
It dawned on me that latest version of MySql might be able to perform a two-way
synchronization, but quickly realized that there is a possibility for conflicts
with regards to the SEQ number assigned to an event.
One possible solution for this would be to allow the installer script (or
manually at first) the ability to simply add a unique, site/client/whatever
based SEQ ID. This unique SEQ ID prefix shouldn't be more that two characters,
so with an alphanumeric entry, this should be sufficient for any site I've
managed. This would prevent SEQ ID 899453 at one site from causing a conflict
with SEQ ID possibly assigned at another site. Each site would have a SEQ ID
prefix with something like S1-899453 and S2-899453. This might also help
narrow down searches in the event you wish to limit a query to just those
events at site 1, which you can use "S1-" as a query.
Comments, flames, spears, whatever, are welcome.
.vp
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Php-syslog-ng-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/php-syslog-ng-support
